What your browser shares.
Relay shares selected observations and files to carry out tasks you authorize. Browser use and personal learning settings apply to your current user and selected project. Chrome’s local options can add further restrictions.
Selected pages
When you approve an observation, Relay may send the selected page’s URL, visible text, control labels and element references to your configured ShowWeld endpoint. It does not collect your general browsing history. Page text can contain private information; connect only the tabs needed for your task.
Your chosen AI provider
The host application decides whether approved task evidence is forwarded to its configured AI provider. That route must follow your selected provider and payer. The extension does not carry provider credentials or change that route.
Screenshots and cursor
Screenshots need individual approval and capture the visible approved tab. Pixels may reveal information that text filtering cannot remove. The AI cursor indicates a target on the page; it does not take over your physical pointer. You can hide it or reduce its motion in settings.
Files you select
You can select or drop supported text files, up to 64 KiB each, into the extension. Review the filename, preview, size and hash. Unshared selections remain in temporary local memory and expire; stopping or losing the browser workspace can clear them. A separate approval is required before an agent can read the text.
After an approved read, its text becomes part of the task receipt. The extension can temporarily keep that receipt in its delivery queue until the server acknowledges it. The host then stores the encrypted receipt, and any selected AI provider follows its own disclosed retention. Stopping execution cannot retract information already sent.
Generated edits are prepared for review. You choose Save and the destination through the browser. Preparing a file is not confirmation that it was saved. Relay preserves the reviewed text’s exact bytes, including a UTF-8 byte-order mark and line endings. It does not scan directories or accept arbitrary disk paths.
What a save report means
The original file-preparation receipt stays unchanged. After your Save action, the extension can send a separate report that matches the prepared command, proposed filename, byte count and hash. It sends no destination path, file handle or additional file-content copy. If you rename the destination, only the original proposed name is reported.
A browser write report means the browser’s write and close operations returned successfully. A download handoff means the browser received a download request; it does not confirm that the download finished or that a file reached disk. The server cannot independently inspect your disk. Cancelling the picker creates no successful save report, and an uncertain write remains flagged for your review.
The extension keeps pending save-report metadata locally so it can retry delivery with the same event identity, without writing the file again. Accepted, cancelled or dismissed history is limited to 100 entries and expires after 24 hours when the extension next runs maintenance. Up to 32 outstanding records are kept without silently discarding undelivered reports. An older host without save-report support keeps this evidence local and does not claim server acknowledgement.
Sign-in stays with you
Guided sign-in pauses automation and brings you to the selected tab. Use Chrome’s normal autofill or type directly into the website. Resume deliberately afterwards. Relay does not read Chrome’s password vault, cookies, one-time codes or payment credentials. Automatic filtering cannot guarantee every page or file is free of secrets.
Personal learning is your choice
Both learning settings start off. “Allow reviewed learning examples” lets you submit a correction for an available completed action and review whether to include it. The included settings workspace provides these controls. Your labels mean “Ordinary action” or “Needs closer review”; they do not approve browser actions or declare them successful.
PHP derives bounded features from that action’s stored evidence. The learning record contains those features and labels rather than another copy of the raw page, file or credential text. Derived features can still be sensitive. No page, file or action automatically becomes an example, and the browser cannot opt you in.
The separate “Improve review suggestions for this project” setting permits personal updates from approved examples. You explicitly choose “Queue validated update.” A finite PHP worker trains, checks and either publishes or rejects the update. It can finish while you are away if the host has scheduled that worker. This learning makes no external AI-provider requests and starts no browser actions.
Your private examples, learning nodes and personal model stay with the current user and project by default. They are not automatically combined with other users’ data or sent to an external training service. A bundled public base model supplies review advice when no usable personal model is active. Learned advice can be wrong and never grants permission.
Review and withdraw learning
Pending examples require your explicit inclusion decision. Conflicting labels stay excluded. You can withdraw an included example, inspect learning nodes and remove a node; these changes invalidate dependent learned suggestions. An update must pass validation before it is used.
Deleting a learning node also keeps a minimal private record that blocks its same or older source revision from being imported again. That record contains no raw text or feature vector. It expires with the source and is removed by full project data deletion. The separate feedback example remains available for your review. A later explicit approval of a newer revision can make it eligible again; simply submitting it again cannot.
Turning off personal updates withdraws your derived model and queued learning work. Your reviewed-example setting can remain enabled separately. The minimal records that honor your node deletions remain until their expiry or full project deletion. Turning off reviewed examples also disables personal updates and clears the associated feedback. Learning preferences have a revision so old work or delayed cleanup cannot override a newer choice.
Storage operations can fail. If cleanup cannot finish, the interface reports that a retry is needed rather than claiming the records are gone. The separate data stores do not provide a single all-or-nothing deletion transaction. Backups and copies already exported follow their own policies.
Storage and deletion
The PHP module encrypts command and receipt content, stored feature vectors, and private model/checkpoint payloads at rest. It does not encrypt every database field: identities, origins, review labels, operation/status information, save-report metadata and audit records have separate metadata retention. You can shorten browser evidence retention within the host’s limits. Cleanup runs in bounded scheduled passes rather than promising instant physical erasure.
Project data deletion revokes paired access and removes runs, commands, receipts, separate save reports, grants and audit data, together with the project’s private feedback, learned state and learning jobs. A minimal disabled preference record and advancing revisions remain to prevent old requests from switching access or learning back on. A reported incomplete cleanup needs a retry. Deletion does not undo actions already performed on another website; backups, exported copies, browser-local queues and provider records need their own cleanup.
Stop and revoke
Stop execution in Chrome, pause browser use in project settings, revoke a remembered permission, or revoke the device. Re-enabling browser use starts fresh; cancelled runs do not resume. Stop invalidates a pending save before its final commit check. A write or browser action already dispatched may still finish and cannot be undone by Stop.
A genuine completed save can still be reported after Stop while the device’s authorization remains valid. Sending that evidence does not write again, resume a run or grant permission. Revoking the device blocks further authenticated reports as well as execution. Disconnecting removes the extension’s local pairing and queues.
Operator disclosure
Before publishing this module, the deploying business must connect its verified account/project permissions, provider routing and private storage, schedule maintenance, and provide its legal identity, privacy-policy URL, contact route, actual recipients, retention periods and provider disclosures.
The cursor is a page indicator, and this module controls supported browser surfaces. Automated package checks do not certify native extension installation, real Chrome or operating-system permission prompts, or every website. Those require staging with the installed extension. Chrome Web Store review is a separate process.