Weavin Browser Extension Privacy Notice

Last updated: October 9, 2026

This notice covers the Weavin browser extension. It adds to, and does not replace, the Weavin Privacy Policy, which still applies to your account and everything else you do on Weavin.

1. What the extension is for

The extension has a single purpose: it lets you use your Weavin avatar in the browser side panel for conversation, optional current-page context, saving to your Weavin library, and acting for you while you watch.

2. When it reads a page

The extension does not keep a script running on every page. It injects its page script on demand. Reading page content starts when you send a message, save a page, or ask it to do something for you.

• When you send a message, a snapshot of the page goes along with it. In an ordinary conversation the snapshot is used only for that turn, is not written to the message history, and a new one is taken on the next turn. A snapshot can include the page's rendered text, element labels, the current values of form fields that are not protected, and link and frame addresses, including non-sensitive query parameters. It is not limited to the visible area.
• When you save a page, its text (including the transcript, if the page has captions) is stored as a Markdown note in your Weavin library. On video or audio pages without captions, saving may download or upload the media and transcribe its audio. The audio, transcript, cover image and a note with the original link are kept in your library. The signed media address is handled temporarily and stored encrypted until it has been used.
• When you ask it to act for you, the task can keep reading and acting, including in a background tab, until it finishes or you stop it.
• Site settings lookup. While the side panel is open, the domain of the current site is sent to Weavin to look up your settings for that site. This happens when you open the panel, switch tabs or a page navigates, and the answer is cached for five minutes.
• Sign-in and payment fields. When the extension recognises a visible sign-in or payment input (a password field, a one-time-code field, a card number field or a payment form), it does not read the page content: the snapshot is empty and it does not take screenshots or act. It decides this from the form's attributes and structure, not from what you typed into it. A message can still carry the page address and title. After you tell it you have signed in, actions can continue; the protected field values stay unread. Pages that hold sensitive content but have no such recognised field are not covered by this protection.
• Masking before sending. Page snapshots and the text of saved pages are masked by rules in the extension first (for saved text, including recognised email addresses and phone numbers), and our servers add a second masking pass aimed at credentials. Masking is not applied to everything: the messages and task instructions you type are sent as you wrote them, some page-title paths are not masked in the browser, and signed media addresses are sent intact when needed to save media. Uploaded audio and server-generated transcripts are not covered by the text masking.

3. What is sent to our servers, and where it is kept

• Conversations. Your messages with the avatar are stored. Each message records its source page as the site, a display name and the path (masked), plus a short hash of the full address. The query string, fragment and full address are not stored with the message record. (Snapshots and saved pages can contain addresses with non-sensitive query parameters.)
• Saved pages. Saved text goes into your library as an ordinary library file. A separate capture record keeps the site, path and page hash, a content hash, the status, the media host and times. Deleting the library file does not delete that capture record; deleting your account does.
• Records of what it did for you. For each recorded browser action we keep: the kind of action, the site, the path (without query string or fragment, masked), a page hash, a short masked description (up to 300 characters), the risk level, the verdict and one-line reason from the independent check (see section 4), the outcome, the time, and the avatar, conversation and task it belongs to. These records have no field for typed-in values.
• Task execution data. Separately, when the avatar acts for you, the server stores each step's action values (such as text to type or an option to select), the page snapshots the extension returns, and task progress points. A snapshot nobody used is cleared 60 minutes after the step ends; once the task is no longer running, the stored page content and typed values are cleared; and step rows are deleted after 30 days. Clearing runs in batches, so it can lag. Progress points are kept as long as the task is.
• Devices and site settings. We keep a record of each connected browser (device name, extension and account identifiers, language, token hashes, expiry and last-used times) and your settings per site (the domain, your allow choice and whether high-risk actions are unlocked).
• Built-in scenarios. For scripted scenarios the description is template text, and the record holds the template name and a hash of the path rather than the real host or path.
• The Log. The Log shows the browser actions, checks and outcomes that were recorded. Waiting steps are not recorded, and a record can be missing if logging fails or a limit is reached.

4. The independent check

Actions judged important or irreversible get a separate AI model check on whether the action matches what you asked for; routine actions are not checked this way. The check receives your original request, the kind of action, the site, the page path, the name of the target button or control, the destination, and the value that would be entered or the current value of the related form fields. It does not receive the full page snapshot, your selection, or an address with a query string. The names, option text and values it does receive come from the page.

• Credentials in those fields are masked before the check is sent. Email addresses and phone numbers may remain, because the check needs to know who an action is addressed to.
• The values sent for the check are not saved in the records described in section 3.
• The check goes through our AI gateway, and we require the provider not to retain the data. The model is run by a third-party provider (see section 8).
• During an "Act for me" task, if the check cannot be completed, the step is marked as not checked and waits for your confirmation.

5. What stays on your device

• Local preferences. Your language, one-time tip flags, the sites you paused and the avatar you selected are kept in the extension's local storage.
• Session storage. While work is in progress the extension keeps the message being sent, task instructions, items waiting for your confirmation, the state of connecting the extension to your account, and the ids and stages of saves and tasks.
• IndexedDB. Weavin issues the extension a device token (an access token and a refresh token that lasts 30 days). The extension keeps it, with your account name and profile, in its own browser database, along with operation records waiting to be uploaded and cached settings.
• Not read. The extension does not read your browser's saved passwords, cookies or login sessions. What you type into a message is sent as written.
• Tab addresses. The extension reads the address and title of your tabs to tell which site a tab is on. See section 2 for what is sent. It reads favicons from Chrome's own local cache and does not request them from the websites.
• No remote code. The extension does not load code from the internet.

6. How to delete data or disconnect

• Saved pages are ordinary files in your library. Delete them there. The separate capture record is not removed by that.
• Disconnect the extension: in Weavin, open Settings, then Connected browsers, and choose Disconnect for the browser. Disconnecting makes this device's token stop working. Existing records stay and remain linked to the retained device record. Conversations and library files are not deleted.
• See what was done for you: recorded actions are viewable in Weavin under Browser records, and in the side panel under Log.
• Delete everything: deleting your account removes the records of what the avatar did for you, your devices and capture records, and the rest of your data on the timetable in section 7 of the Privacy Policy.

7. How long we keep it

• Records of what it did for you: records older than 90 days can be deleted. Later writes remove them in batches, so records can be kept longer than 90 days, and may be kept indefinitely if the account is no longer used. Each account also has a daily cap of 5,000 such records.
• Conversations and saved pages: kept until you delete them or delete your account. We do not currently expire them automatically.
• Unfinished saves: a cleanup runs every 15 minutes and closes saves that got stuck and removes their temporary files. This is housekeeping, not a retention period.
• After account deletion: as stated in section 7 of the Privacy Policy, associated data is permanently deleted within 30 days.

8. Third parties and how we use the data

Extension data reaches the types of recipients below, in addition to those in section 4 of the Privacy Policy. We do not sell, rent or trade it. We use it only to provide the extension's purpose described above, not for anything unrelated, and not to judge creditworthiness or for lending.

9. Contact

• Email: privacy@weavin.ai
• General inquiries: hello@weavin.ai

Last updated: October 9, 2026