What is stored

Privacy Policy

Last updated 25 October 2026

This covers both this directory and the bots it lists (such as Inertia Control).

This directory

At sign-in it reads your Discord account (ID, username, avatar) and the list of servers you're in, once, to work out which panels to show you. It doesn't read your email, messages or roles.

It keeps a signed session cookie for one hour holding your ID, name, avatar and the short list of panels to show. Your Discord token is never stored and is revoked as soon as it has been used. Nothing is written to a database here.

The store uses the same sign-in, and also notes which of your servers you own or manage, for one hour, so you can pick one to subscribe. Payment happens on Stripe's own checkout page; Stripe then tells the bot when a server's subscription starts, renews or ends.

The status page shows only overall numbers and sets no cookies.

This explains what Inertia Control stores, why, and for how long. It's written to match what the bot actually does. The bot is run by Inertia Studios, based in the United States of America, and everything below lives on a virtual private server rented by Inertia Studios and in that server's backups. Discord is where the bot's data comes from; Discord's own privacy policy covers what Discord itself does.

What the bot stores

Discord IDs and names. Your user ID, and the display name and avatar Discord shows for you, so warnings, tickets and panel sessions can be tied to the right person.

Moderation records. Warnings, timeouts, kicks, bans, notes, their reasons, who issued them and when. Kept by the server that issued them for as long as that server uses the bot; warnings can expire on a schedule the server picks.

Message content, in limited cases. The bot reads messages in servers it's in so auto-mod, the word filter, scam-link checks and stickies can work. It keeps message text only where a feature needs it: a message that was reported, a message removed by auto-mod (in the log), ticket conversations (so staff can review them, and so a copy can be posted when a ticket closes), and application and appeal answers. Messages aren't kept otherwise.

Panel sign-ins. When you sign in with Discord the bot gets your Discord ID, username and avatar from Discord and nothing else; it never sees your Discord password or email. It stores a session for a limited time, the browser type, the country the sign-in came from, and the IP address the sign-in came from, so a stolen session or a break-in attempt can be spotted and blocked. Authenticator (2FA) secrets are stored so your codes can be checked; they're never shown again after setup.

Who sees IP addresses. Only the bot's operator. Addresses are written to a private channel that only the operator can see, and to the bot's database. A server's own logs show the country and browser of a sign-in, never the address, so nobody on a server's staff can target a person from a log. The operator sees them for one reason: to spot and block stolen sessions, break-in attempts and abuse of the panel, and never shares them.

Settings. Each server's settings (channels, roles, filter words, messages) and who changed them.

Activity numbers. Counts for staff activity and levels (how many messages, how many actions), not the messages themselves. Also daily counts of joins, leaves, raids, scams and similar events for the weekly report.

Community features, if a server turns them on. Birthdays: the day and month you save (never the year) and your time zone offset, deleted if you remove it or leave the server. Reminders: what you asked to be reminded of and when. Highlights: the words you picked, deleted when you leave. AFK: your AFK note and links to messages that mentioned you while you were away, deleted when you're back. Booster roles: which role is yours. Starboard: which message was copied where.

Economy, achievements and games, if a server turns them on. Your coin balance, daily streak and what you bought in the server's shop (and when a rented role runs out); the badges you unlocked and a count of your messages for them; reputation given and received (the giver, the receiver and an optional reason, kept for 90 days); trivia scores and your daily word guesses; your counting, poll votes and event answers (Going, Maybe or Can't go). Coins have no money value and can't be bought or cashed out.

Profiles. The bio, pronouns and time zone you choose to save with /profile set, deleted when you clear them or leave the server.

Confessions. Confessions are anonymous to members, but the bot records who sent each confession and reply, and shows that to the server's staff so they can deal with abuse. The text of a confession waiting for staff approval is stored until it's approved or denied.

Modmail. When you message a server's staff through the bot's DMs, your messages and their replies are relayed and saved as a transcript for that server's staff, like a ticket.

Public leaderboards. If a server turns on its public leaderboard page, anyone with the link can see the display names, pictures, levels or coin balances of that server's top members.

Invite tracking. Which invite each member joined with, who made it, and when they joined or left, so invite counts can leave out fake accounts and people who left.

Server insights. Counts of messages per day, hour and channel; which members talked on a given day (so each is counted once); and for new members, when they joined, got their first role, sent their first message and left. Never message content. Deleted after 100 days.

Server backups. Once a day (if the server keeps it on) a snapshot of the server's roles, channels and permissions, so a nuked or wrecked server can be put back. Snapshots hold names and permission settings, not messages, and are kept for the number of days the server picks (14 by default).

Ticket transcripts. A copy of each closed ticket's conversation, kept with the server's records so staff can open it later from the dashboard.

Branding and social feeds. A picture or banner a server uploads for the bot's profile there, and the YouTube or Twitch channels a server asks to be alerted about (public information only).

Subscriptions. For a paid server: which server it is, who subscribed (their Discord ID), the Stripe customer and subscription IDs, the plan, the date it's paid until, and the billing email address Stripe passes on, used only to contact them about the subscription. Card and bank details go to Stripe and stay there.

Operator records. Technical logs (errors, restarts, which features ran) that can include Discord IDs and server names; the operator's notes about servers; help requests sent from panels; and security blocks and bans. These are only for running and protecting the service.

Cookies. The panel sets four, none of them for tracking or advertising: your sign-in session (12 hours); which server you're looking at (up to 400 days); a "this browser was approved" marker for sign-ins that were confirmed in Discord DMs (up to 400 days, so you aren't asked again); and a short session for the application website (6 hours). Sign-in steps in progress (authenticator code, DM approval) use a cookie that lasts 10 minutes.

Where the country comes from. It's the network's geolocation of the address you connected from (Cloudflare's), not GPS, and it's only ever as precise as a country.

Messages the bot sends you. The bot DMs people about things that concern them: a sign-in to approve, a block or ban and its reason, an application or appeal result, a server's approval. It doesn't send marketing.

What it doesn't store

Your Discord password, Discord email address, phone number or payment details — it never receives them. Subscription payments go to Stripe; the bot only records that a server is paid up and until when, plus the subscriber's billing email (above).
Your messages in general. Only the cases above.
Anything from servers the bot isn't approved for. If it's invited somewhere else it leaves.

Who can see it

A server's staff see that server's records on its panel, according to the pages their roles allow. Nobody on one server's panel sees another server's data.
For the first 48 hours after the bot joins a server, and until its owner chooses who can use the panel, anyone in that server with a moderation permission (Administrator, Manage Server, Ban, Kick, Timeout or Manage Messages) can see the staff pages, including members' moderation records, tickets, reports, appeals and applications. After that, only the people the owner has chosen can. Owners should set this up straight away if that matters to them.
The bot's operator can open any server's panel (see the Terms, section 3). Every change made there is logged to that server. The operator is also the only person who can see sign-in IP addresses and the bot's server-wide records (which servers it's in, who asked for help, security blocks).
When a server asks for help from its panel, the bot's support team sees the request, the server's name, owner, member count and plan, and while the request is open can look at a read-only copy of its panel settings (never its security or owner-only settings). Each look is logged to that server. Support changes settings only if the server's owner presses Allow in Discord; every change is logged to the server, and it ends when the request is closed or the owner stops it. Support never sees sign-in IP addresses.
Data isn't sold, rented, or shared for advertising or cross-site tracking.
It goes to other companies only where a feature needs it: Discord, where it all comes from; the company hosting the server the bot runs on; Cloudflare, which carries traffic to the panel and supplies the country of a sign-in; Vercel, which hosts the Control Center and passes requests through to the bot; Stripe, which takes subscription payments directly from the payer; YouTube and Twitch, which are only asked about the public channels a server follows; and the music sources a server's staff pick. These companies handle data under their own privacy policies and may keep ordinary request logs.
A server's owner can download that server's records, which include the records about its members (warnings, tickets, applications and so on). Sign-in IP addresses are never included.
The operator may share information when the law requires it (for example a valid court order or subpoena), or when it's reasonably needed to protect someone's safety, stop fraud or attacks on the service, or enforce the Terms.
If the service moves to a new owner (Terms, section 9), the data goes with it and stays under this policy; paying servers are told first.
Overall numbers about the service (servers protected, uptime, attacks stopped) may be published, as on the status page. They never identify a server or a person.

How long it's kept

Panel sessions last 12 hours and are deleted when you sign out.
Sign-in records and the settings-change history are trimmed automatically as new ones arrive.
Moderation records, tickets, applications and appeals are kept while the server uses the bot. When a server is removed or its subscription lapses, its settings and records are kept for 30 days so it can come straight back, then the operator deletes them (Terms, section 5). Its owner can ask for that to happen sooner.
Ticket transcripts are kept with the server's other records, on the same terms.
Operator logs and notes are trimmed regularly and kept no longer than needed to run and protect the service.
Backups of the database are made daily and deleted automatically after 14 days.
Server snapshots are deleted after the number of days the server picks. A server's owner can download everything the bot holds about their server at any time from the dashboard's Backups page.

Keeping it safe

Panel sign-in is through Discord, with an authenticator code on every sign-in when a server has that on. Session tokens are stored only as hashes. Each server's staff see only their server. IP addresses are seen by the operator alone. The panel blocks addresses and accounts that behave like an attack (the Terms, section 7). No system is completely secure, so the operator can't promise data will never be exposed, but works to prevent it; if data the bot holds is ever exposed or taken, the affected servers are told promptly, with what happened and what was affected.

Age

You must meet Discord's minimum age to use Discord, and so the bot. It doesn't knowingly keep records about anyone under 13 (or under the age your country requires). If it has, tell the operator and they'll be removed.

Your choices

To see or remove your records in a server, ask that server's staff: the panel shows them everything about you in one place, and they can delete warnings and notes.
To sign out everywhere, use the Security page (owners) or ask an owner to end your sessions. To reset your authenticator, ask an owner to run /dashboard2fa.
To have everything about you deleted from a server's records, contact that server's owner or the operator.
You can ask what the bot holds about you, have mistakes corrected, and have it deleted, by contacting the operator; expect an answer within a month. The exception is records a server needs to keep for its own safety (for example, a ban and its reason), which stay with that server. The bot is operated from the United States and this policy follows US federal law.
Some US states (California, for example) give their residents rights to know, correct and delete their information and to opt out of its sale. The bot doesn't sell personal information or share it for advertising, and the requests above work for everyone, wherever they live. Nobody is treated differently for using them.
Browsers' "Do Not Track" signals aren't acted on, because the bot and its sites don't track you across other sites in the first place.
If you use the bot from outside the United States, your information is stored and processed in the United States.

Changes and contact

This policy can change; the date at the top is the current version. Big changes are announced to approved servers, and continuing to use the bot after a change means you accept it. Questions go to the operator listed on your panel's Overview page, or through the server the bot was approved for.