What Axon collects and why.

This Privacy Notice explains how Axon handles personal data when someone visits axon-bot.com, signs in to the dashboard, installs the Axon Discord application, uses an Axon command, or participates in a Discord server where an administrator has enabled an Axon feature. It does not replace Discord's own privacy notice. See Discord's Privacy Policy for Discord's processing.

Axon decides why and how it processes account, security, abuse-prevention, and service operations data. For server content that Axon processes only to carry out an administrator's configuration, the server operator may control that data and Axon may act as its processor or service provider, depending on the law and the facts. Members should usually direct server-content questions to that server's administrators first.

Dashboard account and sign-in data

When you sign in through Discord, Axon receives your Discord user ID, username, global display name, avatar reference, locale, OAuth scopes, and the servers Discord says you can manage. Axon stores encrypted OAuth credentials, hashed session and CSRF values, device user-agent text, sign-in results, and session timestamps. Axon does not receive your Discord password.

Plan and payment records

When a server buys a paid plan, Stripe collects payment details and sends Axon customer, checkout, price, subscription, invoice, refund, and payment-status identifiers needed to manage the subscription. Axon stores subscription state, billing interval, plan, renewal and cancellation state, grants, trial use, downgrade choices, and a hash of each webhook payload. Axon does not receive or store full card numbers or card security codes.

Server and member data

Axon receives server IDs, names, icons, owner IDs, channels, categories, roles, permissions, installation state, member totals, and bot totals. For access checks, moderation, member search, onboarding, roles, protection, Captcha, and similar enabled features, Axon may receive Discord user IDs, profile fields, server nicknames, role membership, join dates, account creation dates, bot status, voice-state metadata, and membership screening state. A full member inventory used to calculate member and bot totals is counted in memory and is not stored as a directory of every server member.

Feature content and records

The data depends on what a server enables. It can include module settings and revisions; command names and outcomes; moderation reasons, notes, evidence links, cases, appeals, and action results; ticket, application, modmail, suggestion, poll, announcement, template, custom-command, and automation content; reaction and role records; birthdays limited to month and day; leveling, economy, reputation, giveaway, reminder, temporary voice, starboard, and watchlist records; plus delivery and audit history.

Message handling

Axon can receive message content from Discord when a feature needs it, such as AutoMod, custom commands, automations, leveling, tickets, applications, modmail, suggestions, or transcripts. Axon does not build a general archive of server messages. Event Logging stores message IDs and delivery metadata, not deleted or edited message text. A feature may store submitted content when that content is the record the administrator asked Axon to keep, such as a ticket transcript, application answer, modmail reply, or moderation note.

Technical data

Axon records request and service timing, route paths without query strings, error codes, job and delivery state, container logs, sampled traces, and CPU profiles. Security filters remove authorization headers, cookies, OAuth codes, known secret fields, request bodies, URL credentials, and query strings from telemetry. The public site stores a local theme choice. Signed-in pages use cookies required for OAuth state, authentication, and CSRF protection; Axon does not use advertising cookies.

Axon processes data for the following purposes:

• provide the dashboard, Discord commands, and features a server enables;
• authenticate users and confirm current server permissions;
• deliver, retry, reconcile, and audit requested Discord actions;
• protect accounts, servers, members, and Axon from abuse or unauthorized access;
• diagnose failures, measure service health, and maintain backups; and
• comply with law, enforce the Terms, and respond to valid legal requests.

Where the GDPR, UK GDPR, or a similar law applies, Axon relies on contract when processing is needed to provide a requested account or service; legitimate interests for security, reliability, fraud prevention, and limited service measurement; legal obligation when law requires processing; and consent where the law requires consent. A server operator is responsible for choosing a lawful basis and giving any required notice for the features it enables for its members.

Axon uses first-party cookies that are required to sign you in securely and protect dashboard requests. It also stores preferences that you choose in your browser. Axon does not currently use advertising cookies, cross-site tracking, or optional audience-measurement cookies.

Required cookies cannot be disabled through a preference panel because the requested sign-in and security functions would stop working. If Axon adds optional analytics, advertising, or similar storage, it will update this notice and request consent before loading it where the law requires consent.

Axon sends data to Discord to perform the actions users and server administrators request. It also discloses data to infrastructure providers that host the public site, application services, database, cache, encrypted backups, monitoring, and error reporting. Those providers may process data only to provide contracted services, protect their systems, or meet legal duties.

Stripe processes payment and billing data when a server owner purchases or manages a paid plan. Stripe's own privacy notice applies to the information it collects as a payment provider. Axon shares the server ID, Axon purchaser ID, selected plan, and billing interval needed to connect the purchase to the correct server.

Axon may disclose information when required by a valid legal process, to protect someone from serious harm, to investigate abuse or security incidents, or as part of a merger, financing, acquisition, reorganization, or sale of the service. Any successor must honor this notice for data collected under it. Axon does not sell personal data, does not share it for cross-context behavioral advertising, and does not use Discord API data to profile people for employment, housing, insurance, credit, or similar eligibility decisions.

Axon keeps data only while it serves the purpose described here, a server's configured retention setting, a security need, or a legal obligation. The current service enforces the following operational windows:

• expired sessions and revoked OAuth records are removed 30 days after expiry or revocation;
• failed job results are removed after 7 days;
• health snapshots are removed after 30 days;
• dashboard sign-in history is retained for 90 days;
• owner-visible error reports are retained for 30 days;
• billing customer, subscription, refund, and payment records are retained while needed to provide the plan, resolve disputes, prevent fraud, and meet accounting or legal duties;
• protection incidents are retained for 180 days;
• Protection verification sessions are removed within 7 days after expiry;
• moderation cases are retained for the server's selected 30- to 3,650-day period; and
• ticket transcripts are retained for the server's selected 1- to 3,650-day period.

Configuration, audit, and server-owned records may remain while the server uses Axon so administrators can understand prior changes and actions. Removing Axon stops new Gateway collection but does not automatically erase records that a server still needs for audit, dispute, security, or legal reasons. An authenticated server owner can request whole-server deletion, subject to identity checks and any lawful hold.

Axon encrypts OAuth credentials, hashes session secrets, uses TLS in transit, limits dashboard access through current Discord permissions and Axon roles, separates public web traffic from private service origins, records sensitive changes, redacts telemetry, and encrypts production backups. No security program can guarantee that an incident will never occur.

If Axon confirms unauthorized access that creates a legal notification duty, it will notify affected users, server operators, Discord, and regulators as required. Do not send passwords, bot tokens, OAuth secrets, financial information, health information, or other unrelated sensitive data through Axon fields or support messages.

Signed-in users can review and revoke device sessions, download a JSON account export, and delete their Axon account from the Device sessions page. Account deletion revokes OAuth, removes sessions and personal preferences, unlinks membership records, and pseudonymizes the account. It does not let one person erase shared server configuration, moderation, ticket, or audit records that belong to a server or concern other people.

Depending on where you live, you may have rights to know, access, correct, delete, or obtain a portable copy of personal data; restrict or object to some processing; withdraw consent; and appeal a denied request. You may also complain to your local data protection authority. Axon does not discriminate against anyone for exercising a privacy right. Axon may verify your Discord account and request details needed to locate the record before acting on a request.

California residents may also ask for the categories, sources, purposes, and recipients of covered personal information. Because Axon does not sell personal information or share it for cross-context behavioral advertising, there is no sale or advertising-share opt-out to process under the current service model.

Axon is a general-audience service for people who meet Discord's minimum age rules and can lawfully agree to these terms. It is not directed to children under 13, and server operators must not configure Axon to collect data from anyone below the minimum legal age in that person's location. If Axon learns that it received personal data from a child in violation of these requirements, it will delete or restrict that data as required.

Axon does not need health, biometric, financial-account, government-identifier, precise location, or other highly sensitive data to provide the service. Users and server operators must not place that data in free-text fields, tickets, applications, notes, evidence, or custom content unless Axon has expressly approved that use in writing.

Axon and its providers may process data in the United States and other countries where they operate. Those countries may have different privacy laws. Where required, Axon will use an approved transfer mechanism, such as an adequacy decision or standard contractual clauses, and apply technical and organizational safeguards appropriate to the data.

Axon may update this notice when its data practices, features, providers, or legal duties change. The page will show a new effective date and version. If a change materially reduces user rights or expands how Axon uses previously collected data, Axon will provide additional notice through the dashboard, Discord, or another reasonable channel before the change takes effect when the law requires it.

Privacy and data requests can be sent to support@axon-bot.com. If your request concerns content controlled by a Discord server, include the server ID, record type, and relevant dates, but do not send credentials or unrelated private content. You can also use the support page for service help.

Axon currently operates under the Axon name. The operator's final legal name, postal service address, governing jurisdiction, and reviewed privacy contact must be published before paid or general availability. This disclosure remains a release requirement and is not replaced by the Axon trade name.