Privacy Policy

1. What we collect

a. From Discord, when you sign in

• Your Discord username, global display name, avatar, and user ID (Discord's identify scope — the minimum needed to identify you). We use it only to identify your deadmap account.

b. From the probe — your browser, your session, your choice

The probe is a userscript you install in your own browser. It runs only while your game page is open, only on your machine, and only sends what it reads from your own session:

• your character's position in the city grid (cell coordinates — the probe transmits nothing finer);
• the state of the building you are in (type, integrity, power, barricades);
• threat and occupant counts for the area you are in, exactly as the game displays them to you;
• in-game events your session displays (action lines, searches, combat lines) — these may include names that the game itself shows you;
• the name and ID of your linked character, plus any profile fields you fill in (group, notes, reviews, revive requests, settings);
• the probe's version number and timestamps — used to tell which client build reported a line, so game-text changes can be diagnosed.

We do not run any process that reads other players' browsers or the game's servers: what deadmap knows about a player is what that player's own probe chose to report.

c. From the web pages

• your deadmap API token (generated by deadmap; stored only in your browser's local storage and sent only to deadmap);
• your display preferences (also browser local storage).
• deadmap sets no cookies.

2. What we do not collect

• IP addresses. Server access logs record only the hosting provider's proxy address — never yours.
• No tracking pixels, analytics, advertising or marketing services, or third-party embeds of any kind.
• No data about other players beyond what their own probes report about their own sessions.
• We do not sell, rent, or trade any data. There is no advertising on this site.

3. How we use it

To render the shared map and its layers, produce the daily snapshot archive, and power your own dashboard (profile, reviews, XP, searches, revive requests). Nothing else — the data is not used for advertising, profiling, or any purpose beyond the map itself.

4. Who can see what

• Public (no login): the map layers, building/property lookup, and the snapshot archive. These contain game-state data (buildings, power, populations), not your identity.
• Logged-in deadmap users: the characters, locations, and profile details that all users report — including yours — since the shared map is the product.
• The operator: administrative tools can view reports, profiles, and events, and are used for maintenance and to answer deletion requests.

5. Storage, security, and retention

Data is stored in a single database on a hosting provider (NearlyFreeSpeech.NET, United States) and served over HTTPS only. Accessing account data requires your token (or the operator's administrative login). An off-box backup of the database is kept on a second machine on a rotating schedule (7 days / 4 weeks / 12 months). We keep your data until you ask us to delete it.

6. Deleting your data

Contact the operator (below) and we will delete your account, your character's profile and reports, and any other data tied to you. Already-published daily snapshots are historical layer images (aggregate game state, not identities) and remain in the archive.

7. Children

deadmap is not directed at people under 16, and we do not knowingly collect data from them. If you believe a child has provided data, contact us and it will be deleted.

8. Changes to this policy

If we change this policy, we update the dates above and this page; material changes will be noted on the home page. The current date is the effective one.

9. Contact

Data questions, deletion requests, or anything else: contact the operator at privacy@fusr.info. The operator acts pseudonymously — no personal identity is published on this site, and all correspondence is through that address.