Privacy Policy
What is stored, who receives it, and how to erase it.
THE SHORT VERSION
Computer stores very little, because it has to. There are no accounts with passwords, no email addresses, no payment info, no analytics, and no advertising.
- Game: your Discord user ID, your display name, and a handful of preferences and career counters.
- Telephone: per-server settings and a call history. Never message bodies, except voicemails and call reports.
- AI bots: if AI bot chat is switched on, some meeting chat lines are sent to Groq. You can opt out — see Section 9.
- You can export or erase your data from inside Discord, any time. See Section 11.
1. WHAT THIS COVERS
Computer is one Discord bot doing three separate jobs. This policy covers all three, because they share a database:
- The murder-mystery game —
/sus. The lobby lives in a server channel; the actual game is played through Discord DMs. - The cross-server telephone —
/phone. Connects real Discord servers to each other over one shared phone network. - The ship phone —
/user. Lets players ring each other by 4-digit extension through DMs.
Discord itself is a separate company with its own privacy policy. Anything Discord holds — including your DMs with the bot — is subject to Discord's policy, not this one. We only control what our own database files hold.
2. WHO RUNS IT
Computer is an independent project published by Neptune Productions under the Discord user neptunetheii (GitHub: notmicrosoft2000-cmd). It is not affiliated with, endorsed by, or sponsored by Discord Inc.
The bot's source code is currently kept private, so this page is the authoritative description of what is stored. It is a Python discord.py bot; if the code is ever published, this policy will link to it.
3. WHAT WE COLLECT — GAME
Stored in a single file, accounts.json, keyed by your Discord user ID:
| Field | What it is | Why |
|---|---|---|
| Discord user ID | Your numeric snowflake. The lookup key. | Identifies you across sessions and servers. |
| Display name | Your Discord display name at the time it was read. | Shown in-game so players know who they're talking to. |
| created_at | When your profile was first created. | Housekeeping. |
| accent | A colour you picked. | Your in-game look. |
| catchphrase | A short line you set. | Bot dialogue uses it in your lines. |
| pronouns | Free text, your choice. | Bot dialogue refers to you correctly. |
| custom name | Optional in-game name. | Lets you play without your real display name. |
| stats | games, wins, kills, deaths, ejections, tasks — counters only. | Personal record, shown by /sus account. |
| phone | A 4-digit ship extension. | Your /user phone address. |
| ai_optout | Whether you opted out of AI sharing. | Honouring Section 9. |
We never store your email address, your Discord username, your password, your real name, your location, your IP address, or any payment information. Discord does not expose your email to bots in the first place.
Individual game records are not kept. We store running totals, not a history of every match. Kill logs, meeting transcripts, and voting records live in memory and are gone when the process ends.
4. WHAT WE COLLECT — TELEPHONE
Stored in a SQLite database, telephone.db. Almost all of it is keyed by server, not by person:
| Table | What it holds | Notes |
|---|---|---|
| lines | Your server's listing name and the channel its phone jack is in. | Set by /phone register. |
| numbers | Your server's 4-digit number. | Unique; a number belongs to exactly one server. |
| settings | Do-not-disturb, auto-answer. | Per server. |
| line_filters | Which of profanity / slurs / links / GIFs to block. | All on by default, with per-server trust overrides. |
| filter_trust | Servers you trust to skip filtering. | You set this; we don't guess it. |
| call_blocks | Call pairs you've blocked. | Never routed. |
| speeddial | Numbered slots pointing at servers. | Per server. |
| call_alerts | Which roles or users want a ping when your phone rings. | The user half of this is the only user ID stored outside accounts.json. |
| rules_agreements | That your server accepted the code of conduct, and when. | Shown once per server. |
| call_log | Caller server, callee server, outcome, timestamp. | Metadata only. No message content. |
| voicemails | Sender's server display name and the message body. Capped at 20 per recipient. | The one place phone message text is stored on purpose, because a voicemail that isn't saved is worthless. |
| reports | Reporter, reported servers, reason, and the full transcript of the reported call. | Only created when someone runs /phone report. See Section 12. |
| blacklist | Servers cut off from the network, with the operator's reason. | Operators only. |
| stats | Global network counters, e.g. total calls. | Aggregate, no personal data. |
THE ONE THING WORTH UNDERSTANDING
The telephone relays messages between unrelated servers run by strangers. If your server registers a phone jack, everyone on the network can ring you and send text into that channel. That is the entire point of the feature — but it means you are choosing to expose that channel to strangers.
Use a dedicated channel you don't mind people posting in. Do not register a channel you also use for private staff talk.
5. WHAT IS ONLY IN MEMORY
Not written to disk, and lost whenever the bot restarts:
- Active games: player names, roles, room positions, chat logs, kill logs, voting records.
- Live call transcripts — the messages exchanged during a call currently in progress. These are held in memory and dropped an hour after the call ends, unless somebody filed a report.
- Who is ringing whom, and who is in the party bridge.
This is good news for privacy. It's also why a crash loses in-flight games. We consider that an acceptable trade.
6. WHERE THE DATA COMES FROM
- Directly from you — preferences, pronouns, catchphrase, custom name, accent colour, your I AGREE click on the code of conduct, opt-outs, and any
/phone reportyou file. - From Discord — your user ID and display name, and your server's ID, name, and channel IDs. The bot cannot function without these.
- From your server's staff — a member of staff runs
/phone registerand can set filters, DND, auto-answer, block servers, and pick alert roles. They are not required to and are not asked to collect anything else. - From other servers — when your server is relayed to, or receives a call from, another server. Their messages arrive in your channel under their own names. We don't add anything to those messages.
Scope of what we can read: in servers, the bot reads messages only in a registered telephone jack channel. It does not read other channels. It does not read your DMs except the DMs it is itself sending you. It does not keep a log of anything it can see.
7. WHAT WE USE IT FOR
Strictly to operate the features you asked for:
- Running games and keeping score.
- Giving you a phone number so other players can ring you.
- Routing calls, holding voicemails, and applying your content filters.
- Showing you your own stats when you ask with
/sus account. - Stopping abuse: enforcing the code of conduct, blacklisting servers, and reading transcripts a server has explicitly reported.
We do not sell, rent, trade, or broker your data. We do not use it for advertising. We do not build profiles. We do not run automated decision-making that affects you.
9. AI AND GROQ — READ THIS ONE
Computer's bots can be powered by a language model instead of a fixed script. When that is on, your meeting chat is sent to Groq, a third-party AI provider, so their model can write a bot's reply. This is the most significant data flow on this page, so it gets its own section.
Exactly what is sent
- Up to the last 14 lines of meeting chat, each with the display name of who said it. Bot lines are included. Human lines are included.
- Up to 200 characters of the message that triggered the bot's reply, quoted with the sender's display name.
- The bot's own role, personality, behaviour state, and target.
- Names of players a bot has decided it dislikes.
What is never sent
- Anything from outside the game channel. Task answers, panel clicks, phone calls, voicemails, call logs, and reports are never sent to the AI provider.
- Your Discord user ID, email, or any account data. Only display names appear in prompts.
- Anything at all, if AI is not configured — in which case bots use built-in scripted lines and function normally.
Your controls
- Personal opt-out —
/sus privacy ai:true. Your chat lines are removed entirely from AI prompts, and when you're the one who set a bot off, it's told only that a player spoke and that the content was withheld — no name, no quote. The bot still talks; it just can't quote you. - Server-wide opt-out — staff run
/sus privacy server_ai:true, and nothing from that server reaches a third party. This setting persists across restarts, so a deploy can't quietly undo it. - Global opt-out — the operator can disable AI for the entire network with
SUS_AI_ENABLED=false, which stops all AI calls code-path-wide. - Three independent layers. Your opt-out is checked on every prompt, not just when you set it, so it applies mid-game and doesn't depend on a flag someone forgot to flip.
Groq's own handling of API traffic is governed by Groq's privacy policy. Please read it if the details matter to you.
10. HOW LONG WE KEEP IT
| Data | Kept for |
|---|---|
| Game profiles, stats, preferences | Until you erase them. There's no automatic expiry. |
| Phone listings & numbers | Until your server unregisters, or you delete your listing. |
| Call log metadata | 90 days. Then swept automatically. Network-wide aggregate totals are kept forever. |
| Voicemails | Until deleted by the recipient or their staff. New ones push out the oldest past 20 per recipient. |
| Call reports & transcripts | 180 days, then swept. Kept only for calls somebody actually reported. |
| Live call transcripts | Memory only, dropped 1 hour after the call ends. Never written to disk unless reported. |
| Games, chat, voting records | Memory only, until the game ends. |
| Blacklist entries | Until an operator removes them. Not swept by the timers above. |
The sweeps above run automatically on a timer, not on request. Where a data type has no automatic expiry, we say so rather than implying one exists.
These windows are configurable by the operator. If they change, this table changes with them — the numbers here are meant to match the code, not to be decorative.
11. YOUR RIGHTS
You can exercise these yourself, from inside Discord. You do not need to email anyone or file a form.
- See everything we hold about you —
/sus exportsends you a readable summary plus the raw JSON of your profile. - Erase it —
/sus forgetdeletes your profile, releases your ship extension, removes your ring-alert subscription, and resets your stats. This cannot be undone. - Stop AI sharing —
/sus privacyshows your current settings and lets you opt out. - Check the AI status of your server —
/sus privacyreports whether the host has AI chat on. - Server-side export — staff can run
/phone data exportto DM themselves a JSON dump of everything the network holds about their server. - Server-side erasure — staff can run
/phone data forgetto wipe their listing, number, filters, trusts, blocks, speed dials, ring alerts, call history, voicemails, and any reports filed by or about the server. Blacklist entries are kept — that's the operator's record of a decision, not your data.
If you are under 18, a parent or guardian can ask us to erase a profile by making the same request. Just say so in the contact below and we'll take the word for it rather than interrogating a minor about their data rights.
Stats are cumulative counters with no backup of past games, so forgetting you resets the record with nothing lost in the void. The ship extension does become available for reassignment.
12. MODERATION AND SAFETY
The telephone connects strangers. That creates obvious risks, so here is the whole enforcement model:
- Every server accepts a code of conduct once, by clicking I AGREE, before any phone command works.
- Content filters for profanity, slurs, links, and GIFs run by default. A server can trust another server to skip filtering, but that trust is mutual and revocable.
/phone reportsaves the transcript of the call in progress and flags the involved servers for operators. Operators read these with/phone data reports— the reports were always reviewable, not just collected.- Operators can blacklist a server, which blocks its phone outright, tears down any call in progress, and stops it relaying messages.
Two things to be honest about:
- A report stores the full transcript of the call, including messages from every participant. Filing one captures other people's messages too. That is the point — a transcript nobody keeps can't be reviewed — but it does mean a report is not a private note to staff.
- Enforcement is ultimately on server staff. If your server's members break the rules and staff don't act, the whole server can be cut off. Choose servers you trust, or run one with moderation you actually pay attention to.
13. CHILDREN
Computer is not directed at children under 13, and we don't knowingly collect data from them. Discord's minimum age is 13 in most countries. The game is playable by teens and adults; the telephone network is explicitly a public space where the code of conduct forbids content inappropriate for minors, and violations get a server blacklisted.
If you believe a child under 13 has used the bot, contact us and we'll erase the profile.
14. CHANGES TO THIS POLICY
We may update this page as the bot changes. If a change materially affects what we collect or who we share it with — particularly anything in Section 9 — we'll update the page and adjust the effective date below.
This page is written to match what the bot actually stores. If this page and the bot ever disagree, treat the bot as the truth and this page as a bug — tell us and we will fix it.
15. CONTACT & EFFECTIVE DATE
Effective date: 5 October 2026.
Questions, corrections, or an erasure request: open an issue on the support server, or reach the operator on Discord as neptunetheii or by email at neptunetheii@proton.me. If this page is ever out of date, say so and we'll fix the page — that's a bug report like any other.
Related: Terms of Service · Back to the bot