Legal

Privacy Policy

Last updated: 2026-09-25

In short: acrO stores what the features a server turns on need, never sells or rents data, and a server owner can delete the server's data at once with /config wipe.

This policy explains what the acrO Discord bot, its website and dashboard collect, why, how long it's kept and what you can do about it. The controller responsible for this data is acrO TEAM.

1. What we collect

Discord identifiers and names — IDs of servers, channels, roles and users that features work with, a server's name, and a member's name at the time of a moderation case.
Server settings — everything staff configure (channels, roles, messages, filters, language, timezone).
Feature data, only when the feature is used: XP, levels and message/voice counts (leveling); balances, items and reputation (economy); moderation cases with reasons; temporary roles and their end time; tickets with topics, form answers and ratings; giveaway entries; suggestions and votes; starboard posts; tags, automatic replies, scheduled and sticky messages and embeds staff create; reminders and AFK notes you write (and your previous nickname while you're AFK); the roles of members who left, when a server keeps roles on rejoin; who owns a temporary voice channel; your birthday's day and month (and the year only if you give it); which invite someone joined with; YouTube and Twitch channels a server follows.
Ticket transcripts — when a ticket closes, its messages (with authors' names, avatars and links to attachments) are saved for the server's staff, and can also be posted to a staff channel or sent to the member as a file.
Public leaderboards — only if a server turns this on: members' names, avatars and levels on that server are shown on a public web page.
Ban appeals — only if a server turns this on: when you appeal a ban on the website, your user ID and name, the ban reason, what you wrote, and the staff's decision with an optional note are kept for that server's staff.
Settings history — who changed which setting on a server (user ID and name, the old and new value), shown to the server's staff on the dashboard and in its log channel.
Member reports — when you report a message or a member: your user ID and name, the reported member, the reason you wrote, a snippet of the reported message, and the staff's decision with an optional note, for that server's staff only.
Modmail — when you DM acrO to reach a server's staff: your messages (and links to your attachments) are posted into a private staff thread on that server, on Discord. We store which thread belongs to whom, its number and whether it's open, and who is blocked from modmail; when a conversation closes, a text transcript can be posted to the server's log channel.
Applications — the forms a server's staff create, your answers, and the staff's decision with an optional note.
Confessions — the text of anonymous confessions and replies with the author's user ID. Other members never see who wrote one; the server's managers can look the author up when a confession breaks the rules, and every lookup is logged on that server.
Events — the events staff create and who answered Going, Maybe or Can't go.
Booster perks and counting — which personal role belongs to which member; a counting channel's current number, record and who counted last.
Keyword highlights — the words you asked to be notified about on a server (/highlight), until you remove them or leave.
Custom commands and scheduled messages — the commands and messages a server's staff create, with the ID of who created them.
Server statistics — daily totals per server (messages, joins, leaves, voice minutes, commands), plus message counts per hour of the day and per channel (for the activity insights). These are counts only: no message content and nothing per person.
Ban sync — which servers a server owner linked into a group, and who created it. A repeated ban is recorded as a moderation case on the server it was repeated on.
Backups — a server's roles, channels and permissions (including permissions set for individual members) and acrO settings, when staff make a backup.
Dashboard login — when you log in with Discord, we receive your user ID, username, avatar and the list of servers you're in with your permissions there (OAuth2 scopes identify and guilds). We keep these, with up to 250 of your servers' names and icons, in your login session. The Discord access token is revoked right after login and never stored.
Premium and votes — Discord's subscription records (which server or user has premium, and until when); keys (stored only as a hash) with the server they were redeemed on and the user ID of who redeemed them; who gave a server premium; the user ID of who last changed the bot's look on a server; if you vote on top.gg, your user ID and the time.
Abuse prevention — IDs of users and servers blocked from the bot, with the reason.
Technical data — your IP address is used in memory for rate limiting and isn't stored by us (our hosting provider's logs may contain it briefly); error reports can contain IDs and are used only to fix problems.
Cookies — the dashboard sets two strictly necessary cookies: your login session (7 days) and a short-lived one that protects the login itself. If you pick a language with the switch in the header, a third cookie remembers that choice for a year. There are no tracking or advertising cookies.

2. Message content

If the operator enables Discord's Message Content access, acrO reads messages as they arrive to run the features that need text: automod filters, automatic replies, message logs, the starboard and ticket transcripts. Recent messages are kept in memory for about an hour (at most 200 per channel) so edits and deletions can be logged. Message text isn't stored in our database, with two exceptions: ticket transcripts and confessions (above). Direct messages you send to acrO are only relayed to the staff thread of the server you chose (modmail). Some features copy messages into the server's own channels on Discord when staff set them up — the logging module (edited and deleted messages), the starboard (highlighted messages) and automod alerts (the message that broke a rule).

3. Why, and on what legal basis

To run the features a server's staff turned on, show the dashboard and website, keep the service safe (rate limits, blocking abuse) and fix errors — our legitimate interest in providing the service they asked for (GDPR Art. 6(1)(f)).
To provide Premium you bought or redeemed — performing that agreement (Art. 6(1)(b)), and keeping purchase records where the law requires it (Art. 6(1)(c)).
Optional details you add yourself, like your birthday — your consent (Art. 6(1)(a)), which you can withdraw by removing them.

We don't build profiles, show ads or use data to train AI models.

4. Sharing

We never sell, rent or give data to advertisers or data brokers. Data is processed by our hosting provider, Railway Corporation (United States), and naturally by Discord. Payments are handled by Discord; we never see card details. top.gg only receives the number of servers. YouTube and Twitch only receive the public channel names we check. Where data leaves the European Economic Area (Discord and many hosting providers are in the United States), it's protected by the provider's safeguards, such as the EU–US Data Privacy Framework or Standard Contractual Clauses.

5. How long we keep it

While acrO is on a server, feature data is kept until staff delete it or the member removes it (for example /birthday remove).
Everything about a server is deleted 30 days after acrO is removed from it — except backups, kept until 180 days after they were made so an owner can rebuild a lost server.
Dashboard sessions end after 7 days. Top.gg votes are deleted after 30 days. Daily statistics are deleted after about 13 months, hourly and per-channel counts after 100 days. Ticket transcripts are deleted after 30 days (365 with Premium). The settings history is deleted after 90 days, ban appeals 180 days after they were decided, member reports 90 days after they were handled. Confessions are deleted after 90 days, decided applications and closed modmail conversations after 180 days, events 30 days after they took place.
Premium records are kept as long as needed to honour purchases and for accounting. Blocks for abuse last until they're lifted.
A server owner can delete the server's data at once with /config wipe. Only what must outlive it is kept: temporary bans and roles that are still running (so they still end on time), premium records, and the server's basic record (its ID and name).

6. Your rights

You can see, correct or delete your data, get a copy of it, object to or restrict its use, and withdraw consent — contact us (the bot's support channels); we answer within 30 days. Many records you can also remove yourself (your birthday, reminders, AFK note), and server staff can delete most others with the matching commands. You can also complain to a data protection authority, for example the one in your country.

7. Children

acrO is for Discord users, who must meet Discord's minimum age (13 in most countries). We don't knowingly collect data from anyone younger.

8. Security

Dashboard sessions are random and only their hash is stored; every form is protected against cross-site requests; access to a server's dashboard is checked against the bot's live view of Discord on every request; the bot asks only for the permissions its features need.

9. Changes and contact

We'll update this page when what we collect changes; the date at the top shows the latest version. Questions or requests: the bot's support channels.