Privacy Policy

There are no ads on this site, no analytics, and no tracking scripts of any kind. Nothing about you is sold, rented, or handed to a data broker.

What is collected falls into three piles: what your sign-in provider tells us when you sign in, what your browser tells us while you’re here, and what the game servers write down while you play. The last is the big one, and it includes where you were standing. If you buy unban tokens there is a fourth, small pile: Stripe handles the payment and a purchase record lands here — see Who else touches it.

You sign in with an account from another service — Discord or Google today, and possibly another one later. That provider passes over your display name, your email address, your avatar image, and your account ID at that provider. We also store the access and refresh tokens it issues, which are what let the site confirm you are still you.

We never see your password there, and we cannot read your messages there.

A session cookie, so you stay signed in, and a second cookie that remembers which map you were last looking at. See Cookies below for the full list.

Stored alongside that session: your IP address and your browser’s user-agent string. That is the standard record of where a sign-in came from, and it is how a stolen session gets spotted.

If you turn on notifications, we also store the push endpoint your browser hands out, the two keys that let us encrypt messages to it, and that device’s user-agent.

The DayZ server writes an admin log. We read it line by line, and that log is where most of what this site knows comes from:

• your gamertag, and every time you connect and disconnect
• your position on the map, sampled periodically while you are connected — pulled from the server’s own player-list dump and from anything else it logs
• kills, hits, going unconscious, dying, and building
• the emotes you perform — which is how gamertag verification works

Your position data is the most sensitive thing here, and it is handled that way. See Who sees what.

Nothing you say in chat is parsed, stored as data, or published — the log parser has no handling for chat at all. But the server’s raw log is kept as-is, so if the server ever happens to write a chat line into it, that line sits there unread.

• An avatar, if you upload one — the image itself is stored in our database.
• Your gamertag claim.
• Your session location-sharing grants.
• Notifications about you — stored so your inbox can show them.

Public, to anyone, signed in or not: your gamertag, your lives, how long each lasted, how it ended, your kills, your obituaries, and your position on the boards.

Any signed-in, verified player: whether you are currently on a server. The map's online list shows everyone currently connected, the same way DayZ’s own in-game player list already does — nothing here hides that.

Yours alone: your email address, your IP addresses, and your map coordinates. The routes that serve coordinates take no player parameter at all — there is no field in which to name somebody else — and they are marked never to be cached or stored by anything in between.

Whoever you grant it to, and only for one game session: your live location. Off by default, granted to one person at a time, and it ends with the session.

Nobody buys this data. Five parties see some of it because they have to:

• Your sign-in provider (Discord or Google today) — handles your sign-in.
• Nitrado — hosts the game servers that write the logs.
• Your browser’s push service (Apple, Google or Mozilla, depending on your device) — only if you enable notifications, and only to deliver them.
• Stripe — handles payment if you buy unban tokens. Checkout happens on Stripe’s page, not this one: Stripe sees your card details, your email, and whatever else it collects under its own privacy policy; this site never sees your card number. What gets stored here is a purchase record — Stripe’s reference for the checkout, how many tokens, and when — tied to your account.
• OpenRouter, and the model it currently routes to — obituaries are written by an AI model (right now, Anthropic’s Claude), reached through OpenRouter. To write one, we send your full gameplay record for this life and your earlier ones — your gamertag, your killer’s gamertag, map, time survived, cause, weapon, distance, and your record going in. Some of what goes over is detail the site itself never shows anywhere: how low your health got, and how many close calls you had with infected, fire, or other players. We also send the headlines, attributions and opening lines of recently published obituaries as style context, which can include other players’ gamertags. Your account, email and IP address are not sent.

Beyond that: I will hand over data where the law requires it, and I will say so publicly unless I am barred from saying so.

Two cookies, both ours, neither used for tracking: the one that keeps you signed in, and one that remembers which map you were last looking at. No analytics cookies, no advertising cookies, no third-party cookies. There is no consent banner because there is nothing to consent to.

Indefinitely. There is no automatic deletion of anything and no expiry schedule.

That is deliberate for the gameplay record — the premise of One Life is that the record is permanent — and it is simply the truth for everything else. Rather than publish a retention schedule that no actual job enforces, here is the honest version: it stays until you ask for it to go, or until the site shuts down.

Email [email protected] from the address on your account, or give me your gamertag and I will verify it another way.

Deleted: your account, your name and email, the tokens your sign-in provider issued, every session — and with them the stored IP addresses and user-agents — your avatar, your push subscriptions, your preferences, your location shares, your unban token balance and its history, your referral link, and your gamertag link.

Not deleted: your gameplay record, your obituaries, and any ban history recorded against your gamertag. Lives, deaths, kills and positions live in an append-only log that every part of this site is rebuilt from; pulling a gamertag out of it would break the rebuild the whole system depends on. It is also the premise of the product. Bans are keyed to the gamertag, not the account, so they stand on their own the same way. Once your account is gone, that record stands with nothing here tying it to you.

If you ever bought tokens, the payment records at Stripe also survive — financial rules require Stripe to keep them, and deleting your account here does not delete them there. The purchase rows in our own ledger go with everything else.

If one specific obituary is the problem, say so. That is a conversation, not a policy.

One Life is not for anyone under 13, and accounts are not knowingly created for them. If you believe a child under 13 has an account here, email [email protected] and it will be removed.

This policy can change, and the date at the top changes with it. If something material changes about what is collected or who receives it, that gets called out rather than quietly edited in.

[email protected]. One person reads it.