Privacy
This policy describes how Blogmarks (blogmarks.dev), including the website and the Chrome extension, handles information. Last updated: April 5, 2026.
Website
When you use the web app, we process data needed to run the service: for example, bookmarks you save, account identifiers tied to your sign-in, and technical data such as IP address for rate limiting and security. AI enrichment uses the content of pages you save, as described on the site. Use the in-app sign-out flow to end your session in the browser.
Chrome extension
The Blogmarks extension saves the URL and title of the active tab when you choose to save, and sends them to the Blogmarks API (api.blogmarks.dev) over HTTPS using your session.
Sign-in: If you sign in from the extension, your phone number and verification code are sent to AWS Cognito (Amazon Web Services) only for authentication. Cognito issues tokens; the extension stores ID and refresh tokens in Chrome extension storage so you stay signed in. Sign out from the extension popup to clear those tokens from your device.
The extension does not read browsing history, inject scripts into web pages, or access sites other than the Blogmarks API and Cognito for the purposes above.
Third-party services
We use infrastructure and providers needed to operate the product (for example AWS for hosting, Cognito for auth, and email/SMS delivery as configured for your account). Their use is limited to providing the service.
Retention
Extension: Cognito tokens remain in extension storage until you sign out or remove the extension. Server: Bookmarks and account-related data are kept for as long as your account exists and as needed to operate the service (for example backups, security, and legal obligations). When you delete your account or we delete data under our processes, associated server-side copies are removed or anonymized according to our operational practices.
Contact
For privacy questions, use the support email shown on the Chrome Web Store extension listing, or open an issue on GitHub.