Transparency

You are about to give a bot access to your server's messages and — if you enable web verification — to the IP addresses of everyone who joins. Wanting to know exactly what it does with that before you accept is reasonable. This page explains it without legal language.

What Axis cannot see

This is not a promise: it is what the code does not do and what Discord does not allow.

• Your private messages. The first line of the message handler discards anything that does not come from a server. Even if you DM the bot, nothing is stored or forwarded to anyone.
• Other servers. Every server is isolated. What one server's staff sees in their logs belongs to their server and to nobody else.
• What you say in voice. Discord does not give audio to bots. Axis only sees that you joined a voice channel, never what was said in it.
• Your screen, your camera, your files. None of that ever reaches a bot.
• Your Discord password. The verification portal uses Discord's own login: your password is typed into Discord, not here, and never passes through our server.
• Your phone number, email, age or ID. Never requested, never stored. Not once.

What is stored, and for how long

• Sanctions and moderation records: for as long as the bot is in the server. That is the history staff needs.
• A hash of your connection (web verification only): 90 days, then deleted automatically. It is an irreversible hash: it can tell whether two accounts come from the same place, but your IP cannot be recovered from it. Exception: if that connection is sanctioned in a server, its trail is kept for as long as the sanction lasts — if it expired, waiting it out would be enough to come back on another account.
• Edited or deleted messages: logged for auditing. A message nobody touches is not stored.
• Joins, leaves and name changes: public server activity.

What we never do

• We do not sell or share data. No advertising, no commercial profiling, no third parties looking in.
• We do not train artificial intelligence on what happens in your server.
• We do not spread your bans to other servers. If you IP-ban someone on your server, they stay banned on your server. Every community decides who it throws out; turning a local ban into a global one would hand any admin the power to remove people from communities that are not theirs.
• We do not post in your server unless you ask. No announcements, no updates: you have to turn it on yourself with /updates.
• We do not publish which servers use Axis. To anyone looking for a target, a list of "protected servers" is a list of targets with the defence already identified. All you will ever see are the aggregate figures above.

What not even the staff can do

Most bots protect a server from outsiders. The uncomfortable part is that a good share of disasters are caused by someone who already had permissions.

• Erase their own tracks. The audit log is chained: every event carries the signature of the previous one. If someone edits or deletes a row straight in the database, the chain stops adding up and it shows. Any admin can check with /audit verify.
• Act alone on the irreversible. The most dangerous actions can require two different people to confirm them. Whoever proposes one cannot approve it.
• Stay out of the log. The bot owner's actions are recorded exactly like everyone else's.

How to check it yourself, without trusting us

• /my-data — everything stored about you, sent to your DMs. There is no "user-facing" version and a real one.
• /delete-my-data — requests deletion of what can be deleted. Your connection hash and any sanctions in force cannot: if they could, the right to be forgotten would be a button for dodging bans.
• /audit verify — checks that nobody has tampered with the log.
• /protection — tells staff which defences are configured and which are not, with no sugar-coating.
• Service status — if the bot is down, that page says so; it is not hardcoded green.
• Signed attestations — this is the one that does not depend on us. Every hour the log height and the hash of its last entry are signed with an Ed25519 key. Download two from different days: if the log now told a shorter story than it did then, the older attestation gives it away — and it is signed. The public key ships in the same file.

If you remove the bot

It stops receiving any data from your server immediately. Records that already existed stay stored in case you add it back (losing your sanction history on reinstall would be a silly way to grant everyone an amnesty). If you want them genuinely erased, ask on the support server and it will be done.

Who is behind it

Axis is maintained by one person, on a dedicated server — not on somebody's home computer. There is no company behind it, no investors, and no data-sharing arrangements with anyone. For any question, complaint or deletion request: support server.