Privacy policy

Astri protects Discord servers from nukes and raids. To do that it keeps a record of what happens in each server it's in. This page explains what, why, for how long, and what you can do about it.

Last updated 17 October 2026

Summary

Astri stores what it needs to spot and undo attacks: who joined and when, audit log entries, risk scores, and evidence for each incident.
It doesn't keep the text of messages, except messages posted in a honeypot channel, which is labelled as a trap.
Most data is deleted after 30 to 180 days. Everything about a server is deleted 30 days after Astri is removed from it.
One thing crosses servers: your account standing. If Astri automatically contained your account in other servers, staff of servers you join are told, without naming those servers. You can see your standing and ask for a human review.
Servers whose owners join an Astri Network share raiders and nukers with each other, and their staff see which server an action came from.
Nothing is sold, rented or used for advertising or profiling for marketing. There are no tracking cookies.
You have rights under the GDPR, including access, correction, deletion and objection. See your rights.

Who's responsible

Astri is run by a private individual, known as Noahtarp, based in the Netherlands ("we", "us"). For the processing described as ours below, we are the controller under the EU General Data Protection Regulation (GDPR) and the Dutch GDPR Implementation Act (UAVG). You can reach us as set out under contact. We are not required to appoint a data protection officer and have not done so.

Astri isn't made by, endorsed by or affiliated with Discord. Discord's own handling of your data is covered by Discord's privacy policy, not this one.

Servers and Astri

Who decides what happens to your data depends on what it's used for:

Protecting and moderating one server. A server's owner and staff choose to add Astri, choose its settings and decide what it does in their server. For that server's own records (joins, incidents, cases, appeals, backups, settings) the server's owner is the controller and we process the data on their behalf, under the data processing terms in our terms of service. Questions about how a server moderates you are best sent to that server's staff first.
What we decide ourselves. We are the controller for account standing, the Astri Network, the website and its sign-in, verification on the website, abuse prevention, operator records and keeping the service secure and working.

Either way, you can contact us and we will help, or pass your request to the right server owner and tell you we did.

What the bot stores

For each server Astri is in:

Data	What's in it	Kept for
Join records	Member ID, when they joined, when their account was made, whether it's a bot, a simplified form of the username, the avatar ID and the invite used	30 days
Avatar fingerprints	A short numeric fingerprint of each avatar image, for spotting look-alike accounts. Not linked to a member by itself	30 days after last seen
Invite counts	How many members joined through each invite, and how many of them were flagged	30 days after the last join
Audit log entries	Who changed what in the server (channels, roles, bans, permissions), as Discord's audit log reports it	90 days
Risk scores	A score for recent members and the signals behind it	Until the score has stayed low for 7 days
Incidents	What Astri saw and did: member IDs and usernames, the signals, each action and its result, and honeypot messages (below). Includes enough to undo each action, such as the roles it removed	180 days after the incident is closed
Server snapshots	The server's channels, roles, permissions and their images, so a nuke can be compared with how things were and rolled back. No messages or members	Every save for 48 hours, one a day for 30 days, changes for 14 days
Settings	The server's Astri settings, its trusted and whitelisted members, and who changed a setting and when	Settings while Astri is in the server; the change history 90 days

Member IDs, usernames and avatars come from Discord, through the access a server gives Astri. Astri doesn't collect members' email addresses, phone numbers, real names or anything from outside Discord. It doesn't try to work out sensitive things such as health, religion or politics, and we ask staff not to put them in moderation reasons.

Messages

Astri looks at new messages as they arrive, to spot raid spam such as the same text from several new accounts, or a link straight after joining. For that it keeps a one-way fingerprint of the text, its length and how many links and invites it has, for a short time. The text itself is not stored.

The honeypot channel is different. It's labelled as a trap, so anything posted there is treated as evidence: Astri keeps the first 500 characters and the number of attachments in the incident. Attachments themselves are not saved.

Astri doesn't read direct messages, and doesn't store message edits or deletions.

Moderation tools

When a server's staff use Astri's moderation tools, it also keeps:

Cases: each warning, timeout, kick or ban staff make through Astri, who made it, and the reason they gave. Kept while Astri is in the server, so staff can see a member's history.
Removed members: for members banned or kicked, their past usernames and an avatar fingerprint, to spot them coming back on a new account. 180 days.
Watchlist: members staff asked to keep an eye on, with a reason, until the date staff set.
Appeals: what you write when you appeal an action, and the outcome. 90 days after it's decided.
Verification: who is waiting to verify in a server, until they do or leave.
Backups and locks: copies of the server's structure (channels, roles, permissions, no messages or members) that staff save, and channels or roles staff locked. Kept until staff delete them, or Astri leaves.

The reasons staff type are written by them, not by us. If one is wrong, ask that server's staff to change it, or ask us.

What the website stores

When you sign in with Discord, the site asks for your username and the list of servers you're in (the identify and guilds scopes). It stores, for each signed-in browser:

Your Discord ID, username, display name and avatar.
The servers you're in and your permissions there, so the dashboard shows the right ones.
Your Discord access token, encrypted, so the server list can be refreshed. It's never sent to your browser.
A hashed form of your IP address and your browser name, so you can recognise your sessions on the account page and we can spot stolen sessions.

This is deleted when you sign out, or 30 days after you last used the site. The account page can sign you out everywhere at once. Changes you make on the dashboard are recorded against your Discord ID in the server's change history (90 days).

Servers can ask new members to verify on the site. The page checks your browser (its user agent, request headers, screen size, language and time zone) and, when the server asks for a captcha, loads Cloudflare Turnstile, which receives your IP address and browser details to tell people from scripts. Astri keeps a verification log for 90 days: your Discord ID, when you pressed Verify, whether each attempt passed or was refused and why, a hashed form of your IP address and your browser name. The one-time link is stored only as a hash, and stops working after a few minutes or one use.

The status page shows totals across every server, such as how many servers use Astri. They can't be traced to a server or a person.

Like any website, the servers that host it briefly see your IP address and request details to deliver pages and fend off attacks. These request logs are kept short and are not used to profile you.

Cookies and storage

One cookie keeps you signed in, and a short-lived one protects the sign-in step against forgery. Both are strictly necessary.
The site remembers a few choices in your browser's own storage, such as whether you've finished the dashboard tour. It never leaves your browser.
On verification pages that use a captcha, Cloudflare Turnstile may store what it needs to tell people from scripts.

There are no analytics, tracking or advertising cookies, and no third-party fonts or scripts on other pages. Because everything we use is strictly necessary for the service you asked for, Dutch law (Telecommunicatiewet, article 11.7a) doesn't require a cookie banner. Blocking these cookies will stop sign-in from working.

Account standing

Everything is stored per server, with one exception. When Astri automatically contains an account (bans, kicks, quarantines or strips its roles during a raid, nuke, honeypot hit or spam incident), that counts toward the account's standing in every server Astri protects. When an account contained in other servers joins, that server's staff see its standing and what happened and when, but never which servers. A server can also let standing raise a joiner's risk score; this is off unless its staff turn it on.

Bans and kicks by a server's staff never count. Only Astri's own automatic actions do.
Standing is worked out from the incident records above, so it goes when they do, after at most 180 days.
A false positive or an undone action stops counting straight away.
We may correct an account's standing by hand, for example after a review, with a note saying why. Corrections stay until they expire or are removed. We also remember which standing you were last told about, so you aren't messaged twice.
You can see your own standing on the account standing page and ask for a review there. Reviews and their outcome are kept for a year after they're decided.

Standing is a signal for staff, not an accusation or a finding that you did anything wrong.

Astri Network

A server's owner can ask to link it with other servers in a network, and it joins only once the owner who runs that network accepts. When Astri contains an account during a raid or a nuke in one server of a network, every other server in it applies its own raid punishment to that account, even if the account hasn't joined there yet. Nothing is shared with servers outside the network.

The network keeps the account's ID, the server and the raid or nuke it came from, and what each server did about it. Staff in the network's servers see the account and the name of the server it came from.
Each server name in a network is shown to the staff of the other servers in it. A server asking to join is named to the network's owner, along with who asked; requests are deleted once answered, or after 7 days. Join codes are deleted 7 days after they run out.
Only Astri's automatic actions against raiders and nukers are shared. Staff actions, and anything else Astri does, never are. Actions taken through a network don't count toward account standing.
If the raid or nuke is marked a false positive, or the action is undone in the server it came from, it's undone in every server. Accounts that never joined are forgotten after 30 days, and every network record is deleted at most 180 days after it was made.
If you were banned or held back through a network, appeal to the server that acted, as for any other action.

Running the service

To keep Astri working, secure and free of abuse, we also keep:

Service logs: short technical logs with IDs and outcomes, never message text, tokens or session IDs, to run and fix the bot. Kept only as long as that needs.
Operator records: a log of significant events and of what we do as operators (for example a server joining a network, a standing correction or a block), with the server and account IDs involved. We keep these as long as they're needed to investigate abuse, answer appeals and complaints, and establish or defend legal claims, and delete entries that are no longer needed.
Blocks: servers and accounts barred from using Astri or the dashboard for breaking the terms, with the reason. Kept while the block applies.
Departures: when Astri left a server, so its data can be deleted 30 days later.
Totals: counts such as servers, incidents and uptime, which don't identify anyone.

Legal bases

The GDPR needs a legal basis for each use of personal data. Ours are:

Legitimate interests (article 6(1)(f)) for protecting servers and their members from raids, nukes, spam and repeat attackers, moderation, account standing, the Astri Network, verification, security, abuse prevention and operator records. The interest is keeping Discord communities safe and the service working. We think it outweighs the impact on you because we keep little, for a limited time, show only what's needed, never use it for advertising, and give you a way to see and challenge what affects you. Server owners rely on the same basis for their own servers.
Contract (article 6(1)(b)) for signing you in and running the dashboard you asked to use, under our terms.
Legal obligation (article 6(1)(c)) where the law requires us to keep or hand over data, and to answer your rights requests.
Establishing or defending legal claims, as part of our legitimate interests, for keeping records of disputes and complaints.

We don't rely on consent, so there's nothing to withdraw, but you can always object (see your rights). We don't knowingly process special categories of data (article 9) or data about criminal convictions (article 10).

Automated decisions

Astri acts automatically, in seconds, because raids and nukes are too fast for people. It may time out, quarantine, kick or ban an account, or remove its roles, based on signals such as account age, join timing, matching names or avatars, spam patterns, a honeypot hit or, where a server turned it on, account standing. These actions only limit access to a Discord server, which its owner can already do; they don't have legal effects on you. Even so, you can always get a human to look again:

appeal to the server's staff, who can undo the action and mark it a false positive;
ask for a review of your standing on the account standing page, which a person decides;
contact us, to put your side and contest the decision.

Server staff choose the settings and whether Astri acts or only reports, and they see why it acted.

Server staff with Manage Server or above see their own server's records, in Discord and on the dashboard. Staff of other servers see only standing and network records, as described above.
Discord, since Astri runs on it and acts through its API.
Our hosting provider, which runs the servers and database Astri uses, as our processor. It may only use the data to provide its service to us.
Cloudflare, for the captcha on verification pages that use one.
Authorities, courts and advisers where the law requires it, to protect people from serious harm, or to establish or defend legal claims, and only what's needed.
A successor, if Astri is handed over to someone else to keep running. They'd have to follow this policy, and you'd be told.

We don't sell or rent personal data, and don't share it for advertising.

Outside the EU

Astri's data is stored in the European Economic Area where we can. Discord and Cloudflare are based in the United States, so data they receive may go there. Such transfers rely on the EU-US Data Privacy Framework where the company is certified, or on the European Commission's standard contractual clauses. You can ask us for details of the safeguards.

Security

We take reasonable technical and organisational measures for a service of this size: encrypted connections, Discord tokens encrypted at rest, sessions and IP addresses stored only as hashes, access limited to what each part needs, server staff permissions checked against Discord on every change, and extra confirmation for dangerous actions. No system is perfectly secure. If a breach is likely to put you at risk, we'll report it to the Dutch Data Protection Authority and, where the law requires, tell you.

Removing Astri

When Astri is removed from a server, the dashboard hides that server straight away. 30 days later every record about it is deleted, including incidents, cases, appeals, backups, settings and join records. A server Astri leaves also leaves its network straight away. Adding Astri back within those 30 days keeps the data. Deleted data may stay in backups of the database for a short time until they're overwritten.

Your rights

Under the GDPR you have the right to:

access what we hold about you and get a copy;
have it corrected if it's wrong;
have it deleted;
restrict how it's used while a complaint is looked at;
object to uses based on legitimate interests, including standing and the network. We'll stop unless we have compelling reasons that override yours, or need it for legal claims;
receive data you gave us in a portable format, where that applies.

To use them, contact us with your Discord ID and, if it's about one server, that server's ID. We may ask you to prove the account is yours, for example by signing in to the site or answering from it, so we don't hand someone else's data to the wrong person. We answer within one month, which can be extended by two more for complex requests; we'll tell you if so. It's free, unless requests are clearly unfounded or excessive.

Some limits apply. Deleting the record of an incident can stop a server's staff from seeing why someone was banned, or let a raider straight back in, so where a server owner is the controller we pass your request to them, and where we keep a record to protect others we may keep it for its normal period and explain why. We won't reveal other people's data or which servers contained you where that would harm them. If you think your standing is wrong, the quickest route is a review on the account standing page.

Children

Astri is for Discord users, so it follows Discord's minimum age, which is 13 in most countries and higher in some. Don't sign in to the website if you're below the minimum age where you live. In the Netherlands and some other countries, people under 16 need a parent or guardian to agree before using services like the dashboard; if that applies to you, ask them first. Members of servers Astri protects may include young people; Astri treats them the same as anyone else and keeps no more about them. If you think we hold data about a child who shouldn't be using the service, contact us and we'll delete it.

Changes

If this policy changes, the date at the top changes too. Big changes are announced in the support server before they apply, and the old version is available on request.

Contact and complaints

For anything about your data, this policy or your rights, email [email protected] or ask in the support server. We'll answer in English or Dutch.

If you're unhappy with how we handle your data, please tell us first so we can put it right. You also have the right to complain to a data protection authority: in the Netherlands that's the Autoriteit Persoonsgegevens, or you can go to the authority where you live or work.