Privacy Policy

Last updated: May 10, 2026

dropdat (“we”, “the extension”) helps you capture AI chat conversations from supported sites, reuse that context across other chats, and save individual web pages or links into folders for later reference. This policy explains what the extension reads, what it stores, and where data goes.

What we read

When you click the dropdat capsule button on a supported chat site (ChatGPT / OpenAI, Claude, Gemini, Grok, Microsoft Copilot, Perplexity), the extension reads the visible messages from the active conversation in order to build a “capsule.” Reading happens only when you click Generate. We do not read pages passively, and we do not read pages outside the supported chat hosts listed in the extension manifest.

When you right-click on any web page and choose dropdat → <folder name>, or click Save tabin the extension popup, the extension reads only the URL and page title (and, where the browser provides it, the favicon URL) of the active tab. We do not read the page’s content, DOM, cookies, or form fields when saving a link. The save only happens on that explicit user action.

What we store

Each capsule contains:

  • A title (extracted from the page).
  • The user/assistant message text from that conversation.
  • The source host (e.g., chatgpt, claude).
  • The page URL.
  • Timestamps and a local id.

Each saved link contains:

  • The page URL and title at the moment you saved it.
  • An optional favicon URL.
  • The folder you chose (or your default folder if none).
  • Timestamps and an id.

Capsules are written first to the browser’s local IndexedDB inside the extension’s own origin. Saved links and folders are written directly to your dropdat account on our backend (they require you to be signed in via an API key). Your selected default folder and the API key itself live in chrome.storage.local.

Right-click menu & notifications

The extension adds a single dropdatentry to the browser’s right-click menu. The submenu lists your folder names so you can pick a destination in one gesture. After a successful save (or a failure such as “sign in first”) the extension shows a single OS notification as confirmation. We do not send unsolicited, marketing, or background notifications.

What we sync (account-only)

If you sign in to the extension by pasting an API key generated in the dropdat dashboard, capsules are uploaded to your dropdat account on our backend so you can access them from the web dashboard. The backend stores capsules, folders, and saved links under your authenticated user id. You can delete any of them from the dashboard at any time.

Saved links and folders always live on the backend (they require an account to be useful). Capsules also work offline-first: if you do not sign in, capsules stay only in your browser.

Cookies and authentication

The extension uses Chrome’s cookies permission solely to read your Clerk session cookie from *.clerk.accounts.dev so that the popup can authenticate to the dropdat backend on your behalf. We do not read cookies from any other origin and we do not transmit cookies to any third party.

Third parties

  • Clerkis used for authentication. Clerk’s own policy governs how it handles your account email and session. See clerk.com/legal/privacy.
  • The dropdat backend stores your capsules under your account.
  • We do not use analytics, advertising trackers, or external telemetry.

Permissions, briefly

  • storage, activeTab — needed to mount the capsule button inside chat composers, read the active tab on user action, and persist capsules / API key / preferred folder locally.
  • contextMenus — registers the right-click dropdat menu so you can save the current page or a right-clicked link into a folder.
  • notifications — shows a single OS toast confirming a save (or surfacing a failure). No background or marketing notifications.
  • cookies — Clerk session cookie only.
  • Host permissions — limited to the supported chat sites, the dropdat backend (dropdat.app), and Clerk domains.

Data deletion

  • Local:open the extension popup and remove individual capsules, or clear the extension’s site data via Chrome’s extension management UI.
  • Synced: delete from the dashboard, or contact us via the support email below.

Changes

If this policy changes materially, the “Last updated” date will change and we will note the change on this page.

Contact

Email: support@dropdat.app