Privacy Policy

Effective 2026-07-21. Written in plain language to accurately describe what this specific system does ; not a lawyer-drafted document, and not legal advice.

Who this covers

This policy covers dayznerdsquad.com, the admin dashboard, and .bOne itself (the Discord bot), all operated by Bench, the creator of DayZ Nerd Squad. It does not cover Discord itself, or any DayZ server host (like Nitrado) a community chooses to connect; those have their own separate privacy policies.

What we collect when you log in to the dashboard

Logging in uses Discord's own OAuth login screen, requesting only the identify scope, the minimum Discord allows. That gets us your Discord user ID, username, and avatar. We never request your email address, and Discord doesn't hand us one with this scope.

Your Discord access token itself is used once, at the moment you log in, to ask Discord who you are; it is never stored.

On every successful login, we also log the IP address you logged in from and a coarse location (city/region/country) looked up from that IP via a third-party lookup service (ip-api.com). This is a security/audit log, capped at the 200 most recent logins, and visible only to the bot's developer, not to individual server admins.

What gets stored when your server uses the bot

Everything .bOne stores for a Discord server it's added to lives in one file scoped to that server, kept separate from every other server's data. Depending on which features a server's admins turn on, that can include:

Server configuration: channel routing, role IDs, and (if configured) a Nitrado API token and FTP credentials for that server's DayZ server, used to read server logs and manage in-game files
Discord-user-linked balances and stats for in-server economy/game features (currency balances, cooldowns), tied to Discord user IDs and usernames
Self-reported links between a Discord account and an in-game gamertag; these are typed in by the player or an admin and are not independently verified
Gamertag-linked gameplay data: kill/death counters, and in-game position samples used for heatmaps and activity tracking, tied to a gamertag rather than a Discord identity
Moderation and behavior-detection records an admin configures
Free text players submit themselves: suggestions, and notes/evidence attached to player reports

A DayZ server's Nitrado token and FTP password are encrypted at rest when the operator has encryption configured on the host (see "How we protect it" below); everything else in that list (channel IDs, map name, a self-reported gamertag) is not a secret and is stored as plain text.

What's shared across every server running the bot

A small amount of data isn't scoped to one server, because the feature itself is cross-server by design:

A global watchlist of player reports, searchable by gamertag across every server that opts in; each report includes which server filed it, a category, and free-text notes an admin wrote. This is the most sensitive data the system holds, since it's written to be shared between communities.
Global currency balances for the bot's cross-server casino and expedition mini-games, tied to Discord user IDs.

If your server's admins submit a report to the global watchlist, be aware that report, including any notes attached to it, is visible to admins of other servers running the bot, not just your own.

Cookies

The dashboard sets two cookies, both required for it to function; see the separate Cookie Policy for exactly what they contain.

Who we share data with

We don't sell data, and we don't use any advertising or analytics service; there isn't one integrated anywhere in this system. Data only ever reaches:

Discord: to run the bot and log you into the dashboard.
Nitrado, and your own server's FTP host: only if your server's admins connect one, and only to do what they configured it for (reading logs, managing server files).
Anthropic's Claude API: only if a server's admins have an AI-powered feature (like /ask) enabled, and only the text of that specific request.
ip-api.com: the dashboard-login IP lookup described above.

How long we keep it

The moment the bot is removed from a server, its Nitrado token and FTP password are automatically cleared. Everything else: rotation history, economy balances, stats, tickets, and the rest of that server's usage data, is kept, so a community that re-adds the bot later doesn't lose its history. If you'd like the rest of a server's data deleted too, reach out (see Contact below) and we'll remove it by hand.

The dashboard login audit log is capped at the 200 most recent entries and older entries roll off automatically.

Your choices

You can unlink your own Discord-to-gamertag link at any time with /link remove. For anything else: deleting a suggestion you submitted, removing yourself from a server's stored data, or a global watchlist correction, contact Bench directly.

How we protect it

The dashboard is served over HTTPS. Login sessions are a signed cookie our server can verify wasn't tampered with; they don't sit in a database anywhere. Where the operator has enabled it, DayZ server credentials (Nitrado token, FTP password) are encrypted at rest; that protects a leaked backup or data file on its own, but, like any single-server setup, doesn't protect against someone who compromises the server itself. Nothing here is a substitute for keeping your own Discord account secure (enable 2FA on Discord).

Age

This bot runs on Discord, which requires users to be at least 13. DayZ, the game this community is built around, is rated for mature audiences (17+/18+ depending on region); this isn't a service aimed at children.

Changes to this policy

This policy was last updated 2026-07-21. If what we collect changes in a meaningful way, this page will be updated to reflect it; there's no separate mailing list or notification system, so check back here if you want to know what changed.

Contact

The fastest way to reach Bench (the operator of DayZ Nerd Squad and .bOne) is directly in the DayZ Nerd Squad Discord server.