Privacy Notice

Version: 2026-10-16 · In force from: publication date

In short: we keep only what the game needs; we do not sell data, show ads or use trackers; what is in your campaigns is seen only by their members, and the administrator has no way to open it in the app.

1. Who is responsible for your data

The Metagame.party service (the site metagame.party and the app on it, the “Service”) is run by a private person, Andrei Brazhnikov (“we”, the “operator”). We are the controller under the EU General Data Protection Regulation (GDPR).

Contact for anything about your data: [email protected]; postal address for correspondence: to be added.

While the Service is in beta, section 13 also applies.

2. What we process

Data	Source	Why
Username, display name, password — as a hash only (Argon2id), interface language, theme and density	You, at sign-up and in the profile	Signing in and interface settings
E-mail (if given), whether and when it was confirmed	You	Confirming the address, password reset, essential notices about the Service
Google or Discord account ID, the e-mail and name of that account, whether the e-mail is verified	Google / Discord — only if you choose to sign in with them	Signing in with that service; the name becomes the display name of a new account
Version of the terms accepted and when	You, at sign-up or in the acceptance dialog	A record of the terms you use the Service under
The invite code an account was created with and when; the account’s set of limits (tier)	A code from the administrator	Sign-up by invitation: who signed up with which code; storage limits
Campaign content: campaigns, members and their roles, characters, NPCs, monsters and homebrew, encounters, vault pages, notes, the feed and dice rolls, uploaded images	You and the other members of your campaigns	This is your game — what the Service exists for
Security log: sign-ins, failed attempts, password and e-mail changes, linking of sign-in methods, acceptance of terms, administrator actions — with IP address and time	Automatic	Protection against password guessing, account takeover and abuse
Server technical logs: time, address and result of requests, request and account id, errors	Automatic	Running and debugging the Service
Service figures: requests, errors, sign-ins and connections per minute — not tied to people	Automatic	Watching the Service, alerts about failures
Moderation log: what the administrator opened or removed, when and why	Automatic	Accountability when handling notices (DSA)

We do not receive your passwords, messages, friends or contacts, avatars or any other data from Google or Discord beyond the above. We do not collect special categories of data (health, beliefs, etc.) and ask you not to put them in campaigns.

Contract (Art. 6(1)(b)) — the account, signing in, storing and showing your campaigns, letters to confirm the address and reset the password, limits.
Legitimate interests (Art. 6(1)(f)) — the security log and technical logs, backups, handling complaints and abuse, protecting the Service and its users. Our interest is a working and safe Service; you may object to this processing (section 9).
Legal obligation (Art. 6(1)(c)) — answering lawful requests of authorities and handling notices of illegal content under the EU Digital Services Act (DSA).

There is no advertising, no profiling and no automated decision with legal effects for you.

4. Who sees your data

Members of your campaigns — only what the campaign’s rules give them: for example, players do not see the game master’s notes and hidden materials. The game master sees what members put into the campaign.
Other users see your display name where you meet them (campaign members).
The administrator of the Service — see section 5.
Processors that help run the Service and act only on our instructions:
- a hosting provider — the server, database, files and backups are in the European Union;
- an e-mail delivery service — only the recipient’s address and the letter (address confirmation, password reset);
- Google (Gmail) — the mailbox [email protected]: the letters you write to us and our answers.
Google and Discord — only if you choose to sign in with them; their own privacy policies also apply to that exchange.
Authorities — only on a lawful request.

We do not sell data or share it for advertising or marketing. There are no analytics or advertising trackers.

5. Administrator access to content

Account data (username, display name, e-mail, sign-in dates, number of campaigns, limits) is visible in the admin console — it is needed for support, invitations and protection against abuse. Blocking, deleting and changing the limits of an account are written to the security log.
Campaign content and uploaded files (images, campaign pages, homebrew): the administrator can find them by author, campaign or link and then sees only a description — kind, title, size, date. The content itself can be opened only for a specific reason, which must be stated: a notice of illegal content or a rights holder’s complaint, your support request, a request of an authority. Each view is recorded with its reason in the moderation log and in the security log.
The database and the files on the server are accessed directly only in a security incident or a failure that cannot be fixed otherwise; such a case is recorded with its date and reason too.
The administrator never edits your content; it can be removed only on a substantiated notice or by law (Terms of Service, section 8). A removal is recorded the same way, and its author gets a letter with the reason and how to object.

6. Transfers outside the EEA

The server, the database and the backups are in the EU. If a processor (for example, the e-mail delivery service) processes data outside the European Economic Area, we choose one covered by GDPR safeguards: an adequacy decision of the European Commission or standard contractual clauses. Our mailbox is with Google, a US company certified under the EU–US Data Privacy Framework. Signing in with Google or Discord also involves US companies; you share data with them yourself when you choose to sign in with them.

7. How long we keep data

Data	Period
Account and campaign content	While the account exists; after deletion, see below
Security log	90 days
Links in letters (confirmation, password reset)	Until the link expires, plus 1 day
Sign-in session (cookie)	Up to 30 days or until you sign out
Server technical logs	14 days
Service figures	30 days
Moderation log	1 year
Backups	Up to 14 days (the last 14 daily backups are kept)

Deleting your account. When you ask for your account to be deleted, we delete it. What goes: the account and its sign-in methods and sessions, your limits, your character library, your homebrew, your personal images, and every campaign you run as game master with all its contents (its players get their characters in their libraries). What stays, de-identified, so as not to break other people’s game: your characters in other game masters’ campaigns stay there with no player, your feed messages stay without an author’s name, and images you uploaded into someone else’s campaign stay in that campaign. The security log keeps its entries until its 90 days pass, and the data leaves the backups when they expire (up to 14 days).

8. Cookies and browser storage

One technical cookie (httpOnly) keeps you signed in for up to 30 days. Signing in is impossible without it, so no consent is needed.
Browser storage (localStorage / sessionStorage) keeps your settings on this device: language, theme, density, layout of sections and, while signing in with Discord, a one-time check value.
Signing in with Google loads Google’s button script (only on the sign-in page, and only when Google sign-in is on).

There are no advertising or analytics cookies.

9. Your rights

Under the GDPR you may:

get confirmation and a copy of the personal data about you — your account data and your entries in the security log. What you create in the game you can export yourself: a character as a file, a campaign (if you are its game master) as an archive;
rectify inaccurate data (most of it yourself, in the profile);
erase your account and data;
restrict processing;
receive your data in a portable format — characters and campaigns you export yourself (see above); your account data we send on request;
object to processing based on legitimate interests.

Write to [email protected] from the address in your account, or give your username — we need to make sure the request comes from the account’s owner. We answer within one month.

You may also complain to a data protection supervisory authority — in the EU country where you live or work, or where you believe your rights were infringed.

10. Age

The Service is for people 16 and older; by accepting the Terms of Service you confirm that you are. If we learn that an account belongs to someone under 16, we may block or delete it.

11. Security

Connections are encrypted (HTTPS), passwords are stored only as Argon2id hashes, the session cookie cannot be read by page scripts, attempts to guess passwords and codes are rate-limited, only the administrator has access to the server, and data is backed up daily. No system is perfectly secure: if a breach is likely to affect your rights, we tell you and the supervisory authority, as the GDPR requires.

12. Changes to this notice

The current version and date are always at the top. We announce significant changes in advance, at least 14 days before they take effect, on the site and in the app; if your account has an e-mail, we may also write to it. At your first sign-in after the changes take effect you see the new version and confirm it.

13. During the beta

While the Service is in a closed beta (Terms of Service, section 14):

sign-up is by invitation only, so we keep which invite code an account was created with (section 2);
account deletion is done on request to [email protected]; a button in the profile comes later (section 7);
if moving to a new version requires wiping beta data, we announce it in advance and, where possible, let game masters export their campaigns first.

When the beta ends, this section is removed and you confirm the new version of the notice at your next sign-in.