Security
Bookmarkr is a private library. The aim is simple: your shelves stay yours, traffic is encrypted, and we collect as little as we can.
No system is perfectly secure. If we discover a breach affecting your personal data, we will notify you and the relevant regulator as the law requires.
How we protect the service
- All traffic is encrypted with TLS. HTTP Strict Transport Security is set to two years.
- Data is protected at the database by row-level security, so a query returns only the rows that account is allowed to see. Search, connections, and shared shelves can still show a limited public profile.
- Passwords are hashed by our authentication provider. We cannot read them.
- Email and Google-linked accounts can add an authenticator-app second factor. A verified code is required after password or Google sign-in. Google-only accounts keep using Google's sign-in.
- Payment details are handled entirely by Stripe and never touch our servers.
- Rate limiting protects account creation, password reset, and email-sending endpoints.
- The API sends a strict Content Security Policy,
Referrer-Policy: no-referrer, and a Permissions-Policy that disables camera, microphone, geolocation, and payment access. The site document sendsReferrer-Policy: strict-origin-when-cross-origin. - Requests to internal and private network addresses are blocked when we look up a favicon.
Sharing and MCP
Nothing you save is visible unless you share it. You choose who sees a shelf, whether they can view or edit, and you can revoke that access.
Pro members can generate an MCP token in Settings to connect Cursor or Claude. Those tools can list and update your own shelves. Shared shelves stay out of MCP. Treat the token like a password: do not commit it, and revoke it if it leaks.
Pro members can also add an automation webhook. Bookmarkr POSTs signed events about your own sites to an HTTPS address you choose. The signing secret is shown once and stored encrypted. Revoke the automation, or change your password, if that address leaks. Shared shelves stay out.
What not to store
Do not put passwords, PINs, card numbers, CVV codes, bank details, security answers, one-time codes, or recovery keys into Bookmarkr, not in a note, a link name, a shelf name, or your biography.
Bookmarkr stores the link to a site. The password for that site belongs in a password manager.
Your device
Your session is stored in your browser's local storage. Anyone with access to your unlocked device can use your account. Lock the device, and sign out on shared computers.
Account → Active sessions lists other browsers signed into this account, with a short device label and an approximate city/region looked up locally from the connection IP (the address is not stored). You can sign those devices out from that list.
Account → Two-factor authentication lets email and linked accounts enroll an authenticator app. We do not store the 6-digit codes.
Report a vulnerability
If you find a security issue, tell us through Contact and mark the message as a security disclosure before publishing it. Give us a reasonable chance to fix it.
We will not pursue action against researchers who act in good faith, avoid privacy violations and service degradation, and do not access or modify other people's data.
Do not probe, scan, or test the service without permission. That is a breach of the Acceptable Use Policy.