Privacy Policy

DayZ Hub ("the Service": the DayZ Hub bot and dashboard, DayzHUB Console and the DayZ Hub mods store) is operated by DayzHUB from the Netherlands. For any privacy question or to exercise your rights, email [email protected] or contact us through the DayZ Hub support Discord.

• Our customers' data (your DayZ Hub, Console and store accounts, your settings, your payments): we decide how it is used, so we are the data controller.
• Players on a game server connected to DayzHUB Console: the server's owner decides what the Console records and how long it keeps it, within their plan. For that data the server owner is the controller and DayZ Hub is their processor: we only process it to run the Console for them. If you play on such a server, the owner is your first point of contact (see section 9).
• Members of a Discord server that uses the DayZ Hub bot: the server's owner decides which bot features are on, and so which data about the server's members is processed. For that data the server owner is the controller and DayZ Hub is their processor (see section 4).

DayZ Hub bot and dashboard

• Discord account data (via OAuth login): your user ID, username, avatar and the list of servers you manage. We never see your Discord password.
• Server configuration: settings you save (channel IDs, role IDs, messages, feature toggles).
• Feature data: what features need to work, such as suggestions and votes, giveaway entries (user IDs), ticket records and transcripts, poll votes and vote counts, and, only if you enable Steam verification, members' SteamID64 and a CFTools reference ID. Section 4 describes what the bot reads and stores about the members of your Discord server.
• Payment records: plan, amount, date and PayPal transaction or subscription ID. We never see or store your card or PayPal login details; payment is processed entirely by PayPal.

DayzHUB Console accounts

• Your name; your email address if you sign up with email, and your password stored only as a secure hash; your Discord or Steam ID and avatar if you log in with them; when you accepted the terms; login security data (failed attempts, temporary locks) and your last login.
• For each game server you connect: its details and settings. The RCON password is encrypted at rest; the agent's API key and your API tokens are stored only as hashes.
• Unless you turn it off in Settings > Server details, a connected server with a public address is shown in the public server list at dayzhub.cloud/servers: its public name, address, map, country, player counts and the last 24 hours of player counts. No player names or Steam IDs are shown there.

Game servers connected to the Console (players' data)

• Players' Steam IDs and in-game names (including earlier names), when they join and leave, sessions and playtime.
• Positions for the live map, and on plans that include it, the history of where players went (Player Route).
• Kills, deaths, hits and damage (weapon, body zone, distance), in-game chat, objects placed, built, dismantled or destroyed, door and lock interactions, and admin actions.
• Events from mods the owner connects, such as LBmaster and TheModBase (TB) mods: trades, vehicles, insurance, houses, stalls and premium.
• Reports players send from the game, notes and watch flags staff add, bans and ban-list entries (reason, evidence links), and ban appeals sent through the public form (Steam ID, name, the contact given and the message).
• If the owner turns on Steam checks: players' public Steam data (VAC and game bans, account age, profile visibility).
• For server owners, the Console can show a risk label per player (low, watch, high), based on public Steam data and in-game statistics (hits, kills, speed warnings, reports). It is a pointer for staff. DayZ Hub does not act on it: the server owner decides what to do, and nothing is done to a player automatically by DayZ Hub.
• DayzHUB.Console can point a server's owner and staff to accounts that may belong to the same person. For this it compares data the Console already holds for that owner's servers: the names an account has used, when it was online, when it was first and last seen, and entries of the ban lists the server uses. The comparison happens when a moderator opens a player page, nothing new is stored, and data of different server owners is never combined. The result is only a starting point (Pro plan), shown with its reasons; potential matches do not prove common ownership, and nothing is done automatically because of them.
• If a server owner opts in, the Console can show a player's number of active bans on other opted-in Console servers, by category (cheating, griefing, other). Only that number and the category names are shared: not the reason text, not the server, not the owner. It is a pointer for staff; nothing is done to a player automatically and the owner decides. Bans with an open or accepted appeal are not counted, and where the owner has switched on the appeal form of the ban list, players can appeal on dayzhub.cloud. Nothing is shown until at least three servers owned by at least two different owners take part. A staff member can also look up one exact Steam64 ID at a time in Moderation; the result is the same (a number, the categories and the month of each ban, never the reason text, the server or the owner), each lookup is limited per hour and is recorded in the server's audit log with who looked it up and when.
• If a server owner switches on IP bans for their server (Pro plan, off by default), the staff of that server can enter an IP address or a range of addresses to be banned. An exact IPv4 address is written to the game server's BattlEye ban list, where BattlEye keeps it in readable form on that server until the ban expires or is lifted. BattlEye cannot take ranges, so a range is never sent to BattlEye: the Console enforces it itself and kicks a matching player within seconds of joining, which needs the Console's RCON connection to the server. DayzHUB.Console itself keeps the address or range only in encrypted form, with a shortened display form (the first two numbers) and a keyed one-way hash of it as the ban's unique key, for as long as the ban lasts; when the ban ends, the address, the range and the hash are deleted. While IP bans are on, the Console reads the addresses in the RCON player list in memory only, to enforce ranges, to make sure that staff and whitelisted players are never kicked and to check that a new ban would not hit them while they are online; these addresses are not stored. IP bans are written only to servers of the same owner and are not returned by the API. The legal basis is the server owner's legitimate interest in keeping their server safe from ban evasion and abuse (Art. 6(1)(f) GDPR). You can object to the server's admins or to us at [email protected].
• If a server owner switches on alternate-account hints for their server (Pro plan, off by default), DayzHUB.Console reads the network address that BattlEye reports for players connected to that server and turns it into a keyed one-way fingerprint; the address itself is held in memory only for that step and is not stored. The fingerprint is kept for 14 days and is used only to show that server's owner and staff a hint ("connected from the same network") on a player page, next to the other reasons and the note that potential matches do not prove common ownership. It is never combined with data of other server owners, is not used for any automatic decision, and is deleted when the server or the account is deleted. The legal basis is the server owner's legitimate interest in recognising ban evasion (Art. 6(1)(f) GDPR). You can object to the server's admins or to us at [email protected].
• We do not store players' IP addresses in readable form: they are removed even from raw RCON replies shown in the Console. What the Console derives from an address, and only when a server owner switches it on, is described in the two points above.

Mods store

• Your Discord ID and name, the mods you own and why (purchase, test version, subscription or founder access), the game servers (IP address and game port) you add for each licence, with the previous one for 48 hours after a move, logs of licence checks (server IP and port, mod, time and result), and your acceptance of the Mod Licence Terms (which version, when, in which language and for which mod).
• Licence check from your game server: besides its IP address (read from the connection) and game port, the check receives the server name (up to 120 characters), whether the server has a password (yes or no; the password itself is never sent), the player limit, and the names and versions of the DayzHUB mods that run. We use this to decide whether the mod may run and whether a server qualifies as a free test server. The server name, the password flag and the player limit are used at the moment of the check and are not stored in the check log. The licence service keeps one record per server (IP, port, the server name the mod announces, up to 40 characters, the mod versions, the result of the last check, and when the server was first and last seen); see Retention & deletion.
• Team members: if you add other people to a mod you bought, we store their Discord ID, who added them and when, give them the mod's Discord role and let them download the mod. You can remove them at any time.
• Test version: we store the end date of a 7-day test version and send you a Discord message 3 days and 1 day before it ends.
• "Add this server" link: a mod can print a link (dayzhub.net/my-mods?add=IP:PORT&mod=...) in your server log. It carries only the server address and the mod name, stores nothing by itself, and adds a server only after you sign in and press the button.
• Receipts for paid mods: receipt number, date, the mod, the amount, the payment method and PayPal reference, and the billing details you choose to add on your receipts page. We never see your card or PayPal login.
• Discord role: when you buy a mod, our bot gives your Discord account that mod's buyer role in the DayzHub Discord server, if you are a member. It is used to notify owners of that mod about its updates.

Donation Shop

• When someone buys in a server's shop, we record the order for that server's owner: the buyer's Discord ID and name, the product, the amount and currency, the payment reference and the email address that PayPal or Stripe shares with us. The payment itself is processed by PayPal or Stripe and we never see or store card or login details. We use this to deliver the purchase, show the sale to the server owner and work out the platform fee.
• The server owner can see their shop's orders and buyers in their dashboard.

Technical data and cookies

• IP address and request logs (handled by our CDN and host) for security and abuse prevention.
• Only necessary cookies: your login session, your language choice and your cookie choice. No advertising or tracking cookies.

This section is for members of Discord servers that use the DayZ Hub bot, and for those servers' owners. The owner decides which bot features are on, so the server owner is the controller and DayZ Hub is their processor for this data (see section 2). The bot does what is described here only for features the server has switched on in our dashboard.

Member events (Discord's "Server Members" access)

When someone joins or leaves the server, or their nickname, roles or timeout change, Discord sends the bot that member's user ID, username, display name and nickname, avatar, account creation date, whether the account is a bot, roles, join date and timeout. The bot uses this for:

• welcome and goodbye messages and image cards, roles given automatically to new members, and join alerts for staff;
• Join Guard raid protection: checking new accounts (account age, default avatar, name patterns, unverified bots) and logging them, giving them a quarantine role, timing them out, kicking or banning them, as the server chose. Joins per minute are counted in memory only;
• invite tracking: matching each join to the invite that was used, for invite leaderboards and invite contests;
• server logs: member joined, left, nickname, role and timeout changes, posted to the server's own staff channel;
• clean-up when a member leaves: their clan seat, group-finder post and invite credit are removed.

The dashboard also reads the server's member list from Discord to show the member roster (including which members have the server's verified role), the leveling leaderboard and member pickers. That list is kept in memory for two minutes and is never saved. The bot keeps member details in memory for about an hour at most, except for members who are in a voice channel.

Message text (Discord's "Message Content" access)

The bot reads the text of messages, and the names and links of attachments, in the channels it can see, only for these features:

• Ticket transcripts: when a ticket is closed, the ticket channel's messages are saved as a transcript. If staff chose a transcript log channel, a plain-text log of the last 100 messages is also posted there.
• Message logs: when a message is deleted or edited, its earlier text is posted to the server's private staff log channel.
• Automod: word and invite-link filters on message text and attachment names. A matching message is deleted and logged, with up to 1,000 characters of its text, to the staff channel.
• Starboard: a message that gets enough star reactions is reposted, with its text and image, to a highlights channel.
• Vote rewards: in one channel the server chooses, the vote confirmations posted by the vote site's bot are read to credit the in-game name.
• Leveling: optional bonus XP for long messages and for messages with attachments. Only the XP is stored.
• Suggestions: a suggestion typed as a message in the server's suggestions channel is reposted and saved as a suggestion.

Messages the bot sees are kept in its memory for about 90 minutes at most and are not saved otherwise. Copies posted into a server's own channels (logs, transcript files, starboard posts) are controlled by that server's staff under the server's own Discord permissions; we keep no copy of them.

Presence (not collected)

The bot does not use Discord's "Presence" access and never asks for it. We do not receive or store anyone's online status, activities (such as the game they are playing) or devices.

What we store in our database

• Ticket transcripts: ticket number, category, who opened it (user ID and username), who closed it and why, the answers to the ticket form and, for each message, the author's user ID and username, the text (up to 2,000 characters, including the text of the bot's own messages), up to 10 attachment links and the time.
• Ticket records: ticket number and channel, who opened, claimed and closed the ticket, members added to it, category, form answers, close reason, rating and times.
• Invite tracking: the inviter's user ID, the user IDs of the members they invited with their join times, and counts. When a member leaves, they are removed from their inviter's list. The member's own record (the members they invited, and their counts) stays while the bot is in the server.
• Join records (join report, on plans that include it): member ID, join time, invite code, inviter ID, whether a welcome message was sent, and when and how the member verified.
• Join Guard log: user ID and username, the reasons it was triggered and the action taken.
• Leveling: member ID, XP and level.
• Suggestions and vote rewards: suggestion text, author ID, votes and staff decision; the in-game names from vote confirmations with monthly counts, and which Discord account claimed a reward for which name.

Other features store only what they need to work, as listed under "Feature data" in section 3 (for example warnings, giveaway entries and clan membership).

How long we keep it

• Ticket transcripts: for the period the server chooses, 30, 90, 180 or 365 days after the ticket was closed (180 days unless the server changes it, never more than 365). The server's admins can also switch transcript saving off and delete any transcript, or all of them, at any time.
• Closed ticket records: at most 365 days after the ticket was closed.
• Everything else above: while the bot is in the server, until the server's admins wipe it in the dashboard (invite and leveling data), or until you ask us to delete it.
• When the bot is removed from a server, or leaves it, all of that server's data is permanently deleted 3 days later, also if a paid period is still running (the subscription for that server is then cancelled). Re-adding the bot, or renewing a lapsed subscription, within those 3 days cancels the deletion.

Who can see it

• That server's admins (people with the Manage Server permission, checked through Discord when they log in) and the team members they invite through Team Access, limited to the dashboard sections they were given. Only admins can delete transcripts.
• DayZ Hub staff, only when needed to give support, fix a problem or answer a data request.

We do not sell this data or share it with anyone else, and we do not use it for advertising, profiling or AI training.

Deleting data and other requests

• Server owners and admins can delete data themselves in the dashboard: a single ticket transcript or all of them (and switch transcript saving off), and all invite-tracking data or all leveling data. To have all of the server's data deleted, remove the bot: everything is deleted 3 days later, as described above. For anything else, or to have it deleted straight away, email [email protected] with the server's name or ID.
• Members of such a server should contact its staff first, since they decide which features are on. When you leave a server, you are removed from the list of whoever invited you, but your own invite-tracking record there (the members you invited and your counts) stays while the bot is in that server. You can also email [email protected] to see or delete data about you. We will help the server's owner answer and act within 30 days.

• To provide the bot, dashboard, Console and mods you signed up for: performance of a contract (GDPR Art. 6(1)(b)).
• To secure the Service, enforce mod licences (including the licence check from your game server and the free test server check), prevent abuse and keep operational records: legitimate interests (Art. 6(1)(f)).
• To keep accounting records of payments and handle refunds and disputes: legitimate interests (Art. 6(1)(f)).
• Where you opt in (for example the review promo): consent (Art. 6(1)(a)), which you may withdraw at any time.
• Players' data on a connected game server is processed on the server owner's instructions (Art. 28). The owner needs their own lawful basis, usually their legitimate interest in running, protecting and moderating their server, and must tell their players.
• Data about members of a Discord server that uses the bot is processed the same way, on the server owner's instructions (Art. 28). The owner needs their own lawful basis, usually their legitimate interest in running, protecting and moderating their community, and should tell their members (for example, in the server's rules).

We do not sell data. We use these service providers only to run DayZ Hub:

• Discord: the platform the bot and Discord logins run on.
• PayPal: subscription and purchase payment processing.
• Stripe: payment processing for Donation Shop purchases, when a server owner uses Stripe.
• Brevo: sends Console account emails (address confirmation, password reset, notices).
• Steam (Valve): Steam login, and public-profile and ban checks when a server owner enables them.
• CFTools: Steam-ID server-presence checks for verification and live server status (only when you enable them).
• Cloudflare: CDN, TLS and DDoS protection (processes connection metadata such as IP addresses).
• EUGameHost: VPS hosting provider in the EU. Both of our servers (dayzhub.net and dayzhub.cloud) run there, so it stores the data on our behalf.
• Plausible Analytics: privacy-first, cookieless website analytics (aggregate page-visit counts only, no personal data or cross-site tracking). You can switch it off at any time under Cookie settings.
• Twitch, YouTube and Steam: read-only public data for go-live alerts and Workshop update checks (only the public usernames and IDs you configure).
• Trustpilot: only if you choose to submit a review for the review promo.

Data also goes where a customer sends it: to the Discord channels a server owner connects with webhooks, and to the other owners using a ban list the owner shares.

Some providers (for example Discord, PayPal, Cloudflare and Valve) are based outside the EEA. Where personal data is transferred internationally, it is protected by appropriate safeguards such as those providers' Standard Contractual Clauses.

On dayzhub.cloud we count page views and clicks on our sign-up and sign-in buttons to learn which pages are useful. We do this on our own server, without cookies, without third-party services and without storing IP addresses or user agents. For each day we only keep totals: the page, the language, a coarse referrer category (for example search, social, Discord or the name of another website), the country (two letters, from Cloudflare) and whether the device is mobile or desktop. These totals cannot be linked to you or to a returning visit, and are deleted after 400 days. We do not count visitors who send Do Not Track or Global Privacy Control, or who are signed in. You can ask questions at [email protected].

• Data is held in a database with regular encrypted backups. Sensitive secrets (CFTools credentials, RCON passwords, the private links for LBmaster and TB webhooks) are encrypted at rest. Your Discord login tokens are kept encrypted in your session only while you are signed in, to re-check which servers you may manage; passwords, API keys and other tokens are stored only as hashes.
• All traffic is served over HTTPS. You can only see the Discord servers you manage or were invited to through Team Access, and the game servers you own or were invited to.

• Bot: feature data is kept while the bot is in your server, except ticket transcripts and closed ticket records, which have their own limits (see section 4). When the bot leaves (you remove it or a subscription lapses), your configuration and feature data are kept for about 3 days, so you can re-add or re-subscribe without losing settings, then permanently deleted. This also applies if you remove the bot while a paid period is still running; the subscription for that server is then cancelled.
• Console: game-server logs and player reports are kept for at most 90 days (7, 30, 60 or 90 days depending on the plan) and player routes for the plan's history period. Player records (names, playtime, statistics, notes) stay while the server is connected and are deleted with it. Bans stay until they expire or are removed. Console accounts that are never confirmed are deleted automatically.
• Mods store: licences stay while you own the mod. A server you moved or removed disappears from your list after 48 hours, and its record (IP, port, dates) stays in the licence history for abuse checks. Licence-check logs (server IP and port, mod, time, result) are kept 90 days and then deleted automatically. The server record of the licence service (IP, port, the server name the mod announces, the mod versions, the result of the last check, and when the server was first and last seen) is deleted automatically when the server has not been seen for 12 months, unless it is still a server you have listed in My mods; we also delete it earlier on request. Team members stay until the buyer removes them. Acceptances of the Mod Licence Terms are kept as proof of the agreement.
• You may request immediate deletion of your data at any time; we act on it within 30 days.
• Payment records are kept for as long as needed for accounting, refunds and disputes.

If you are in the EU/EEA you have the right to access, correct, export, restrict, object to, or erase your personal data. Email [email protected] or use the support Discord.

Players: for data a game server recorded about you, contact that server's owner first, since they decide about it. If you cannot reach them, write to us: we will pass your request on and help the owner answer it.

Members of a Discord server that uses the bot: for data the bot processed about you in that server, contact the server's staff first, since its owner decides which features are on. You can also write to us at [email protected]: we will help the owner answer your request or delete the data.

You also have the right to lodge a complaint with your local data-protection authority; in the Netherlands, the Autoriteit Persoonsgegevens.

DayZ Hub is not directed at anyone below the minimum age required to use Discord in their country (at least 13). Please do not use the Service if you are under that age.

We may update this policy. The "last updated" date will change and material changes will be announced in the support Discord.