Privacy policy
Last updated 2026-09-26.
Warcaller relays a caller's voice from one Discord channel into many, so this policy starts with what happens to that voice, then covers everything else: what is stored, for how long, who else sees it, and how to get it back or delete it. It applies to warcaller.app, the dashboard, and the Warcaller Command and Warcaller Squad bots.
1. Voice is never recorded
While a relay runs, voice packets travel from the caller's Discord client to our listener bot, across our own servers, and out to the squad bots that play them in your party channels. On that path we:
- never write audio to disk, and never store it in a database or a log file;
- never decode it, so no one at Warcaller and no machine of ours ever turns it into sound or text;
- pass each packet straight on as it arrives, holding it no longer than it takes to send, and never more than a fifth of a second;
- forward the caller's encoded packets byte for byte, exactly as their Discord client produced them.
Between the listening bot and the squad bots the packets cross a message bus that keeps nothing: it hands each frame to the bots waiting for it and drops it, and that server is configured to write nothing to disk at all.
Talkback: when a party channel can answer
For a party channel a server admin has switched talkback on, the squad bot in that channel is no longer deafened, so that channel's encrypted voice packets reach our servers. We open (decrypt) only the packets of one person at a time: a member the server gave its talk-back role who is holding their priority push-to-talk key, and we play those packets, still encoded and never decoded, in the command channel. Everyone else's packets are discarded the moment they arrive, without being decrypted. When nobody holds a key, nothing in that channel is decrypted at all. The bot shows as undeafened in the member list while the switch is on. To decide whether a packet is forwarded we process voice-state and speaking events (mute, deafen, and the priority flag) as they happen and keep none of them.
Discord encrypts voice end to end between the caller and our bots, and again between our bots and the party channels. There is no recording, no transcript and no archive, because nothing is kept. What our servers do keep about a relay is described in section 3: who started it, when, and which slots were used.
2. What we cannot see
Some limits are built into how the bots connect to Discord rather than promised in a policy. Our bots ask Discord only for server, voice-state and member information. They do not have the message content permission and have no code that reads messages, so:
- we do not receive the text of messages in your server, in any channel, including channels our bots can see;
- we receive a slash command only when someone runs one of ours, and then only its name, its options and who ran it;
- we do not see your direct messages, attachments, or anything in servers where our bots are not installed.
3. What we store, and why
About you. Your Discord account id, name and avatar, the email address on that account, and the session that keeps you signed in. The email is used for account and billing notices when a Discord message cannot reach you, and for product news only if you turn it on yourself.
About your server. Its name and icon, the channels and roles you pick, your slot settings, and which of our bots are installed. This is the setup your relays run on.
About your relays. When each one ran, who started it, which squads joined and why it ended, any starts you schedule, and a log of who changed what in the dashboard. It is what the board shows you, what lets a relay survive a restart mid-fight, and what a server's admins can check afterwards.
About your plan. From Stripe: which plan the server has, its status, and the trial and renewal dates. Card numbers never reach our servers.
To keep it running. Logs of what the service does, such as errors, commands and sign-ins, used to keep it working. No audio is in any of it.
We collect nothing else. There is no analytics service, no advertising pixel, no session recorder and no profiling. We do not sell, rent or trade personal information, and we never have.
4. Who else is involved
Running the service means four other companies handle some of this data on our behalf or alongside us:
- Discord operates the platform the bots live on. Everything the bots do happens inside Discord, under Discord's own privacy policy as well as this one.
- Stripe processes payments. We send it your Discord id, the server id and the plan so a subscription can be matched to a server; it holds the card details, we never do.
- Amazon Web Services sends the account and billing emails described above.
- Cloudflare sits in front of the website, terminates the encrypted connection and absorbs attacks, so it sees requests to warcaller.app.
Beyond those, we disclose data only when the law compels it, when it is needed to protect someone's safety or our rights, or if the service is ever sold or merged, in which case the buyer is bound by this policy and you are told before anything moves.
5. Cookies
One cookie, for your sign-in session. It is HttpOnly and Secure, lasts 30 days, and is deleted when you sign out. There are no analytics, advertising or preference cookies, so there is no consent banner to click through.
6. How long things are kept
- Your account: until you delete it. Deletion is immediate, not a scheduled job.
- Sign-in sessions: 30 days, or until you sign out.
- Server settings, relay records, schedules and audit entries: as the server's own history, for as long as the server is set up with Warcaller. Removing our bots ends the relays and stops us using the settings; an admin can write to us to have them erased.
- Subscription records: kept while the plan runs and afterwards as long as tax and accounting law requires.
- Backups: taken regularly, kept in secure storage for a short period and then destroyed. Deleting your account is final, backups included.
- Logs: up to 90 days, then deleted.
7. Keeping it safe
Traffic to the site is encrypted. Discord tokens are encrypted before they are written to the database, and session cookies are stored only as hashes, so neither can be used to sign in as you or to act on your Discord account. The bots hold the narrow Discord permissions listed in the setup docs, never Administrator. We take regular backups, keep them in secure storage and verify each one automatically after it is written. No service can promise perfect security; if a security incident ever affects your data, we will tell you and the relevant authority promptly.
8. Your rights and how to use them
Most of this is self-service on the Account page of the dashboard, without contacting anyone:
- See it all: “Download my data” returns everything tied to your account as a file.
- Delete it: deleting your account cancels any plan you pay for, closes your record with Stripe, and removes your profile, sessions and Discord tokens at once. Your Discord id is also cleared from the relay history and schedules that recorded it, so those entries survive without naming you. Afterwards we keep a single marker that cannot be turned back into your account, whose only job is to make sure the deletion holds. Settings that belong to a server stay with that server until its admins remove the bots or ask us to erase them.
- Choose your notices: pick whether billing notices arrive as a Discord message or by email, and whether you want product news at all. News is off unless you turn it on.
- Walk away entirely: kicking our bots from a server ends its relays and marks them uninstalled.
Depending on where you live you may also have the right to correct data, to restrict or object to processing, or to receive it in a portable form. Write to us and we will do it within 30 days. If you are in the European Economic Area or the United Kingdom, our lawful bases are performing our contract with you (running the relay and the subscription), our legitimate interest in keeping the service secure and working, and your consent for product emails, which you can withdraw at any time. You may complain to your national data protection authority. If you are in California, we do not sell or share personal information as those terms are defined there, and we will not treat you differently for exercising a right.
9. Where your data lives
Our servers are in the United States, and the companies in section 4 process data there and elsewhere. If you use Warcaller from outside the United States, your data is transferred there, protected by the contractual safeguards those providers offer and by the practices in this policy.
10. Age
Warcaller can only be used through Discord, which requires its users to be at least 13, and older in some countries. We do not knowingly collect data from anyone below that age. Tell us if you believe we have, and it will be deleted.
11. Changes
When this policy changes, the date at the top changes with it. For changes that meaningfully affect what we do with your data, the accounts that pay for a plan are notified before the change takes effect.
12. Contact
Privacy questions and requests go to [email protected], answered within 30 days and usually much sooner. For everything else, our Discord server is the place.
The terms of service cover the rest of the agreement, and the audio and privacy doc explains the relay path in more detail.