Last updated 05.10.2026
This policy explains what we collect when you use dz.arbat16.com, the Sentinel app and the cloud panel, why we need it, who else sees it and what you can demand from us. It is written to match the code, not a template: every item below is something the service actually stores or sends.
We do not sell personal data and we do not show ads. Google Analytics runs only if you allow it in the cookie banner.
1Who is responsible
The operator is AP SYSTEM32.BIN LLC, registered in the State of New York, United States, address 447 Broadway, 2nd Floor #1565, New York, NY 10013, United States.
For your account, your organization and your visits to the site we are the controller under the GDPR. For data about players on game servers that you connect through Sentinel, you are the controller and we are your processor: we keep and show that data only so the panel features you turned on can work, and only on your instructions.
Contact for any privacy matter: privacy@dz.arbat16.com.
2What we collect
When you simply visit the site
| Data | Why |
|---|---|
| IP address, browser identification string, the page you asked for and the time, in the web server log | Delivering pages and investigating attacks and errors |
| Cookies the site needs to work: session, language, sign-in, your answer in the cookie banner | Listed one by one in the Cookie Policy |
| Pages you view, how you arrived, device and browser type, approximate location derived from your IP address, a random identifier stored in a cookie | Google Analytics, only if you click Accept in the cookie banner. Google signals and ad personalization are turned off |
| The Steam ID or profile link you type into the Steam ID lookup | Sent to Steam to fetch the public profile. The answer is cached for ten minutes and is not linked to you |
| Name, email, Discord name or phone, server name and message from the contact form | Answering you |
| Name, email, optional phone and address, the works and links named, and the signature from a copyright notice | Handling the notice and any dispute about it |
The AR16 Launcher downloads the server list and its own updates from this site. It sends no account data; its requests land in the web server log like any page visit.
When you sign in through Steam
Steam does not give us your password: it confirms your identity and hands over what your profile makes public.
| Data | Why |
|---|---|
| SteamID, nickname, avatar | Identifies your account and shows who you are in the interface |
| Profile link, account creation date, country, visibility, online state | Shown in your profile section and used to tell real accounts from throwaways |
| Real name, if your profile publishes it | Stored only because Steam includes it in the same response. We do not ask for it and do not display it publicly |
| The full raw Steam response | Kept so we can restore your profile without asking Steam again if a field changes meaning later |
Every time you sign in we write a line to the sign-in log: IP address, the country, city, postal code and approximate coordinates of that city derived from the IP address, browser identification string, session token and time. You can see these entries in your profile settings. They exist so you can spot a sign-in that was not yours.
When you use the panel and Sentinel
| Data | Why |
|---|---|
| Organization name, members and their roles, invitations sent by SteamID, who invited whom | Ownership and access control |
| For each connected computer: its name, host name, Windows version, Sentinel version, a machine identifier, online status, processor and memory load, server FPS, player counts and availability | The fleet screen, graphs and alerts |
| Game server settings, mod lists, restart schedules, messages to players, configuration snapshots, and the files you open or change through the panel, which pass through our server on their way to and from your computer and stay in our command log | Managing servers from the browser |
| Lines from the game server’s logs (the console and the RPT, script and admin logs), sent only while someone has that log open; the admin log carries player names and IDs, positions and chat | The live log view |
| The list of your world backups: which world, size, checksum and time. The archives themselves stay on your computer; a cloud copy goes to Cloudflare R2 only if you keep cloud copies in paid cloud storage | Restoring a server |
| Activity log: who did what and when, from which IP address and browser | Answering “who changed this” inside your team |
| Discord webhook address and the messages we post to it | Alerts in your Discord channel, only if you connect one |
| Your public encryption key, your private key locked with your passphrase, and the devices where you unlocked it: device name, browser, IP address, time | Protecting server and RCON passwords. We cannot read the private key or the passwords it protects |
When you use the assistant
Your messages, the assistant’s answers and the data it reads from your servers to answer you (settings, logs, player lists) are stored with the chat, along with token counts and cost. To produce an answer they are sent to Requesty, a routing service for AI models, and through it to the company that hosts the model. Before sending we mask passwords and webhook addresses.
When you pay
Payments go through Stripe. You enter card details on Stripe’s own page and they never reach us. We keep the plan, billing period, amounts, promo code, Stripe customer and subscription identifiers, top-ups of the assistant balance, and the email you gave at checkout, which Stripe passes back to us as your billing contact.
Players on servers that use Sentinel
When a server owner turns on player features, Sentinel sends us data about people who play on that server. For this data the server owner is the controller and we act on their behalf.
| Data | How long we keep it |
|---|---|
| Sessions: SteamID, BattlEye GUID, DayZ ID, nickname, IP address, join and leave time, ping, kill and death counts, and events during the session | 1 day on the Free plan, 30 days on Plus, 90 days on Max |
| Positions on the map and inventory snapshots | 1 day on the Free plan, 30 days on Plus, 90 days on Max |
| Totals per player: first and last visit, number of sessions, time played, kills and deaths, last nickname | Until the server owner asks us to remove them |
| Public Steam profile and Steam ban status | Copied from Steam when someone opens the player, refreshed when the copy is more than a day old, kept until the server owner asks us to delete it |
| Bans with their reasons, and notes the server staff write about a player | Removing them in the panel hides them from the lists but keeps them in the history; they are deleted for good when the server owner asks us |
| Lines of the server’s logs sent for the live log view, which can carry player names and IDs, positions and chat | About 30 minutes while the computer keeps sending them; what the panel or the assistant reads from the computer stays in the command log as long as the account exists |
The plan here is the server owner’s plan. If the owner moves to a plan that keeps less, for example from a paid plan to Free, history the new plan does not keep is held for 30 days and then deleted. An alert about a player on your watch list carries the player’s nickname, SteamID and your staff’s note to the recipients you set up: notifications in the panel, Discord, webhooks. The terms of this processing are in the section “Processing of player data” of the Terms of Service.
What we never collect
Steam passwords, card numbers, documents, precise location from your device, your contacts, your camera or microphone. We do not build advertising profiles and we do not sell data.
3Legal grounds
| Purpose | Ground (GDPR Art. 6) |
|---|---|
| Running your account, the panel, Sentinel and the assistant | Performance of a contract, Art. 6(1)(b) |
| Payments and keeping payment records | Performance of a contract and legal obligations under tax and accounting rules, Art. 6(1)(b) and (c) |
| Web server log, sign-in log, activity log, abuse prevention | Legitimate interest, Art. 6(1)(f): a working service that nobody hijacks, and your ability to spot a sign-in that was not yours |
| Answering the contact form | Steps you asked for, Art. 6(1)(b), or legitimate interest, depending on what you ask |
| Handling copyright notices | Legal obligation and legitimate interest in removing infringing content, Art. 6(1)(c) and (f) |
| Google Analytics | Your consent, Art. 6(1)(a). You can withdraw it at any time with “Cookie settings” at the bottom of every page |
| Data about players on your servers | We process it on the server owner’s behalf, Art. 28. The owner needs their own ground, usually a legitimate interest in running the server and enforcing its rules |
If you disagree with processing based on legitimate interest, you can object under Art. 21 and we will either stop or explain in writing why our grounds override. We make no decisions about you by automated means that have legal or similarly significant effects.
4Who else sees your data
We do not sell data to anybody. Each of these services receives a specific slice for a specific job.
| Service | What it receives | Why |
|---|---|---|
| Fornex Hosting (Spain), data center in Germany | Everything stored in our database | Hosts our server |
| Cloudflare (USA) | Connection data for every visit; cloud copies of world backups and uploaded mods | Delivers the site, filters attacks, stores files in R2 |
| Steam, Valve Corporation (USA) | SteamIDs | Confirms your sign-in, returns public profiles and ban status, answers the Steam ID lookup |
| ipinfo.io (USA) | Your IP address when you sign in | Turns it into a country and city for the sign-in log |
| Stripe (USA, Ireland) | Your email if we have it, the plan and the amount; the card details you enter on Stripe’s own page | Takes payments |
| Requesty and the company that hosts the AI model | Assistant chats, with passwords and webhook addresses masked | Produces the assistant’s answers |
| Google (USA, Ireland) | The analytics data described above, only after you click Accept | Visit statistics |
| Discord (USA) | Alert messages for your channel, only if you connect a webhook | Delivers alerts |
Some of these transfers leave the European Economic Area. Where the provider takes part in the EU-US Data Privacy Framework we rely on the European Commission’s adequacy decision for it, otherwise on the Standard Contractual Clauses.
5Cookies and analytics
Cookies the site needs to work are always on. Google Analytics turns on only after you click Accept in the cookie banner. If you later choose Necessary only in “Cookie settings” at the bottom of any page, analytics stops and we delete its cookies from your browser.
The full list, with names and lifetimes, is in the Cookie Policy.
6If you are in Russia
We say this plainly rather than hiding it in a clause. The operator is registered outside Russia and the database is in Germany. Russian law (Federal Law 152-FZ, art. 18(5), as amended from 1 July 2025) requires personal data of Russian citizens to be processed in databases located in Russia, and we do not meet that requirement.
What this means for you: if that matters to you, do not create an account and do not accept analytics cookies. Browsing the site, the server list and the wiki requires no account. If you also choose Necessary only in the cookie banner, the only record of your visit is what any website keeps: your IP address in the web server log and at Cloudflare.
7How long we keep it
- Account, organization and panel data: as long as the account exists. Ask us to delete the account and we delete it with everything attached within 30 days, except payment records.
- Sign-in log: as long as the account exists. It is the only record that would show a break-in.
- Activity log: 1 day on the Free plan, 180 days on Plus, 365 days on Max.
- Game server log files and the machine’s own activity record in Sentinel: they stay on your computer, and the panel reads them from there. What the panel reads is kept in the command log (next item). Server log lines (the console and the RPT, script and admin logs) sent to us for the live view are kept about 30 minutes while the computer keeps sending them; the last lines of a computer that stops sending stay until it sends again.
- Command log: the commands the panel and the assistant send to your computers and the answers that come back, including the text of files you open or save through the panel. Kept as long as the account exists.
- Alert samples: processor and memory load, server FPS, player count and availability, one sample a minute for each computer, kept 7 days so that alert rules can look back.
- Player data: as listed in the players table above.
- Assistant chats: deleted 90 days after the last message on the Plus plan and 180 days on Max. The assistant is not sold on Free: after a move to Free, chats are kept 30 days and then deleted.
- Backups: the archives stay on your computer, and your backup schedule decides how many are kept. We keep only their list. Cloud copies, if you keep them, follow the same schedule while the cloud storage is paid for (next item).
- Cloud storage (cloud copies of backups and uploaded mods): while it is paid for. When the plan stops covering the files, for example after a move to a smaller plan, a cancelled storage add-on or the end of a paid plan, they are kept 14 days on the Free and Plus plans and 30 days on Max, counted by the plan that covered them, then what does not fit is deleted, oldest backup copies first. We tell you when this starts, a week before and a day before.
- After a move to a plan that keeps less, for example from a paid plan to Free: history the new plan does not keep is held for 30 days and then deleted.
- Payment records: as long as tax and accounting rules require.
- Contact form messages: until you ask us to delete them.
- Copyright notices: as long as the removed content or a dispute about it may still need them.
- Web server log: about two weeks, then the oldest file is deleted every day.
- Google Analytics: Google keeps the data for the retention period set in our Analytics account, at most 14 months.
- Server list data is not personal data: it describes game servers, not people. DayZ does not publish player names in the server list.
8What you can demand
Write to privacy@dz.arbat16.com, use the contact form on the home page or message us on our Discord server. Many accounts here have no email address on file, so to make sure a request about an account comes from its owner, we may ask you to confirm it from inside your signed-in account (for example, we show a code in your panel and you send it back to us) or through the Steam account you sign in with (for example, by putting a code we give you into your Steam profile name for a few minutes). We answer within 30 days.
- A copy of everything we hold on you, in a machine-readable form (Art. 15, Art. 20)
- Correction of anything wrong (Art. 16). Profile fields come from Steam: fix them there and sign in again
- Deletion of your account and everything attached to it (Art. 17)
- Restriction of processing while a dispute is open (Art. 18)
- Objection to processing based on legitimate interest, including the location lookup at sign-in (Art. 21)
- Withdrawal of consent to analytics at any time, with “Cookie settings” at the bottom of every page (Art. 7(3))
We do not charge for this and we do not require a reason. If we refuse, we say why. You can also complain to a supervisory authority; for EU residents it is the one in your country of residence.
If you play on someone else’s server, its owner decides about your data there. Write to the owner first. If that does not work, write to us and we will pass the request on and help them carry it out.
9How it is protected
Traffic runs over HTTPS with HSTS. Server and RCON passwords are encrypted with a key our server does not have, so we cannot read them. Access to the database is limited to people who need it to run the service.
We will not pretend this is unbreakable. If a breach happens and it is likely to put your rights at risk, we will notify the relevant supervisory authority within 72 hours and tell you directly, saying what happened and what you should do, rather than issuing a statement about how seriously we take security.
10Age
The service is for adults. You must be at least 18 years old to use the service, and only adults may pay for it. We do not knowingly create accounts for, or collect account data from, anyone under 18. If you believe someone under 18 has an account here, write to us and we will remove it.
Data about players on game servers is processed for the server owner, who decides who may play there.
11Changes
If we change what we collect or who we send it to, we update this page and the date at the top. For changes that materially affect you we will also tell you in the interface. We will not quietly widen the scope and rely on you re-reading the page.
Contact
Privacy requests: privacy@dz.arbat16.com
Operator: AP SYSTEM32.BIN LLC, 447 Broadway, 2nd Floor #1565, New York, NY 10013, United States
This is a plain-language document, not legal advice. If your situation is unusual, talk to a lawyer in your country.
