Chrome & Brave · v1.8.0 · Side Panel · Open Source

Your bookmarks.
Nobody's business.

SafeMark locks your bookmark vault behind AES-256-GCM encryption. No server. No account. No telemetry. Only you hold the key.

free forever · no sign-up · password never leaves your device

Safemark — Vault unlocked
Safemark Vault
Private vault · encrypted · synced
🔒
+
Bookmark this page brave.com/privacy-features/…
N
New Key Technology
newkeytech.com/blog/zero-knowledge
P
Private Shell Config
github.com/…/privacy-guides
S
Signal — Security Notes
signal.org/docs/personal-data
W
WireGuard Setup
wireguard.com/quickstart
🔒 AES-256-GCM 🧬 PBKDF2-SHA256 · 600k iterations 🚫 Zero telemetry ☁️ Encrypted cross-device sync 📖 100% open source 🪟 Side panel

Snoop through the storage.
See nothing.

Most "private" extensions just hide the list. SafeMark encrypts every byte. Here's what anyone with file access actually finds:

✕  Ordinary extension

The whole vault, in the clear — one read and it's gone
"smBookmarks": [
  { "title": "City Bank — Savings",
    "url":   "https://citybank…/account/9941",
    "added": 1729847 },
  { "title": "Ex dating thread",
    "url":   "https://reddit.com/r/…" }
]

✓  SafeMark

Ciphertext only — mathematically useless without your password
"smMeta":  { "iv": "a3F9…", "rev": 7, "parts": 4 }
"smHash":  "tude9lejfKy7EX8lCz…"
"smVault0":"8kDXqzWf2nTvM0ytBv…"
"smVault1":"J6rQeYwNp1aGhLxIo…"

Built like the data matters.

Because it does.

Sealed before it touches disk

600,000-iteration PBKDF2-SHA256 key stretching. AES-256-GCM encryption. Exponential backoff lockout.

The key stays in your head

Nothing to recover, nothing to leak. The AES key is derived fresh, non-extractable, lives in memory briefly.

Encrypted sync, done right

Mirrors through Chrome/Brave Sync as ciphertext chunks — merge across devices without ever exposing entries.

Docked side panel

Opens pinned to the right of your browser window. One click to seal the page you're reading. Always accessible.

Never locked in

Export your vault to standard Netscape bookmark HTML — importable back into Chrome, Brave, or any browser.

Open source, auditable

Every line of crypto and sync lives in a public repo. No obfuscation, no black box, no "trust us."

Install in 60 seconds.

Chrome, Brave, Edge, and any Chromium browser. Straight from GitHub — no store queue.

1

Download & unzip

Grab the zip from GitHub Releases and extract it anywhere.

2

Open extensions

Type chrome://extensions or brave://extensions and enable Developer mode.

3

Load unpacked

Click Load unpacked and select the unzipped SafeMark folder.

4

Seal it shut

Pin the shield icon, click it to open the side panel, set your master password. Done.

Forget the password & the vault is gone forever.

That's not a limitation — it's the entire point. There is no back door, no email reset, no server. Only reinstalling clears an empty, locked vault. Keep your password in your head — that's where the key lives.

I understand — let's seal it

See how it looks.

Sharp, dark, minimal — designed to stay out of your way while keeping your data locked tight.

Lock screen
SafeMark lock screen — password gate

Terminal-style password gate. Monospace font, amber CTA, zero fluff.

Vault
SafeMark vault with bookmarks

Encrypted bookmarks with sort, search, tags, and one-click save.

Docked side panel
SafeMark docked as a side panel in Chrome

Pinned to the right of your browser window — always one click away, never in the way.

Fair questions,
straight answers.

Can the developer read my bookmarks?

No. There is no backend, no API, nothing calling home. Data exists only inside your browser, encrypted. The code that does it is public.

What does Sync actually send?

Only ciphertext: salt, verifier, IV, and encrypted chunks. Chrome/Brave Sync streams it between your devices — nobody along the way sees a single bookmark.

I forgot my password. Now what?

The vault is unrecoverable — permanently. By design: anything that could recover it could also be stolen. Reinstall to start fresh.

Does it slow my browser down?

Key-stretching runs once at unlock. Browsing, saving, and searching are instant. The service worker is dormant between uses.