Privacy Policy

The short version

DIVE edits the page rendered in your browser and records a local change session. Nothing about your edits leaves your machine until you choose to connect an agent or share a project to the team workspace.

Release builds of the extension send anonymous usage analytics to PostHog. Those events never include page content, URLs, selectors, edits, comments, tokens or screenshots.

When you send changes to Claude, Cursor or another coding agent, that provider processes them under your account and its own privacy terms.

What the extension stores

DIVE reads the rendered DOM, computed styles and geometry needed for the features you use. It cannot run on browser-internal pages or extension stores. Don’t use it to capture passwords, private form data or content you aren’t allowed to share.

• Local extension storage: interface preferences, shortcuts, comments, MCP mode, relay URL and the Cloud credential, until you clear them or uninstall.
• Synced browser storage: presets you explicitly save, synced through your browser account.
• Session storage: per-page style, text and structure changes for the current browser session (local storage is used as a fallback where session storage is unavailable).

When network traffic starts

No MCP connection: on a fresh install every MCP transport stays closed until you connect one. Copy as Prompt works without any connection.

Local mode: the extension talks to a companion server on your own machine over an authenticated localhost connection. Nothing goes through our relay.

Cloud mode: choosing Connect to Cloud registers an anonymous device credential. The relay keeps only a SHA-256 hash of it, an anonymous tenant ID and timestamps. Requests between your agent and the extension sit in a short-lived queue with a best-effort 60 second expiry, and are usually deleted as soon as they are read.

Relay logs may include the anonymous tenant ID, message type, payload size, latency, status and short error codes. They never include selectors, screenshots or payload bodies, and relay traffic is never used to train a model.

Self-hosted mode: you run the relay, so retention, logging and access controls are yours.

Screenshots and agent handoff

Screenshots are captured by your browser and stay on your machine unless an MCP action you trigger returns one to a connected agent.

Copy as Prompt writes a Markdown specification to your clipboard. Send to Agent makes your recorded changes available to a connected MCP client. Neither gives DIVE access to your repository.

The team workspace

The workspace at dive.samsad.dev is optional. When you create an account, Supabase Auth stores your email, display name and sign-in identity. Passwords are hashed by Supabase and DIVE never sees them. Google, GitHub or your company’s SAML provider is contacted only if you pick that sign-in method.

We store organization and team names, memberships, roles, pending invitations (only a SHA-256 hash of each invite link) and an audit log of membership and invite changes.

Only projects you explicitly share from the extension are synced, with their change records and snapshots. Row-level security limits every row to the owning person, team or organization.

Cookies: a Supabase session cookie, the sidebar state, and the organization you last selected. Your theme choice is kept in local storage. No advertising or analytics cookies are set by the workspace.

Usage analytics

The extension is free and MIT-licensed. To understand active installs, retention and which features people use, release builds create a random ID in extension storage and send events to PostHog with your browser, extension version, language, timezone and user agent. Page URLs, selectors, edits, comments, text, tokens and screenshots are never included. Source builds without analytics configured send nothing.

Browser permissions

• activeTab and tabs, to open the editor on the current tab and follow navigation.
• scripting, to inject the inspector after you open DIVE.
• storage, for the data described above.
• Side panel (Chrome) or sidebar (Firefox), for the editor itself.
• Broad host access, so the editor works on the sites you choose. DIVE doesn’t touch a page until you open it on that tab.

Deleting your data

• Clear a change session from the Changes tab.
• Remove saved presets and comments in the extension.
• Revoke your Cloud credential from the MCP page before deleting it locally to remove its hash from the relay.
• Uninstall the extension to remove its local storage.
• Leave or remove members from an organization in the workspace; ask an owner to delete shared projects.

Reporting a security issue

Please report vulnerabilities privately rather than in a public issue, and never include real credentials. Describe the problem, the affected version and steps to reproduce, and we’ll respond as quickly as we can.