Privacy and security
The less we keep, the less there is to lose. That is the whole policy; the rest is detail.
This is not a telephone line
Guild Phone is a closed network for players. It is not connected to the public telephone network, and you cannot call emergency services from it — no 911, no 999, no 112. If you need help, use a real telephone.
We do not sell anything about you
Not your name, not your characters, not who you called, not what you said. There is no advertising on this site, no analytics service and no tracking pixel. Selling it is not a line of business we want, and holding it is a risk we are not interested in carrying.
One third party is involved and it is worth naming: backups are copied to a storage provider, so that losing this machine does not lose your guild. They are encrypted before they leave here — see below.
Calls are not recorded
No part of this system records the audio of a call. Not character to character, not guild channels, not raid rooms, not pages. There is no recording feature to switch on by accident, because nothing we run can record.
What we cannot prevent is somebody on the call recording it themselves. You connect your own handset, and so does everyone else on the raid — a desk phone, a softphone, a browser, or a mobile held up to a speaker. Any of those can record, we have no visibility into them, and no control over them. This is not peculiar to us: it is true of every voice platform people run raids on, including the one your guild is probably leaving.
So we have a policy, and this is it. Do not record a call unless everyone on it knows. Not a checkbox somewhere — actually told, in words or in writing, by you, before you start.
The reason is that this network puts people in the same room across borders, and the law on recording a conversation differs by country and by state. In many places it is legal only if everyone agrees, and a raid with forty people on it may well span several of those places at once. Nobody on a raid call can know which rules apply to the other thirty-nine. We are not going to pretend that is a problem we can solve for you, so the rule is the strict one.
Recording for content is a real reason and we are not against it — a streamer capturing a progression kill is doing something worth keeping. Everyone on that call still needs to know it is happening. Recording as a matter of routine is not supported here, and a guild that does it quietly is doing something we would act on if we were told.
Voicemail is the one exception, and an obvious one: a message somebody leaves is a recording, kept so it can be played back, and deleted when it is deleted. Guilds also have an officers' mailbox, so a message left at a guild's reception is heard by whoever holds that rank — not by one named person.
Calling from a browser uses your microphone, and the browser will ask before it does. Audio passes through our server rather than directly between players, which is what stops a call revealing your home address to the other end.
Chat is stored, because chat is useless without it
This is the part that differs most from the telephone, so it is worth being blunt about.
- We keep what you type. Direct messages and messages in guild rooms are held on the server so that scrolling back works when you return.
- For sixty days, then they are deleted automatically. Not kept for us to read later. A guild chat is a conversation, not a record, and after two months nobody is coming back for it. A raid's own channel stops taking new messages when the raid ends but stays readable for the same sixty days, and then goes with everything else. Chat is included in the encrypted backups described below, which is the one place a message can outlive its sixty days — by at most a fortnight; the Backups section is exact about it.
- They are not end-to-end encrypted. Messages are encrypted in transit, but somebody with access to the server could in principle read them while they exist. Treat guild chat the way you would treat any forum: fine for raid times and arguments about loot, wrong for anything that would hurt you if it leaked.
- Who is online is visible to your guild, as it is in any chat system. You can appear offline from your client if you would rather not be.
What we keep
Only what it takes to put a number on a character, connect a call, and run a guild's rooms and raids:
| Who you are | the identifier Battle.net gives us when you sign in, and your BattleTag. Never your password — Blizzard handles the sign-in and we never see it. |
|---|---|
| Your characters | name, realm, class, guild and rank, as the game already shows them to your guild. Nothing from outside the game. |
| Your numbers | the permanent number each claimed character has, the login your phone signs in with, and whether a line rings or is set to do not disturb. |
| Your timezone | so that times on screen and times read out over the phone are yours rather than somebody else's. |
| Raids | which raids you signed up for, as which character, and in which roles. Roles are read back from the last ninety days of sign-ups, which is how you end up in the right spec rooms without picking one. For a scheduled raid we also keep who joined its call and how long for — see below. |
| Call status | whether a handset is registered and whether it is on a call — read live from the phone system when you load the page, and never written down. We do not keep a record of who you call. |
| Desk phones | if you provision a physical handset, the hardware address it first claimed its configuration from, so that nobody else can claim it afterwards. |
Things other people write about you
An officer can bar somebody from their guild's raids and record a reason for it. That text is written by them, about you, and is visible to the officers of that guild. It is their opinion rather than a verdict: it stops you joining that guild's raids and does nothing anywhere else on the system, and it does not cut off your telephone.
What we do not keep
No email address. No payment details — there is nothing to pay for. No home address, no real-world phone number, no contact list, no call recordings, and nothing about what you do anywhere else.
Problem reports
If you send a report, we keep what you typed, and — so that somebody can act on it — whether a handset was registered at the time, for each line you hold. Not which line, and not which character: a line number names you as surely as a name does. We do not keep your BattleTag with it, and the report is not held against your account either, so there is nothing to look you up by.
Two things about the request itself are kept: your browser’s user agent, which is how one broken app is told apart from a fault that is ours, and the first three parts of your network address, which is how a flood of reports from one network is slowed down. Nothing else.
That is a deliberate cost. It means we cannot find you afterwards to help you in particular — only fix the thing you found, for everybody. There is no email address on file either way, so no reply was ever possible.
Reports are copied into our private issue tracker. They are not public, and because we hold no email address for anybody, nobody can be contacted about one. That cuts both ways: no spam, and no reply.
No record of who called whom, with one exception
Telephone systems normally keep call detail records — a line per call saying who rang whom, when, and for how long. Ours does not. It is switched off at the source rather than merely left unconfigured, and the records that had accumulated before we noticed have been deleted.
We don't keep a record of who you call. Scheduled raids are the exception, and it's your guild's record: who joined the raid call and how long for, because that's what a raid roster is. It is kept against that raid, for the guild whose raid it is, and it is who and when and for how long — never what was said, because nothing we run can record audio.
Rooms you open yourself are not recorded. A room from the request-a-number button is just a call: nothing is written when you join it, nothing when you leave, and there is no count of either. One thing is written while you are in any room, so the room page can show who is speaking: while you talk, the server holds the room and your call's channel id (a number Asterisk gives each call, not your name or phone number), and deletes it when you stop talking or hang up. Nor is there any record of one character ringing another. The raid record exists because a raid roster is a thing a guild already keeps; everything else stays as it was.
That is a deliberate cost: it means that if you report a problem with a call, we cannot look it up afterwards. We would rather be unable to answer that question than hold the answer to it. There is no legal requirement on us to keep such records, and if one ever arises this page will say so before it happens.
Server logs
Like every website and every telephone system, the servers keep short operational logs, and those do include the network address a request came from. They exist to find faults and to block the people who spend all day trying to break in. They are not used to build any picture of you.
Concretely, because "we delete them eventually" is not a commitment:
- Web server logs, which hold a full address per request: seven days.
- Chat server logs, which name which character signed in and from where: seven days.
- System logs: seven days, and capped by size as well, so a noisy week discards them sooner rather than later.
Security
We are not going to publish a map of how this is defended, because the only people who benefit from that are the ones attacking it. What is reasonable to tell you:
- The sign-in is Blizzard's own. We never receive your Battle.net password.
- Your telephone credentials are separate from your Battle.net account, and you can replace them yourself at any time without affecting anything else. The same credential signs you in to chat, so replacing it replaces both.
- The service is attacked continuously — automated attempts to guess telephone credentials arrive by the hundred thousand daily. That is normal for anything with a phone number, it is expected, and it is accounted for.
- If something does go wrong, we will say so plainly rather than quietly.
Backups
A machine can die, and a guild that lost its numbers because of that would be entitled to be furious. So there are backups, and you should know what is in them.
- What: the database — everything on this page under "What we keep" — voicemail recordings, and chat messages. Chat is backed up because a server fault that wiped a guild’s conversation would be our mistake and their loss, and that is not a trade worth making. It is encrypted before it leaves this machine, like everything else.
- Where: on this machine, and a copy with a storage provider, because a backup on the machine it is backing up is not a backup.
- Encrypted before it leaves. The off-site copy is encrypted here, with a key the storage provider does not have. They can see that files exist and roughly how large they are. They cannot read them, and the filenames are encrypted too, so they cannot tell a database from a voicemail.
- Kept fourteen days, then deleted automatically in both places.
That has a consequence worth being exact about. Chat still deletes itself after sixty days. But a backup taken before a message expired can hold it for up to fourteen days longer, which is how long backups are kept. After that it is gone from both. So the honest version of “sixty days” is “sixty days, and at most seventy-four in an encrypted backup nobody reads”.
Removing your data
Ask and it goes. There is no retention policy protecting our interests here, and no form to fill in. Removing an account releases its numbers permanently rather than passing them to somebody else.
Being precise about what "goes" means, because most policies are not: you are removed from the live system straight away. Backups taken before that still contain you, and those age out within fourteen days — we do not reach into old backups to edit them, because a backup somebody has been editing is not one you can trust in the moment you need it. After a fortnight there is nothing anywhere.
Honest limits
This is a small, new service run by one person. It is not a company, there is no security team, and it has not been audited by anybody. Treat it as what it is: a telephone and chat system for a game, built carefully, but new. Do not put anything through it that would hurt you if it leaked.
Last reviewed against the running system on 6 October 2026.