Privacy Policy

Your privacy matters at MarkBase

Last updated: December 19, 2024

Overview

MarkBase is a bookmarking workspace that helps you capture, organize, and revisit the content that matters to you. This Privacy Policy explains what information we collect when you use the MarkBase web app or browser extension, why we collect it, and how we keep it safe. We only process personal data to operate and improve the service you asked for.

Information we collect

  • Account information. When you create a MarkBase account we store your email address, password (secured by Firebase Authentication), and any profile details you choose to add, such as a display name.
  • Bookmark content. Every bookmark you save contains the title, URL, optional description, favicon or custom icon, tags, and timestamps that you provide. This is the core data set the product needs to function.
  • Extension tokens. If you generate an extension token, we create a random credential, hash it, and store the hashed value alongside your user ID and email to authenticate bookmark saves from the extension.
  • Technical diagnostics. We may log basic device and usage information (such as browser type, operating system, and timestamped API events) to troubleshoot issues and keep MarkBase reliable. We do not build advertising profiles or track your browsing history beyond the pages you explicitly save.

How we use your information

  • Authenticate you and keep your library synced across devices.
  • Store, organize, and surface the bookmarks you choose to save.
  • Detect duplicates and power features such as tagging, search, and filtering.
  • Provide customer support and communicate important service updates.
  • Monitor performance, fix bugs, and improve MarkBase based on aggregate usage patterns.

Browser extension specifics

The MarkBase browser extension only accesses the active tab when you ask it to save a page. It collects the tab's title, URL, favicon, and any tags you select, then sends that payload to the MarkBase API using your extension token. Tokens are stored locally in your browser using Chrome storage (and mirrored to localStorage) so you stay signed in; you can revoke them at any time from Settings. If a site does not expose its own favicon, the extension requests one from Google's favicon service, which shares that domain with Google solely to fetch the icon.

Data storage and retention

MarkBase runs on Google Firebase and Vercel-managed infrastructure located in the United States. Bookmark records and account information stay in Firebase Cloud Firestore unless you delete them. Extension tokens are hashed at rest and can be revoked instantly. When you delete bookmarks, they are removed from your account (and may remain temporarily in automated backups before being purged). If you close your account, we delete your profile and associated extension tokens.

How we share information

We do not sell your personal data. We only share information with trusted service providers who help us run MarkBase, and they are obligated to protect it under their own privacy commitments:

  • Google Firebase for authentication, data storage, and security monitoring.
  • Vercel for hosting the MarkBase web application and APIs.
  • Google Favicon service to fetch a site icon when the bookmarked page doesn't provide one.

We may also disclose information if required by law, to respond to legal process, or to protect the rights and safety of MarkBase, our users, or the public.

Your choices and controls

  • Update your profile details or display name from Settings.
  • Revoke and regenerate extension tokens at any time.
  • Import or export bookmarks in CSV format, and delete them individually or in bulk.
  • Contact us to request account deletion; we will remove your profile and associated extension tokens.
  • Adjust your browser settings to limit cookies or local storage if you prefer, though this may affect how the extension stays signed in.

Children's privacy

MarkBase is not intended for children under 13, and we do not knowingly collect personal information from anyone under 13. If you believe a child has created an account, please contact us so we can delete it.

Changes to this policy

We may update this Privacy Policy when we release new features or change how we handle data. If the updates are significant, we will notify you by email or through an in-app message. The “Last updated” date at the top of the page always reflects the most recent revision.

Contact us

Have questions about this policy or your data? Email us at support@markbase.app and we'll be happy to help.