// PRIVACY
no ads. no tracking. no guessing.
What gets stored and where it lives and who can see it. In plain words.
// WHO CAN READ WHAT
it depends where you're talking
| where | what | who can read it |
|---|---|---|
| A community server | Messages and files in its channels. Voice and screen shares too. | The channel's members and whoever runs the server |
| The hub | Direct messages and the files sent in them. Calls too. | The people in the chat and the hub's operator. That's us. Direct messages the hub can't open are planned. |
| Your device | Search and your copy of your keys | Only you. Search runs locally over messages already on your device. |
All of it is encrypted on your device before it's sent. It stays encrypted on the server's disk. Who can read it comes down to who holds the key. How that works.
// WHAT A HOST CAN SEE
the details a server needs
Any chat server needs some basics to deliver messages and run calls. On top of the content it holds keys for a server sees these.
- connections
- Which address connected. When it arrived and when it left.
- names and keys
- Display names and the public half of each identity. That's how returning members are recognised.
- the layout
- Which channels exist and who is in which one. Which roles people hold.
- voice activity
- Voice is routed by sender. The server sees when someone spoke and roughly for how long.
- message times
- Each message is stored with its sender and the time it arrived.
- traffic size
- How much data is moving over time. Voice slices are close to a fixed size so size alone says little.
// YOUR HUB ACCOUNT
what the hub keeps
- your account
- Your username and your identity sealed with your password. Your email address too. Email is only used to confirm it's you and to help you get back in.
- friends and profile
- Your friend list and requests. Your profile and status and whether you're online. You choose whether people can find you by username. You can also appear offline.
- your servers
- The list of servers you've joined. A new device opens where you left off.
- messages and calls
- Direct messages are stored encrypted. Calls are relayed encrypted. The hub holds their keys today as the table above says.
// NEVER
what veiled doesn't do
- tracking
- None. No analytics and no crash reports and no ads. That goes for the app and this site.
- outside requests
- The app and this site load their fonts and scripts and images from their own server. No CDNs. No pixels.
- update checks
- The desktop app fetches a small update file from veiled.contact when it opens and every six hours. The request carries no ID and nothing you've written.
- cookies
- This site sets none. Your theme choice stays in your browser. The web server keeps normal access logs for a short while.
// YOUR CALL