Your bookmarks are a profile.
Nobody thinks of a bookmark folder as sensitive. Then you read one back — the clinic, the lawyer, the salary calculator, the job board, the dating advice — and realise it is a diary that writes itself.
The short version
- Bookmarks are unusually revealing. They record intent, not just traffic: the things you meant to come back to, with dates and folder names you chose yourself.
- "Encrypted" usually means encrypted at rest. The provider holds the key, so the data is protected from a stolen disk — not from the provider.
- End-to-end encryption moves the key to you. The server stores something it cannot open, which changes what a breach, a subpoena or a curious employee can yield.
- MarkSync encrypts on your device before anything is sent. The service holds an opaque blob and an anonymous ID — and the cost of that is that nobody can recover your password for you.
Why this data is worse than it looks
Browsing history is a record of where you went. A bookmark is a record of what you intended to come back to, which is a stronger signal and a much smaller, cleaner dataset. It is pre-filtered by you into the things that mattered enough to save.
Read a stranger's bookmarks and you would learn, in a few minutes: roughly what they do for a living and whether they are looking for a new job; which medical conditions they or a family member are dealing with; their financial position, down to which mortgage calculator they used; their politics; what they are shopping for; whether their relationship is in trouble. Folder names make it easier, because people name folders honestly — nobody calls a folder "Topic 4" when "Divorce" is what it is.
Add the timestamps and you get a chronology. The order in which someone saved three links can be more revealing than the links themselves.
The word "encrypted" is doing a lot of work
Almost every sync service will tell you your data is encrypted, and almost every one of them is telling the truth. The question that the sentence leaves out is who holds the key.
Encryption at rest
The data is encrypted on the provider's disks, with keys the provider manages. This is real security and it is worth having: it defends against a stolen drive, a decommissioned server, a misconfigured backup bucket. What it does not do is put your data out of the provider's reach. Their application decrypts it routinely, because it has to in order to serve it back to you.
So encryption at rest protects your bookmarks from everyone except the party holding them, and anyone who can compel, breach or socially engineer that party.
End-to-end encryption
The data is encrypted on your device, with a key derived from something only you know, before it is transmitted. The provider receives ciphertext and stores ciphertext. There is no moment in the pipeline at which the server holds readable bookmarks, because it never has the key.
The practical difference shows up in the scenarios that actually happen:
| Scenario | Encrypted at rest | End-to-end encrypted |
|---|---|---|
| Stolen or discarded disk | Protected | Protected |
| Database breach of the live service | Attacker may get readable data | Attacker gets ciphertext |
| Legal demand for your records | Provider can comply with readable data | Provider can hand over only ciphertext |
| Curious or malicious employee | Access is a matter of policy | Access is mathematically unavailable |
| Service changes its mind about ads | Data is available to mine | There is nothing to mine |
The quiet second problem: the account
Even a service that never reads your bookmarks usually knows exactly who you are, because you signed up with an email address. That email ties your bookmark store to your identity, to every other service using the same address, and to a password reset flow that is, by design, a way for someone other than you to gain access.
Encryption without anonymity leaves a pattern that is informative on its own: who you are, when you sync, from which IP, how much data you keep, how often you add to it. That is a behavioural profile assembled entirely from metadata.
How MarkSync handles it
MarkSync encrypts your bookmarks on your device, with a password only you know, before anything is sent anywhere. What reaches a sync service is a blob it cannot open. Decryption happens on your device too, when you pull.
There is also no account. You are identified by a sync ID — an anonymous identifier for an encrypted store, not derived from your name, your email address, or anything else about you. We never ask for an email address, which means we cannot leak one, sell one, or reset a password with one. That design, and its consequences, is the subject of sync without an account.
The code is open source under the GPL-3.0, so none of this requires taking our word for it, and if you would rather not trust anyone else's server at all, you can run the service yourself. Our own privacy policy is short enough to read in full, and it lists every request the site makes to someone else's server.
The price of the guarantee: because we hold no account and no copy of your password, we cannot reset it and we cannot recover your bookmarks if you forget it. A service that can rescue you from a forgotten password is, necessarily, a service that can read your data. You cannot have both. Back up regularly.
What to ask any sync service
- Can you read my bookmarks if you want to? If the answer is anything other than a plain no, assume yes.
- Where is the key derived? On my device, or on your server?
- What identifies my store? An email address, or something anonymous?
- What happens if I forget my password? A reset link means somebody else can get in.
- Can I read the code, and can I run the server myself? If not, every other answer is a promise rather than a property.