Privacy
What we hold, and what we could not hold if we wanted to
Last updated 14 October 2026. This describes opensync.network, the relay at relay.opensync.network, and nothing else. A relay you run yourself is governed by you.
This website
No analytics, no tag manager, no third-party script, no cookie. The page loads its stylesheet and its three font files from this domain and makes no other request — you can confirm that in your browser's network panel, which is a better assurance than this sentence.
The web server keeps ordinary access logs: IP address, time, path, the site that linked here (its name only, not the full address), user agent, response code. They exist to diagnose faults and to notice abuse, they are not joined to anything else, and they are discarded after 90 days.
The relay
The relay stores exactly three things about an account, because they are the three it needs to do the job:
| What | Why |
|---|---|
| Encrypted bytes | It is a store. It has no key for any of them. |
| A public key | It is how a write is checked against an account, and how the storage allowance is counted. |
| Sizes and arrival times | A consequence of storing bytes. Used to enforce the allowance and to sweep things that have expired. |
It does not hold your filenames, your folder structure, your file contents, or the mapping between blobs and files. Those are inside a sealed manifest, and the manifest is encrypted with the same key as everything else — a key generated on your device that is never transmitted, in any form, at any point.
There is no email address, no password and no account page, because there is no login and no signup. An account is a keypair your first device generated, and the relay serves it without ever being told about it — so there is no registration record, because there was no registration.
What encryption does not hide
A relay can always see that an account is active, roughly how much it stores, and the times at which it writes. That is true of every end-to-end encrypted sync service, ours included, and any product claiming otherwise is describing something it has not built. If that metadata matters to your situation, run the relay yourself — that is why it is one binary rather than a platform.
Other people
The relay runs on a server we rent, so that provider can physically reach the disk the ciphertext sits on. There is no analytics vendor, no advertising network, no CDN in front of this site, and no payment processor, because nothing here is paid for.
Leaving
Change the relay URL in your apps and they stop talking to us. To remove what is stored, mail hello@opensync.network with the account's public key — the npub1… in any app's settings, which is the public half and safe to send — and it and its blobs are deleted.
The honest caveat, which applies to every service of this kind: deletion on a server is a request you make of its operator. The removal that does not depend on anybody's goodwill is a key rotation, which re-seals your data under a new key and leaves whatever the relay still holds unreadable to everyone, us included.
Children
This is not directed at children under 13, and we have no way to know who anybody is.
Changes
If this page changes materially, the date at the top changes with it. There is no mailing list to notify, because we do not have your email address unless you sent it.