Privacy Policy

01 What This Covers

This policy explains what XO ("XO", "we", "us") collects when you add the XO bot to a Discord server, why we collect it, and how to get rid of it. It covers the bot and this website.

Discord is a separate service with its own privacy policy. XO is an independent third party and is not affiliated with Discord Inc. What Discord itself collects when you use its platform is governed by Discord's policy, not this one.

02 Who Controls Your Data

If you add XO to your server, you are the controller of the data described in this policy for that server. You decide why your community exists, what data it holds, and how long it is kept. We act on your instructions as the processor that runs the bot.

You are responsible for having a lawful basis to collect and use your own members' data, for telling your members that XO is present, and for handling any request from one of them. We are the controller only of the limited operational data in section 3, such as which servers run the bot and how to reach you.

03 What We Store

XO keeps two small files. That is the entire storage footprint of the service.

Per server: what you bound, and how you configured it

• The Discord IDs of the channels and roles you pointed XO at with .xopick — for example your logs channel, your jail, your verify channel.
• Your consent decisions: whether protection was activated, whether XO may create roles, and whether decoy channels were allowed.
• Your detection thresholds, such as how many channel deletions in how many seconds count as a nuke.
• The original permission overwrites of every channel and role XO changed, kept only so that .xodeactivate can hand your server back exactly as it found it.

Per server: a recorded layout, so a nuke can be undone

While XO is running it continuously records the shape of your server so it can attempt a rebuild if one is destroyed. That record contains:

• Channel and category names, IDs, types, and positions.
• Permission overwrites — who could see, speak in, or manage each channel.
• Role names, colours, positions, and which permission flags were set.

It is a structural map, not a copy of your community. It contains no messages, no attachments, no member list, and nothing about who said what.

Identity, for consent and for reaching you

• Your server ID, and the server owner ID, so XO can confirm that only the owner activates or deactivates protection.
• Your Discord user ID, if you are the operator, so we can message you when something needs your attention.
• The IDs set as bot operators. Only these accounts can press the setup buttons or open the setup walkthrough.

The shared known-nuke-bot database

XO can hold a small community-shared list of malicious bots. An entry is two numbers: the flagged bot's user ID and the ID of the person running it, filed by a server that saw it in action. It contains no message content, no server names, and no member data. Removing a bot from your server does not delete entries other servers contributed, because they were contributed by those servers for their own safety.

04 What We Never Store

• No message content. Spam and duplicate-message detection looks only at recent messages, only in memory, and only for the length of a short rolling window. That window is never written to disk and is gone when the bot restarts.
• No member profiles. We do not build a list of who is in your server, and we do not profile members across servers.
• No private messages. Anything you DM to the bot is handled in the running process and not persisted.
• No payment card details. Payments are handled by our payment provider; we receive only a transaction reference and an amount.
• No credentials at rest. The bot token is never written to a file, repository, or log that we control.
• No advertising, no analytics trackers, and no selling. This website sets no cookies and runs no third-party tracking.

05 XO's Automated Responses

XO makes automated judgements to keep a community safe: that a burst of channel deletions looks like a nuke, that a new account is probably part of a raid, that a message repeats one posted seconds earlier, that an account matches a known-malicious bot. These are rule-and-threshold decisions made in the running bot, not a profile of your members.

What happens to those responses:

• The decision itself is not kept. It exists in memory for the length of the detection window and is not written to disk.
• The action is visible to you, in your server. Bans, quarantines, lockdowns, and role removals happen in Discord and appear in your own server's audit log.
• The alert is posted to you. XO writes what it did into the alert channel you bound, so your staff sees every automated action and can reverse it.
• No member is judged by us across servers. A judgement is made inside your server, for your server.

Automated decisions are not infallible. They can be wrong, and the ToS section on automated actions explains what happens when they are.

06 Why We Store It

• Your bindings and configuration — so XO knows which of your channels and roles it is allowed to act on, on every restart, without asking again.
• The recorded layout and original overwrites — so a destroyed server can be rebuilt and so deactivating XO genuinely returns your server to how it was. Without these we could not provide the core service at all.
• Owner and operator IDs — so that only the people who control a server can switch protection on and off.
• The nuke-bot entries — so every server guarded by XO benefits from a malicious bot being reported once, by anyone.
• Operational logs — short-lived records of the bot starting, stopping, and failing, kept on our host for security and to diagnose faults. These contain no community data.

We do not use your data for advertising, profiling, model training, or unrelated analytics.

07 Where It Lives

Stored data is held on infrastructure we operate, in the region the bot is hosted in. The per-server file and the nuke-bot list are plain JSON on the host's disk, reachable only by the operator of the service.

Data is kept for as long as XO is installed in your server. It is not moved between providers, sold, or handed to advertisers — there are none.

08 How to Make Us Forget

You are in control, and you have three options, in increasing severity:

1. Run .xoreset in your server. This immediately wipes the stored bindings, thresholds, consent flags, and the recorded layout for that server. Protection stops. There is no way for us to recover it afterwards.
2. Remove XO from the server. Discord revokes the bot's access immediately, so collection stops at once. The stored record for that server remains with us until you ask us to delete it, because we can no longer receive a command from you.
3. Ask us to delete it. Tell us in the support server named in section 14 and we will remove the stored record for your server, and confirm when it is done.

A .xoreset or a deletion request does not remove nuke-bot entries contributed by other servers, which are not your data. To dispute one of those, say so in the support server.

09 Who We Share It With

We do not sell, rent, or trade your data. We share it only with:

• Discord, to the extent required to operate the bot — reading your server's structure, posting alerts, and taking the actions you authorised. Discord's own handling of that data is covered by their privacy policy.
• Our payment provider, if you buy a plan, limited to processing the payment. We never see or store your card number.
• Nobody else, unless we are legally compelled to, and then only what the law requires.

We do not use third-party analytics, advertising networks, or data brokers on either the bot or this website.

10 Security

We use reasonable technical and organisational measures to protect stored data: access limited to the service operator, transport encryption in transit, and no token or credential written to disk. We will notify affected server owners of a confirmed data breach through our support server without undue delay.

Be honest about the limits: the stored layout is a structural map of your server, and the files on our host are not encrypted at rest. Anyone who obtains access to our host could read them. We think that is the right trade for a service that never holds your messages, and we would rather state it than imply otherwise.

11 Children's Servers

XO is not directed at children, and the service is not intended for use by anyone under 13 or the minimum age in their country. If you run a server intended for children, you are the controller of that data and you are responsible for operating XO lawfully on their behalf.

12 Your Rights

Where the privacy law that applies to you gives you rights over this data — for example the GDPR or equivalent — you have the right to:

• Access — ask what we hold for your server. We will give it to you, and it is mostly the content of the commands you already ran.
• Correct — re-run .xopick to repoint a binding, or .xoreset to start clean.
• Delete — as described in section 8.
• Object or restrict — ask us to stop processing where you have the right to object, and we will discuss it.
• Complain — to your local data protection authority.

To exercise any of these, contact us through section 14. We respond within 30 days. We do not charge for a reasonable request.

13 Changes to This Policy

We may update this policy. The date at the top of the page shows when it last changed. If a change materially increases what we collect or what we share, we will announce it in our support server before it takes effect. Continuing to use XO after a change means you accept the updated policy.

14 Contact

Privacy questions, access requests, and deletion requests go to our support server at discord.gg/Z3K3ny6Rxk. Please include the server id and what you are asking about, and we will pick it up from there.

This policy should be read alongside our Terms of Service, which cover the limits of the service itself.