What we keep, and what we don’t.
No dark patterns, no data sales, no reading your chats. This page says plainly what Akiko stores, how long it lasts, and how to make it go away.
Akiko stores what your features need and the security data required to keep banned users from walking back in. It does not store the general contents of your channels, it does not sell anything to anyone, and moderators are never shown your IP address. Run ;;data to see everything held against your account, export it, or delete it.
What we collect
Identifiers
User, server, and channel IDs. These tie your settings to you and nothing more.
What you give a feature
Reminder text, AFK reasons, birthdays, tags, custom commands, and the parameters a command needs to run.
Feature data
Economy balances, levels, and profile data for servers that use those features.
Moderation records
Warnings, infractions, and bans recorded by your server’s staff.
Network data
The IP address you connect from when you sign in to the dashboard or verify, basic browser details during verification, and which accounts have used the same address. Details are under ban evasion and alt detection below.
Conversational AI
Where AI features are enabled, messages that trigger a response are stored so the conversation has context: your message, Akiko’s reply, and a mathematical representation used to recall relevant history. This applies only where AI is switched on, and only to messages that actually trigger the assistant. Akiko does not record channels it is merely sitting in. You can clear this history or turn the feature off at any time.
A message can trigger the assistant by mentioning Akiko, by being sent in a channel the server has set aside for her, or by being sent as a direct message. In servers that enable AI, Akiko may also join a conversation on her own when recent messages in the channel are relevant. To decide whether to do so she compares the text of recent messages in memory only, and nothing from a conversation she does not join is stored. Members who opt out of message tracking are skipped entirely.
Plain-English automod rules are optional and part of Akiko Prime. If a server turns one on, Akiko sends the text of messages in the channels that rule covers to TypeSafe, an AI service, to decide whether a message matches the rule. Only the message text is sent, without names or IDs. Akiko does not keep the text: it records which message matched, who sent it and a score, for up to 14 days. A server must agree before its first rule and can stop at any time with /automod rules withdraw, which pauses every rule. Testing a rule reads recent messages the same way and shows the results only to the person who ran the test.
Usage statistics are aggregate counters only: how often a command has run and when it last ran. There is no per-use record of who ran what, where, or with which parameters.
18+ taste signals
The 18+ commands can learn from what you like. Nothing is stored until you press Like or Dislike on a result in an age-restricted channel, after you have already confirmed you are 18 or older. That first press is the opt in, and it covers you alone.
Each signal keeps your Discord user id, the source the post came from, the post id, the post’s public tags, whether you liked or disliked it, and the time. A running score per tag is worked out from those. What you searched for, message text, and the server or channel are not part of it.
Posts sent by autopost carry a like count and a dislike count as numbers on the Like and Dislike buttons. Each number covers the post across all of Akiko, never one person, and shows no names.
Posts that carry a tag on Akiko’s child-safety blocklist are never stored, and a tag added to that list later is removed from everyone’s data.
You can adjust a tag’s weight, pin it, mute it, remove it, or delete everything. That is available in Discord with /nsfw taste, or on the Taste memory page after you sign in. A pinned tag stops fading and stays until you change it or delete it. A muted tag is never used. New tags can only be added in Discord.
- Only you can see your own signals, through /nsfw taste, in a reply no one else can read. No command shows them to staff or other members.
- Your own likes and dislikes shape only what Akiko shows you. Anonymous counts, with no names, are also used to show vote totals and to choose which posts autopost sends. Not sold, not shared, not used for advertising, and not on any leaderboard.
- Those counts decide autopost too. A post that at least 5 different people have voted on, where at least 70 percent of the votes are dislikes, is skipped. A post with at least 5 votes and at least 70 percent likes is shown more often. This applies to every server’s autoposts and uses only the counts, never who voted.
- Counts of a tag shared by at least 20 different people can appear in a popular list, with no user ids.
- Older likes count for less unless a tag is pinned: weight halves roughly every 30 days, your newest 500 signals are the ones kept, and everything, pinned and muted tags included, is deleted after 180 days with no activity.
- You can see your top tags, remove any tag, or delete all of it at any time. Deleting removes the opt in too.
Ban evasion & alt detection
To stop banned users returning under a new account, we record your IP address when you complete web verification or sign in to the dashboard, whether that address belongs to a VPN, proxy, hosting provider, or Tor exit node, and basic browser characteristics during verification (user agent, language, platform, timezone, screen size, reported processor count) along with a short code derived from them, used to spot automated browsers and to stop someone else completing your link.
This detects when several accounts share a network, which works across servers because an address is not tied to any one of them. A server can switch on alt detection. When it does, that server’s moderators are told when a joining account appears to share a network with other accounts, and they are shown which accounts are involved, never the address. When someone finishes or is turned away at web verification, a server’s moderators can also be told that the connection looked unusual, for example that it came from a hosting network or Tor, again without the address.
Our web servers also keep ordinary request logs, and pages that exist only to catch scanners and bots record the address, the page asked for, and the request headers. An address that keeps probing those pages may be blocked for 24 hours. These logs are searched by address, not by account.
A server can also switch on the suspicious account filter in its automod settings. When it does, Akiko looks for several accounts joining within minutes with a similar name or the same profile picture, and for accounts Discord itself has marked as spam, and tells that server’s moderators so a person can look. It never bans, kicks or mutes anyone. To spot a group it keeps, in memory only and for about 15 minutes, a short scrambled code for each joiner’s name pattern and profile picture. It never keeps the name, the account ID or the picture, and nothing is written to our database. A server can also turn on an AI context note, which sends the username and display name of a joining account to TypeSafe, an AI service, when the name looks borderline. That note is off unless the server chooses it, and it can never cause a flag by itself.
- Moderators see derived results only: which accounts appear linked, and when. Never your address.
- Akiko’s operators can look up an account’s most recent address and the accounts linked to it from a private admin console. Every lookup is recorded.
- Not used for advertising, profiling, or location tracking.
- We do not try to work out where you physically are.
- The reputation provider gets the address alone, with no Discord identity attached.
How long it lasts
| Data | Kept for |
|---|---|
| Reminders, birthdays, AFK, economy, levels, tags | Until you delete them |
| AI conversation history | Until you clear it or delete your data |
| Music queues | The session, plus 5 minutes to reconnect |
| Voice state | Memory only, never written to disk |
| IP addresses, shared-network records, verification attempts | 90 days after last use, then deleted automatically |
| Web server request logs (address, page requested, browser type) | 14 days |
| Decoy page sightings (address, page requested, request headers) from scanners and bots | Up to 90 days |
| Moderation records | As long as Akiko is in the server |
Who else sees it
| Service | What it receives | Why |
|---|---|---|
| Discord | Whatever running a bot requires | Core service |
| IP reputation provider | An IP address alone, with no Discord identity attached | Looks up the country, network, and organisation behind an address |
| Tor Project | Nothing about you. We download their public list of exit relays and compare locally | Tor classification |
| Cloudflare | Every request to our websites, including the address it came from | Hosting, DDoS protection, and blocking abusive traffic |
| hep.gg AI Gateway | Conversation text, where AI is enabled | Runs the language model |
| TypeSafe | The text of messages in the channels a plain-English automod rule covers, only for servers on Akiko Prime that have agreed to it. Separately, the username and display name of a joining account, only for servers that turned on the AI context note in the suspicious account filter | Judges whether a message breaks the rule, and adds a context note to borderline joins |
| Ollama (cloud) | Images you send to Akiko, with the message they came in, where AI is enabled | Lets Akiko look at images |
| Sightengine | Images posted where image scanning is on | Detects scam and rule-breaking images |
| Google Translate | The text of direct messages sent to Akiko | Translates non-English support messages |
| Stripe | Billing details you enter | Payment processing |
| sinking.yachts / URLhaus | URLs found in messages, where link filtering is on | Phishing and malware detection |
What we never store
Getting it back
;;data- View, export, or delete everything held against your account.
;;opt in/;;opt out- Turn non-essential collection on or off.
/nsfw taste- See your top 18+ tags, remove one, or delete all of it. Deleting also turns the feature off.
Everything tied to your account: reminders, birthdays, AFK status, AI history and memory, economy and levels, profile data, tags, premium records, your stored email, and dashboard login addresses. We keep no separate copy for ourselves. Routine backups that were taken before you deleted can still hold a record until those backups are replaced on their normal rotation.
A few things survive, and we would rather be direct about why:
- Ban evasion links. Where your account is linked to another through a shared network, that link and the verification attempts it was worked out from keep their normal 90-day life instead of being erased on request. If deletion wiped them, anyone evading a ban could clear the evidence by asking for their data back.
- Server moderation records. Warnings, infractions, and bans belong to the server that issued them, not to us, and stay visible to that server’s staff.
- Web server logs and decoy sightings. These are recorded by address, not by account, so we cannot find yours to delete. They expire on their own schedule, 14 days and up to 90 days.
These are kept under legitimate interest for security and abuse prevention, used for nothing else, and shared with no one. Moderators still never see your IP address.
How it’s protected
Closed by default
A firewall lets only web and game traffic in from the open internet. Admin access runs over a private Tailscale network with key-based auth.
Private database
Postgres is closed to the open internet by the firewall. It is reachable only from the host itself and from devices on our private Tailscale network.
Encrypted in transit
Traffic between Akiko, Discord, and the dashboard is protected with TLS.
Automatic purging
Expired IP and verification records are deleted on a daily schedule, not on request.
Questions, or want your data?
Use ;;data for anything self-serve. For everything else, open a ticket in the support server or email us. Significant changes to this policy are announced in the support server and via bot alerts.
Effective 7 November 2026. Previous versions were hosted as a GitHub gist. More about Akiko.