Skip to content

How your privacy works

AuraLeaf is private by default. It’s how the app works out of the box, not a setting you have to find.

  • Big platforms can’t. Your community lives on its own server, not a corporation’s. Your account exists only on that server.
  • The AuraLeaf developer can’t. The app never reports back on what you do: no usage stats, no tracking of any kind. If the project ever makes money, it will be from business licences, never from your data.
  • Even your own server can’t read your messages. DMs, group DMs and channel messages are end-to-end encrypted on your device before they leave it. The server stores only scrambled data and refuses anything else.
What How
DMs and group DMs Each message is sealed separately to each of the other person’s devices, with a fresh key every time. Your private keys never leave your device’s secure storage.
Channel messages Keys rotate. When someone leaves, keys change so they can’t read anything new. Whether new members can read earlier messages is your choice, in Settings › Privacy (on by default).
Voice and video Encrypted frame by frame. DM calls refuse to start without it. Voice channels use it by default.
The connection TLS, plus an extra encrypted layer per session that refuses to fall back to anything weaker.
Attachments and media on the server Stored encrypted.
Server backups Encrypted before they are written to disk.
The message cache on your device Sealed under a key kept in your system’s keystore.
  • No telemetry. There are no analytics or tracking tools in the app. The desktop app’s only outside call is checking for its own updates (plus optional spell-check dictionaries, and emoji packs an admin chooses to import).
  • Push notifications carry no content. The push service only gets a “wake up” signal, never the message, the sender or the channel name.
  • GIF search goes through your server. The GIF service sees the search words and a scrambled ID, never your account or address. The GIFs themselves load through your server too.
  • Link previews (on by default) are fetched through a blind tunnel on your server, so the linked site doesn’t see you.

What AuraLeaf does not claim:

  • Bots are the exception to end-to-end encryption. A bot has to read what you send it, so bot conversations are labelled as not end-to-end private.
  • Your server still runs the community. It knows who is a member, who is online, which voice rooms exist, and that a conversation happened. Encryption covers what you say, not the fact that you said something. It doesn’t make you anonymous to your own server.
  • Call keys are made by your community’s server. So the honest claim is that media servers and relays never see your calls unencrypted, not that your own server couldn’t.
  • The live database isn’t encrypted as a whole. The messages in it already are, one by one. Backups and stored media are encrypted too.