← ALL ARTICLES
ANONYMITY

No email. No account. No reset.

Signing up is so normal that it is hard to notice it is a choice. A sync service needs somewhere to put your data and a way to find it again. Neither of those requires knowing who you are.

8 NOVEMBER 20266 MIN READ

The short version

  • An account is an identity, and identities leak. Email plus password means a breach target, a marketing list, and a reset flow somebody else can abuse.
  • A sync ID is just an address for an encrypted store. Anonymous, not derived from anything about you, and useless to anyone without your password.
  • What you gain: nothing to sign up for, nothing to verify, nothing to delete, and no way for us to correlate you with anything.
  • What you lose: the safety net. No password reset exists, because no one holds the key — so the sync ID and password are yours to keep safe.
01

What an account is actually for

Strip away habit and an account on a sync service does four jobs:

  • It gives your data an address, so the service can find it again.
  • It authenticates you, so somebody else cannot read it.
  • It provides recovery, so a forgotten password is survivable.
  • It gives the company a customer record — for support, for billing, for analytics, for email.

Only the first two are things you wanted. The third is genuinely useful and, as we will get to, impossible to combine with end-to-end encryption. The fourth is entirely the company's business, and it is the reason the email field is mandatory on services that have no need to ever contact you.

02

The cost of the account you did not need

It is a permanent identifier

An email address is the join key of the modern web. The same address on a bookmark service, a shopping site and a breached forum links all three together, forever, including in datasets assembled by people you have never heard of.

It is a breach target

A service with a hundred thousand accounts holds a hundred thousand email addresses, and that table is worth stealing on its own, independently of whatever it is attached to. A service with no email addresses cannot lose any.

The reset flow is a way in

Password recovery is, by definition, a mechanism for granting access to someone who does not know the password. It is also the most commonly attacked part of any authentication system, through mailbox compromise, SIM swapping or support-desk social engineering. Its existence is a standing risk.

It makes your metadata legible

Even with your content encrypted, an account turns every sync into a dated, attributable event: this person, this IP, this often, this much data. That is a profile, and it is built entirely out of things that are not your bookmarks.

03

How a sync ID works instead

MarkSync replaces the account with two things.

A sync ID is an anonymous identifier for an encrypted store. It is generated when you first set up, it is not derived from your name, your email address or anything else about you, and it contains no personal information. Think of it as the address of a locker rather than a username.

Your password never leaves your device. It is what encrypts your bookmarks before they are sent, and what decrypts them when they come back. The service never receives it and has no hash of it to crack.

Together they are what you need to reach your bookmarks from a new browser: enter the ID, enter the password, and the extension pulls the blob and opens it locally. There is no sign-up step because there is nothing to sign up to — the first sync creates the store.

Note what this means for the operator. They hold an opaque blob at an anonymous address. They cannot read it, cannot tell you who it belongs to, and cannot be compelled to produce anything more interesting than the blob itself. The privacy policy says the same thing at greater length, which is less impressive than the fact that the code is open and you can check.

04

The trade-off, stated honestly

This is the part that other projects soften, and it should not be softened.

If you lose your password, your bookmarks are gone. Not "gone pending a support ticket" — gone. We hold no account and no copy of your password, so there is nothing for us to reset and no key for us to recover with. The same applies to the sync ID: without it, we cannot find your store, and we have no way of proving which one was yours.

This is not a missing feature. It is the direct consequence of the guarantee: a service that can restore your data after you forget your password is a service that could read your data all along. You can have recoverability or you can have end-to-end encryption. Anyone offering both has quietly kept a key.

05

What to do about it, practically

  • Put the sync ID and password in a password manager, now, as a single entry. They are credentials, and the ID is as important as the password.
  • Write them down somewhere physical if the collection matters to you. A piece of paper in a drawer has a better uptime record than most cloud services.
  • Export a backup periodically. The extension will produce a file; keeping one is the difference between an inconvenience and a loss.
  • Do the second-device setup while you still have the first. Adding a browser is the moment to confirm the credentials actually work, rather than discovering a typo a year later.
  • If you are self-hosting, back up the server too. An encrypted blob you no longer have is as unreadable as one you cannot decrypt. Running your own moves that responsibility to you, which is the point.

For why the encryption is worth this much inconvenience in the first place, see what a bookmark collection says about you. For what happens when the operator rather than the password disappears, see the service shut down.

Keep reading