HTML files are fine for one-time moves. They are terrible for bookmarks that keep changing.
End-to-end encrypted bookmark sync
Different browsers. Same bookmarks.
Relay keeps Chromium-based browsers current with one end-to-end encrypted, zero-knowledge vault only you can unlock. No exports. No rebuilding folders. No readable cloud copy of your bookmarks.
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 annoying thing Relay fixes
Bookmarks should not turn into browser chores.
Most people do not live inside one browser forever. Work happens in one, personal browsing in another, testing in a third. Then bookmarks drift, folders get rebuilt by hand, and nobody knows which browser has the newest version.
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 sync without handing over a readable bookmark library.
How Relay works
One vault. Every Chromium browser you choose.
Relay reads the local bookmark tree, 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.
Privacy posture
Useful sync. Less data exhaust.
Relay is intentionally boring 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
Private by architecture. Verified in public language.
Relay's source repository is private to protect the product, but the security model is documented for users, reviewers, and future independent auditors.
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.
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 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. |
| Privacy tradeoffs feel vague. Sync can become another profile. |
Privacy is 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.