Zero-knowledge bookmark sync
Your bookmarks, current everywhere.
Relay keeps Chrome, Edge, Brave, Arc, Opera, and other Chromium browsers aligned through one end-to-end encrypted vault, with preview, cleanup, undo, library health, and profiles built into the extension.
No email account
Zero-knowledge vault
No analytics SDK
Independent review planned
Product ideas
Reading list
Travel plans
↔
Zero-knowledge vault
Only your password unlocks it
↔
Chrome, Edge, Brave+Current across browsers
Synced
Readable cloud copyNot stored by Relay
Nope
Product ideas
Reading list
Travel plans
The workflow Relay upgrades
Bookmarks should move at the speed you work.
Most people do not live inside one browser forever. Work happens in one, research in another, testing in a third. Then bookmarks drift, folders get rebuilt by hand, and nobody knows which browser has the newest version.
HTML files are fine for one-time moves. They are terrible for bookmarks that keep changing.
Chrome, Edge, Brave, Arc, Opera, and other Chromium browsers all support bookmarks, but they do not keep each other current.
Relay is built for people who want continuity without handing over a readable bookmark library.
How Relay works
One vault. Every Chromium browser you choose.
Relay reads the local bookmark tree, checks library health, encrypts the vault in your browser, and syncs only the encrypted result. Sign in from another supported browser and Relay brings the missing bookmarks across. Use bookmark profiles when one browser should switch between work, personal, or project-specific sets.
Create a vault
Choose a username and save the generated password. No email account required.
Sync from one browser
Relay encrypts the bookmark vault before it reaches the server.
Sign in elsewhere
Use the same username and password. Relay decrypts locally and keeps the browser current.
Dashboard
The extension shows what is going on before you act.
The redesigned Relay popup keeps everyday controls close: sync status, library health, Preview, Clean, Undo, profiles, add-browser steps, and settings all live in one clear flow.
Relay scans the local browser for exact duplicates, unsupported URL schemes, unsorted bookmarks, and folders that have gone quiet.
Check what Relay would add to this browser before pressing the main sync button.
Remove exact duplicate bookmarks with a local undo point ready if you want the previous state back.
The framework
A sharper boundary between browser and cloud.
The most important part of Relay is not a feature button. It is the line it keeps clear: readable bookmarks belong in your browser, not on Relay's servers.
The browser does the smart work.
Relay handles bookmark reading, health checks, duplicate cleanup, folder normalization, profile switching, encryption, decryption, and restore locally before anything touches the network.
- 1Password-derived key stays local.
- 2Bookmark folders and profiles are preserved as structured data.
- 3Unsafe restore payloads are rejected before they can become bookmarks.
The backend stays intentionally focused.
Relay moves encrypted vault data, enforces ownership, applies plan limits, redeems Pro gift codes, and protects sync APIs. It is infrastructure, not a readable bookmark database.
- ✓Encrypted vault blobs and restore metadata.
- ✓Rate limits, browser limits, and ownership checks.
- ×No analytics SDK, no content scripts, no readable bookmark library.
Common setups
Built for people who do not live in one browser.
Relay is clearest in the messy real cases: work in Chrome, research in Brave, testing in Edge, and project-specific profiles that should not melt into one folder pile.
Chrome for work, Brave for personal
Keep the same useful bookmark memory without signing every browser into the same identity system.
Profiles for projects
Switch between work, personal, research, and client contexts, delete unused profiles, and keep restores scoped to the active profile.
Quiet sync after setup
Preview changes, sync what is missing, and keep result messages visible long enough to understand what Relay just did.
Data posture
Useful sync. Less data exhaust.
Relay is intentionally disciplined about data collection: no email identity, no analytics SDK, no tracking profile, and no plaintext bookmark library on the server.
It derives the local encryption key. Relay cannot reset it, because Relay does not have it.
The server stores the encrypted result and operational sync records, not a decryption key or readable copy of bookmark contents.
Trust center
Protected by architecture. Explained in plain language.
Relay documents the security model and trust boundary for users, reviewers, and future independent auditors, with claims written to match real product behavior.
Plain-English details on encryption, permissions, metadata, data deletion, and what Relay cannot read.
Relay is preparing an extension-focused security review. Audit summaries will be published only after they are complete.
Normal installs go through the Chrome Web Store listing, with browser-managed updates and platform review.
Sync guides
Pick the bookmark sync problem you actually have.
Keep Chrome aligned with your other Chromium browsers.
Use Brave without rebuilding folders by hand.
Keep Edge current for work and testing.
Understand the vault before trusting it.
Sync bookmarks without using an email identity as the account base.
Start with the browser store and set up Relay from the extension.
What changes
From bookmark babysitting to quiet sync.
| Before Relay | With Relay |
|---|---|
| Export, import, repeat. Manual files age the moment another bookmark changes. |
Sync from the browser. Relay previews, compares local bookmarks with the encrypted vault, preserves folders, and adds what is missing. |
| One browser gets messy. Bookmarks are current in one place and weird everywhere else. |
Browsers stay aligned. Use the same vault across supported Chromium browsers. |
| Trust tradeoffs feel vague. Sync can become another profile. |
Trust is built into the product shape. No email account, no analytics SDK, no readable cloud copy. |
Ready when you are
Give every browser the same bookmark memory.
Install Relay, create an end-to-end encrypted vault, and stop manually moving bookmarks around like it is 2009.