The list
Relic's sync servers hold your items in a form nobody there can open. They still hold a handful of plain facts, because sync and billing cannot run on nothing at all. Here is the whole list, in both directions.
What the servers hold
- Your email
- The address you signed up with, used to sign you in and to email you about your account.
- Your devices
- How many there are and the names you gave them, like Windows PC or Pixel 9.
- Sync times
- When each device last synced.
- Item ids
- A random id per item, so the same item can be matched across your devices.
- Times and sizes
- When each item was made, when it last changed, and how many bytes it takes up.
- Kept or not
- Whether you put an item in your Vault. The server needs this to know what it may never delete.
- Space used
- The total of those sizes, to enforce the limits on your plan.
- Billing status
- Which plan you are on and whether it is paid up. Stripe handles the payment, and Relic never receives your full card number.
What the servers cannot read
- Your content
- The text, the images and the files you save.
- Your words about it
- Titles, notes and tags, whether you wrote them or Relic suggested them.
- What you look for
- Searches never leave the device. There is no search server to send them to.
- Your keys
- Your vault passphrase, the key it makes, and your recovery kit. None of them are ever sent.
The formal version of this is in the privacy policy, which also names every company that handles any part of it.
Why the server needs those facts
Each one earns its place:
- Ids and times put your items in order and let a device ask for only what it has not seen yet.
- Sizes add up to the space you are using, which is what the limits on a plan are counted in.
- Kept or notis the one that gives something away. Relic's free plan lets go of old unsaved history, so the server has to know which items you chose to keep and must never touch. It sees which items you keep. It never sees what they are.
Everything else about an item, including its kind, lives inside the sealed part. How encryption works walks through the sealing itself. If you would rather no company held even this much, you can run the sync server yourself, or use Relic on one computer with sync switched off.
What the models on your device see
Relic names items, tags them, reads the words in screenshots and works out what things mean, and all of that reads your content in full. It also all happens on your own machine. The models are files Relic downloads once and then runs locally. Nothing you copy is sent to a cloud AI service, and there is no setting that would make it so.
The privacy policy puts it the same way: tagging, reading screenshots, captioning, and search all run locally on your device, and nothing you copy is sent to a cloud AI model.
You can switch each part off. The Search and AI settings cover the individual switches.
What a share link exposes
The item is sealed on your device before it is uploaded, and the key rides in the part of the address that browsers never send to a server. So the server still cannot read a shared item. The person you send the link to can, and so can anyone they forward it to, until it expires. Sharing one item never exposes anything else in your vault. See share links and QR codes for the expiry choices and the one-time option.
Analytics
The Relic apps carry no analytics and no crash reporting service. Nothing counts what you copy, what you search for, or which buttons you press, and there is nowhere for such a report to go.
The website is a separate thing. relic.space measures ordinary page visits the way most websites do, and the privacy policy says which tools it uses. That is about pages on a website. It has no connection to what is in your vault.
The About pane has a Copy diagnostics button that puts a short report about your install on the clipboard for a support email. You choose when to press it, you can read what it says before you send it, and it never contains anything from your vault.