Privacy policy

Two kinds of data, and they are worth separating.

Your account

• Your email address. It is how you sign in and how we contact you.
• If you sign in with Google: the email address, name and profile picture Google returns. We do not request access to anything else in your Google account.
• Subscription status. Payment details never reach us — see Payments below.

Your library

• The links you save, with their titles and when you saved them.
• The content behind those links: page text, a screenshot of the page, and for video or audio posts, a transcript and a few sampled frames.
• What our AI providers derive from that content: a short summary, tags, written descriptions of images and frames, and numeric embeddings used for search.
• Operational logs (errors, timings, counts) that let us tell whether indexing is working. These are not a record of your reading.

We fetch page content from the public internet on your behalf, as a signed-out visitor would — the browser that renders your saved pages runs on our servers and carries none of your cookies or logins. So we never receive your logged-in view of a page. Save a site you are signed into and we index the public version of it, or nothing at all. The extension cannot screenshot or read the pages you browse: it does not request the permissions that would let it.

The one exception is the optional X, Instagram and YouTube sync, and only if you turn it on. Those read your own saved-items list on the site while you are signed in, and send us the links plus their captions or titles — never the page itself, and nothing outside the list you asked us to sync.

To provide the product: indexing what you save is the product. We also use aggregate counts (how many items indexed, how many failed) to keep the pipeline healthy and to size costs.

We do not sell your data, we do not share it with advertisers, there is no advertising or third-party tracking on this site, and we do not use your library to train our own models.

Running the product means handing parts of your content to infrastructure providers. This is the complete list, and what each one receives:

• Cloudflare — hosting, file storage for screenshots and media, the browser that renders pages, transcription of audio, and delivery of our emails.
• Neon — the database holding your account and library.
• OpenAI — receives extracted text and images to produce summaries, tags, descriptions and search embeddings. Sent through their API, which under OpenAI's current API terms is not used to train their models.
• DataImpulse — a proxy network our servers use to fetch public media posts. It carries the outbound request, not your account data.
• Polar — payments and invoicing. They are the merchant of record.
• Google — only if you choose to sign in with Google.

Deepmark staff can read the content stored in your library.

We run an internal tool that shows accounts and the items, text, transcripts and screenshots stored against them. We use it to diagnose indexing failures, which is the most common thing that goes wrong, and it is what makes the product fixable. We state it plainly because a policy that implies otherwise would be untrue.

We do not read libraries for curiosity, we do not use their contents to market to you, and access is limited to people operating the service. If you would rather nobody could, the honest answer is that Deepmark is not the right product for that material.

We keep your library until you delete it. Deleting an item removes its stored text, tags, embeddings and screenshot. Deleting your account removes the account and everything saved under it.

Backups and logs can lag a deletion by a short period before they roll over. To delete your account, email us at support@usedeepmark.com.

Depending on where you live, you may have the right to access, correct, export or delete your personal data, to object to processing, or to complain to a data protection authority. Email support@usedeepmark.com and we will action it.

Our lawful bases, where the GDPR applies: performing our contract with you (running the service you signed up for), our legitimate interests (keeping the pipeline working, preventing abuse), and your consent where you have given it.

Data is encrypted in transit. Access to production systems is limited to the operator of the service. No system is perfect; if we discover a breach affecting your data we will tell you.

One cookie, for keeping you signed in. No analytics, no advertising, no third-party trackers.

Deepmark is not intended for anyone under 16, and we do not knowingly collect their data.

If we change this policy materially we will update the date at the top and, for anything significant, email you.

Deepmark is an independent product, operated from India. For anything in this policy — access, correction, export, deletion, or a complaint — email support@usedeepmark.com and a human will answer.