Seer privacy policy
DRAFT FOR LEGAL REVIEW - NOT IN FORCE. Prepared from the system as built (
backend/,deploy/). Every[PLACEHOLDER]must be filled in and the whole text reviewed by a lawyer qualified in EU data-protection law before publication.
Version: [VERSION, e.g. 2026-11-01] - Effective: [DATE]
This policy explains what personal data Seer collects when you use the Seer launcher, the Seer Client game, the website seerclient.com and the Seer API, why, for how long, who else sees it, and what your rights are. We wrote it in plain language; if anything is unclear, ask us (section 12).
1. Who is responsible
The controller is [CONTROLLER LEGAL NAME], [ADDRESS], [COUNTRY]. Contact for privacy questions: support@seerclient.com. [If appointed: Data protection officer: [NAME / CONTACT].] [If the controller is established outside the EU: EU representative: [NAME / ADDRESS].]
Seer is an independent project. It is not affiliated with or endorsed by Mojang Studios or Microsoft. "Minecraft" is a trademark of Mojang Synergies AB.
2. The short version
- We store your email, a hashed password, your display name, whether you are over 16, the Minecraft accounts you link (UUID and name), your settings if you use sync, your friends list, your cosmetics and your consent choices.
- We do not store your Microsoft or Minecraft password or login tokens - they stay on your computer. We do not store your birth date or country, and we do not store IP addresses in our database.
- We do not sell your data. Ads in the launcher are only personalised if you agree and are 16 or older.
- You can download all your data, correct it, and delete your account yourself in the launcher or on the website.
3. What we collect and why
| Data | When | Why (purpose) | Legal basis (GDPR) |
|---|---|---|---|
| Email address | registration | sign-in, account recovery, service messages (verification, password reset, security notices) | contract, Art. 6(1)(b) |
| Password | registration, password change | sign-in. We store only an Argon2id hash; we cannot see your password | contract, Art. 6(1)(b) |
| A new email address you asked to change to | email change | sending the confirmation link; replaces the old address once confirmed (unconfirmed: discarded after 48 hours) | contract, Art. 6(1)(b) |
| Display name | registration (you can change it) | identifies you to friends | contract, Art. 6(1)(b) |
| Birth year and country | registration, age re-confirmation | checking the minimum age (section 9). Used once and not stored. We keep only a yes/no "over 16" flag | legal obligation / contract, Art. 6(1)(c), 6(1)(b), Art. 8 |
| "Over 16" flag | derived at registration | age-appropriate features (no personalised ads under 16) | legal obligation, Art. 6(1)(c) |
| Sessions: a hashed token, when it was created and last used, when it expires, and a coarse description such as "Firefox on Windows" | every sign-in | keeping you signed in; letting you see and end your sessions | contract, Art. 6(1)(b); security, Art. 6(1)(f) |
| Two-factor authentication secret and hashed recovery codes | if you enable 2FA | verifying your codes | contract, Art. 6(1)(b) |
| Linked Minecraft accounts: UUID and player name | when you link an account | showing your cosmetics in game, friends, account switching | contract, Art. 6(1)(b) |
| Consent records: purpose, your choice, policy version, time | when you accept the terms or change a consent | proving and respecting your choices | legal obligation, Art. 6(1)(c), Art. 7(1) |
| Friends, friend requests, blocked users | when you use friends | the friends feature | contract, Art. 6(1)(b) |
| Online status and, only if you switch it on, the server address you play on | while the launcher/game is connected | showing friends whether you are online / where to join you | contract, Art. 6(1)(b) |
| A server address you choose to send in a game invite | when you invite a friend | delivering the invite to that friend; passed on, not stored | contract, Art. 6(1)(b) |
| Synced settings (game options, profiles, mod settings) | if you use settings sync | restoring your settings on another PC | contract, Art. 6(1)(b) |
| Cosmetics you own and have equipped | when you get / equip cosmetics | showing your cosmetics to you and to other players | contract, Art. 6(1)(b) |
| Security events (e.g. "signed in", "password changed", "failed sign-in"), with time and your account id, no other personal data | when they happen | detecting and investigating account attacks | legitimate interest in security, Art. 6(1)(f) |
| IP address, time, requested address, status code (web server access log) | every request to our servers | security, abuse prevention, troubleshooting | legitimate interest in security, Art. 6(1)(f) |
| Temporary counters derived from your IP address or email (keyed hash, never the address itself) | sign-in and other protected actions | rate limiting against password guessing and spam | legitimate interest in security, Art. 6(1)(f) |
| Personalised advertising | only with your consent | showing ads based on your interests | consent, Art. 6(1)(a) |
| Analytics | only with your consent | understanding how Seer is used | consent, Art. 6(1)(a) |
| Marketing emails | only with your consent | news about Seer | consent, Art. 6(1)(a) |
Where we rely on legitimate interest (security), our interest is keeping accounts and the service safe; we limit it to what is needed and keep it briefly (section 6). You can object (section 8).
What is visible to others. Friends see your display name, your online status and - only if you enable it - your server. When you equip a cosmetic, other players (and anyone who asks our public cosmetics service for your Minecraft UUID) can see which cosmetic you have equipped. They cannot see your email or anything else.
4. Your Minecraft account
The Seer launcher signs you in to Microsoft/Minecraft on your computer. Your Microsoft and Minecraft credentials and tokens are stored in your operating system's secure storage and are never sent to us.
To link a Minecraft account to your Seer account, the launcher proves to us that it controls the account using the same handshake Minecraft servers use: our server sends Minecraft's session service the player name and a one-time code, and the service confirms that this player just joined with that code. We receive and store only the player's UUID and name.
5. Who receives your data
We use these service providers (processors) under contracts as required by Art. 28 GDPR. They may only use your data to provide their service to us. Current list: see [LINK TO PROCESSORS LIST / legal/processors.md].
| Recipient | What | Where |
|---|---|---|
| Hosting provider [NAME] | everything we store (servers, database, backups) | [EU COUNTRY] |
| Object storage / CDN provider [NAME] | your IP address when you download game files, mods or cosmetics | [EU / regions] |
| Email provider [NAME] | your email address and the content of service emails | [EU COUNTRY] |
| Backup storage [NAME] | encrypted database backups (we hold the key) | [EU COUNTRY] |
| Ad network [NAME], only if ads are enabled | see the cookie and ads policy | [REGIONS] |
Independent third parties:
- Mojang/Microsoft (Minecraft session service) receives the Minecraft player name and a one-time code when you link an account (section 4). Microsoft is in the USA; transfers rely on [the EU-US Data Privacy Framework / SCCs - COUNSEL TO CONFIRM]. Your own launcher also talks to Microsoft directly to sign you in and download game files; that is governed by Microsoft's privacy statement.
- [If enabled: Have I Been Pwned / Cloudflare - when you choose a password we send the first 5 characters of its SHA-1 hash to check it against known breaches. This cannot identify you or your password.]
- Authorities, if we are legally required to disclose data.
We do not sell personal data and do not share it for third parties' own marketing.
6. How long we keep data
| Data | Kept for |
|---|---|
| Accounts never verified | deleted 7 days after registration |
| Your account and everything linked to it | until you delete it; after a deletion request, 7 days (so you can change your mind), then erased |
| Sessions | until you sign out, or 30 days without use |
| Email verification / password reset links | 48 hours / 1 hour, single use |
| Pending two-factor setup | 1 day |
| Unanswered friend requests | 90 days |
| Security events | 90 days |
| Online status | about 90 seconds after you disconnect |
| Rate-limit counters, cosmetics cache | minutes up to 2 hours |
| Web server access logs (IP addresses) | 7 days |
| Encrypted backups | 30 days. Data you deleted disappears from backups within 30 days after it is erased from the live system |
Full schedule: [legal/data-retention-schedule.md].
7. Security
Passwords are hashed with Argon2id; session and email tokens are stored only as hashes; all connections use TLS; servers are in the EU, firewalled and updated automatically; backups are encrypted before they leave the server; our application logs contain no personal data. If a breach affects you we will tell you as the law requires.
8. Your rights
You can, at any time and free of charge:
- Access and portability (Art. 15, 20): download all your data as a JSON file - Settings > Privacy > "Download my data" (launcher or website).
- Rectification (Art. 16): change your email, display name and password in your account settings.
- Erasure (Art. 17): Settings > Privacy > "Delete my account". You are signed out everywhere immediately; after 7 days all data is erased.
- Withdraw consent (Art. 7(3)): Settings > Privacy - as easy as giving it. Withdrawal does not affect processing before it.
- Object (Art. 21) to processing based on legitimate interest, and restriction (Art. 18): write to support@seerclient.com.
- Complain to a supervisory authority, in particular in your country of residence or [LEAD AUTHORITY OF THE CONTROLLER'S COUNTRY].
We answer requests within one month (Art. 12(3)). We may ask you to confirm the request from your account's email address.
We do not make decisions based solely on automated processing that have legal or similarly significant effects on you (Art. 22).
9. Children
You must be at least 13 to create an account, or older where the law of your country sets a higher age of digital consent (up to 16). We ask for your birth year and country only to check this and do not store them. Accounts not confirmed as 16 or older never receive personalised ads. If you believe a child has created an account without permission, contact support@seerclient.com.
10. Cookies and ads
See the [cookie and ads policy]. In short: the website uses only cookies that are strictly necessary to sign you in and protect against forged requests; no tracking before you consent.
11. Changes
We will announce material changes in the launcher and on the website before they take effect. Where a change requires your consent, we will ask again. Each consent you give is recorded with the policy version in force.
12. Contact
[CONTROLLER LEGAL NAME], [ADDRESS] - support@seerclient.com