Skip to content
bkmark.it

Privacy policy

Last updated 13 November 2026

bkmark.it keeps the links you save, a readable copy of each page, and what you write about them, so you can find them again. We collect what we need to run that service and nothing for advertising. We do not sell your data, show ads, or track you inside the app. Some features send page content to AI providers to suggest tags, write summaries and power search by meaning. You can export everything and delete your account yourself at any time.

Who we are

bkmark.it is run by [Company legal name], [registered address]. We are the controller of the personal data described here. For team libraries, the team decides what goes into the library, and we process that content on the team's behalf.

Questions about privacy: privacy@bkmark.it. Anything else: support@bkmark.it.

What we collect

Your account

  • Email address and name.
  • Your password, stored only as an Argon2id hash. We never see or store the password itself.
  • Passkeys (the public key and device details your browser gives us), and your two-factor (TOTP) secret, encrypted at rest.
  • If you sign in with Google or GitHub, the account id that provider gives us.
  • Security history: sign-ins, new devices, password and two-factor changes, and keys or apps you connect. Each entry records the IP address and browser (user agent) it came from. You can see this list in Settings.
  • Active sessions, with the IP address and browser that started them.
  • Preferences such as reading size, whether tags are applied automatically, and whether your share pages can be indexed.

Your library

  • Bookmarks: URLs, titles, descriptions, notes, tags, collections, saved searches, and read, archived and ribboned state.
  • Saved copies: the readable text and cleaned-up HTML of each page you save, fetched by our servers.
  • Highlights and notes you write on saved pages.
  • A search index built from the above: text chunks and, on paid plans, embeddings (numeric representations of meaning).
  • AI suggestions and summaries generated for your bookmarks.
  • Link health results, which record whether a saved page still loads.
  • Usage counters, such as how many saves got AI tags this month.

Billing

Paddle sells our paid plans as merchant of record. Paddle collects your card or other payment details, billing address and tax information. We never receive your card number. We store the Paddle customer and subscription ids, the plan, the billing status, the seat count and the renewal or cancellation date.

Integrations you connect

  • Slack: the workspace id, the Slack user ids linked to your account, channel mappings, and the workspace's bot tokens, encrypted at rest.
  • Zapier and other connected apps: the authorization you granted. Access and refresh tokens are stored only as hashes.
  • API keys: stored only as hashes, with a short prefix so you can tell them apart.
  • Webhooks: the URL you register, an encrypted signing secret, and a log of each delivery, including the payload we sent.
  • Email-to-save: when you forward mail to your private save address, we receive the message, read its subject, text and links, and save a bookmark or note. We keep the sender address with the bookmark. We do not keep the original message.

When you use the service

Our servers log requests (time, path, IP address, status) to keep the service running and secure. Logs leave out passwords, cookies and access tokens.

How we use it

  • To provide the service: store your library, fetch and keep page copies, build the search index, sync your devices, and run the integrations you connect.
  • To keep accounts secure: detect new devices, rate limit abuse, and show you your security history.
  • To send email you need: verification, password resets, security alerts, billing notices, and team invitations.
  • To send the optional digest email, if you turn it on.
  • To enforce plan limits and handle billing.
  • To fix errors and improve reliability.

We rely on these legal bases where GDPR or UK GDPR applies: performing our contract with you (running the service), our legitimate interests (security, abuse prevention, error monitoring), your consent (the digest email and connecting optional integrations), and legal obligations (tax and accounting records).

AI features

When you save a page, we may send its title, URL, description and readable text, along with the names of your existing tags and collections, to Anthropic (Claude) to suggest tags and, on paid plans, write a short summary.

On paid plans, we send text chunks of your bookmarks, saved copies, highlights and notes to Voyage AI to create embeddings for search by meaning.

Under their commercial API terms, Anthropic and Voyage AI do not use API inputs to train their models. We do not use your content to train any model.

The Free plan includes AI tag suggestions for 25 saves a month. Search by meaning and summaries are on paid plans only. You can choose whether suggested tags are applied automatically or wait for your review. You can also turn AI off for your personal library in Settings → Profile; team admins can do the same for a team library. With AI off, nothing from that library is sent to Anthropic or Voyage AI, search matches words only, and its stored embeddings are deleted at once.

Who we share it with

We use these service providers (sub-processors). Each gets only what it needs for its job.

ProviderWhat forData involved
Fly.ioHosting, database and cache, in the United States (New Jersey region)Everything stored in the service
AnthropicTag suggestions and summariesPage title, URL, description and text; your tag and collection names
Voyage AIEmbeddings for search by meaning (paid plans)Text chunks of bookmarks, saved copies, highlights and notes
ResendSending email, and receiving mail for email-to-saveYour email address, email content, forwarded messages
PaddlePayments, as merchant of recordBilling and payment details you give Paddle at checkout
SentryError monitoringTechnical details of errors, which can include request metadata. Error reports are set up to leave out cookies, passwords and tokens
PlausibleVisitor statistics on the public website only, not in the appPage views, without cookies or personal data

Only if you use them:

  • Slack and Zapier, when you connect them. They receive the bookmarks and search results you ask them to handle.
  • Google and GitHub, when you sign in with them.
  • Webhook URLs you register receive the events you subscribe to.

We disclose data to authorities only when the law requires it. If bkmark.it is sold or merged, your data would pass to the new owner under this policy, and we would tell you first.

Pages we fetch

To save a copy and check link health, our servers request the pages you save. The site you saved sees a request from our servers, not from your device or IP address.

Sharing and teams

  • Public share links: anything you share by public link is visible to anyone who has the link. Share pages ask search engines not to index them unless you turn on indexing in Settings. You can revoke a link at any time.
  • Team libraries: members of a team library can see its bookmarks, team highlights and the shared note. Your private highlights and notes stay private, even on team bookmarks. Team admins control the team library.

Cookies and local storage

The app sets one cookie, bk_session, which keeps you signed in. It is essential and cannot be turned off. The app also uses your browser's local storage for your theme, reading settings, the last library you opened, and dismissed banners. These stay on your device.

There are no advertising or tracking cookies, and no ads. The public website uses Plausible, which does not set cookies. When you upgrade, Paddle's checkout loads on the plan page and may set its own cookies under Paddle's policy.

How long we keep data

DataHow long
Your account and libraryUntil you delete them or your account
Bookmarks in the trash30 days, then permanently deleted
Saved copies on Free30 days after they are fetched, unless you upgrade. Copies fetched on a paid plan or during the trial are kept permanently
Sessions30 days at most. Signing out ends a session at once
Webhook delivery logs30 days
Expired OAuth codes and tokensDeleted a day after they expire
Security history (sign-ins with IP address and browser, security changes)365 days, then deleted. The record that you used your one Team trial is kept without IP address or browser
BackupsUp to [N] days after deletion
Billing recordsAs long as tax law requires, held by Paddle and by us

Moving from a paid plan to Free never deletes your data. Features you lose pause and come back when you upgrade. On Free, new saved copies expire after 30 days.

Your rights

You can:

  • See and export your data. Settings has a full account export (JSON) and a library export (JSON, HTML or CSV).
  • Correct it. Edit your name and any bookmark at any time. Change your email address in Settings → Profile: we send a link to the new address, tell the old one, and switch only when you open the link.
  • Delete it. Delete your account in Settings. You need to have signed in within the last 10 minutes. Deleting your account removes your personal library and everything in it, your sessions, and team libraries where you are the only member. If you are the last admin of a team with other members, make someone else an admin first. Content you added to a team library stays with the team.
  • Object or restrict processing based on our legitimate interests, and withdraw consent for anything that relies on it.
  • Complain to your data protection authority.

Where GDPR or UK GDPR applies, these are your rights under those laws. If you live in California, you have the right to know, delete and correct personal information, and not to be discriminated against for using these rights. We do not sell or share personal information for cross-context behavioural advertising.

To use a right we cannot offer in Settings, email privacy@bkmark.it. We reply within 30 days.

International transfers

We host in the United States, and our providers may process data there or elsewhere. Where data leaves the UK or EEA, we rely on the European Commission's Standard Contractual Clauses (and the UK addendum) or another lawful transfer mechanism.

Security

Passwords are hashed with Argon2id. Two-factor secrets, Slack tokens and webhook secrets are encrypted at rest. API keys and OAuth tokens are stored as hashes. Connections use HTTPS. Saved pages are sanitised before they are shown. No system is perfectly secure; if a breach affects your data, we will tell you as the law requires.

Children

bkmark.it is not for anyone under 16. If you think a child has given us personal data, contact us and we will delete it.

Changes to this policy

If we change this policy in a way that matters, we will email you or show a notice in the app before the change takes effect. The date at the top shows the latest version.