Easter Co.Legal · Easter Co. SMP
Privacy Policy
This policy explains what Easter LTD does with personal data when you visit launcher.easter.company, install or use the Easter Company launcher, hold an Easter Company account, or play on the Easter Co. Survival Multiplayer Server (Easter Co. SMP).
1. Who we are
Easter LTD ("Easter LTD", "we", "us") is the organisation responsible for the personal data described here. "Easter Company" and "Easter Co. SMP" are trading names we use for this project. We run a small, family-operated public Minecraft server along with the website, the launcher and the account service that support it.
For the purposes of the UK GDPR and the Data Protection Act 2018, Easter LTD is the data controller for that data. Our contact point for everything in this policy is legal@easter.company.
This policy covers our website, our launcher, Easter Company accounts and the Easter Co. SMP server. It does not cover Microsoft, Mojang, GitHub, Modrinth, Google, Valve/Steam or Discord, which each act as separate controllers of the data they hold. Their own privacy policies apply to your use of their services.
2. The short version
- You can read this website without an account and without being tracked. We run no advertising, no analytics and no third-party trackers, and we set no cookies of our own.
- An Easter Company account is needed for the launcher and the server. It holds a username and a password, plus the identities you sign in with and the email address a provider has verified for you.
- Passwords are never stored in a form we can read back, session tokens are stored only as hashes, and a Microsoft sign-in token kept on our side is sealed with AES-256-GCM encryption.
- Playing on the server means we record the things any server operator records to run the game and keep it fair: your Minecraft identity, connection details, chat and commands, gameplay events, and moderation decisions such as bans.
- We do not sell your data, we do not share it for advertising, and we never publish player locations or player records. The public map is a daily snapshot of ships, patrols, villagers and mobs only.
- You can ask us for a copy of your data, ask us to correct it, or ask us to delete your account and the personal data attached to it. Email legal@easter.company.
3. What we collect
3.1 If you only browse the website
Nothing that identifies you reaches us. The site is served as static files by GitHub Pages, so GitHub receives your request and may log your IP address for security and abuse prevention under GitHub's privacy statement. We do not operate the web server and we do not receive those logs. We have no visitor analytics and no advertising code on the site.
3.2 If you create an Easter Company account
An account is created by signing in with a provider and then choosing a Company username and password. We store:
- Your Company username — your public sign-in handle, 3 to 20 characters, unique, and unchangeable once claimed.
- Your password — stored only as a salted scrypt verifier (n=32768, r=8, p=3). We cannot read your password and we will never ask you for it in a message.
- The provider identities you link — the server-verified account identifier from Microsoft/Xbox, Google, Steam and/or Discord, with the provider name and the date. A provider identity belongs to exactly one Company account, and each account can hold at most one link per provider.
- Verified email addresses — addresses a provider has verified for you, in lower-case, each linked to only one account. Only the one you select is used as a sign-in key.
- Your profile — an optional display name and an optional profile picture you upload (PNG only, at most 256×256 pixels and 256 KiB, with metadata removed), and the display name or picture imported once from your provider if one was available.
- Account timestamps and roles — when the account was created and last changed, the method used to authenticate, and internal role labels such as member.
- Minecraft identity — the Minecraft UUID and player name that your account is associated with. Minecraft Java Edition access is checked against Microsoft's own licence service, and access is granted or denied from that answer.
3.3 Security and anti-abuse records
- Sessions — a token for each signed-in session, stored only as a hash, with the client name, creation time, expiry and last-use time. A session can be revoked at any time, which makes the stored hash useless.
- Sign-in attempt counters — a short-lived, rate-limiting record keyed by a hash of your network address and the sign-in method, used to slow down password guessing and other abuse. It holds an attempt count and an expiry, not a history of what you did.
- Sign-in flow state — while a provider sign-in is in progress, a hash of a single-use state value and verifier with a ten-minute expiry. It is deleted or expires when the flow ends.
- Linkage records used for moderation — which Company account, Microsoft identity and Minecraft UUID are connected. We keep this so a ban cannot be evaded by switching between them, and so we can help you if you lose access.
3.4 Your Microsoft session
Signing in with Microsoft gives the launcher a Minecraft session. So that you do not have to approve the same Microsoft account again on every machine, or after every restart, the account service keeps one Microsoft refresh token for your account, encrypted with AES-256-GCM using a key held outside the database and bound to your account identifier. A later Microsoft sign-in replaces it with the newer token. It is erased when Microsoft itself refuses it, or when you ask us to erase it or to delete your account. To ask for that, use the route in Your rights below. We never see or store your Microsoft password.
Your launcher's own copy of the session lives in your operating system's encrypted store. With no stored session, Play asks you to sign in with Microsoft again on each machine you use.
3.5 If you play on the server
Operating a Minecraft server means recording what the game and its moderation require:
- your Minecraft player name and UUID, and the connection address and timestamps of each session;
- in-game chat messages, commands and gameplay events (blocks changed, items moved, deaths, trades, combat, region and patrol events) as recorded by the server and its server-side recording of play sessions;
- moderation records — warnings, mutes, kicks, temporary and permanent bans, the reason, who issued it and when;
- the world itself, including your builds, containers and player data, and the backups we take of it.
We do not publish any of this. The public map and public data files contain ships, patrols, villagers and mobs with hashed identifiers and observation times, and are filtered to exclude player positions and player records.
3.6 If you contact us
We keep the message you send us, your email address and our reply, for as long as we need them to deal with the matter and to keep a record of it.
4. What stays on your own device
The website and launcher keep the following data on your device:
- Launcher settings — install location, memory, launch behaviour, graphics choices, and your saved account sessions. Account sessions are stored only in your operating system's encrypted store (Electron
safeStorage); if the operating system cannot encrypt them, the launcher refuses to save them rather than writing them in plain text. - Website account session — your session token and expiry are kept in this tab's session storage so sign-in survives navigation and reloads. This is browser storage, not the launcher's operating-system encryption. Signing out removes the stored session. Account profiles are read from the account service and are not saved in browser storage. If session storage is unavailable, navigation may require signing in again.
- Website preferences — the map's layer switches and the launcher progress bar's minimised state, kept in your browser's local storage.
- Your map drawings — anything you draw on the map is stored in your browser's IndexedDB on your own device. It is never uploaded, never exported and never published.
You can clear all of it by clearing the site data for this site in your browser, or by removing the launcher's own data folder.
6. Why we use it, and on what legal basis
| What we use | Why | Legal basis |
|---|---|---|
| Account, provider links, verified email, Minecraft identity | To create and secure your account, sign you in, and decide whether you may launch the game and join the server | Performance of our contract with you — Art. 6(1)(b) |
| Server play records and world data | To run the game, keep the world working, investigate griefing and cheating, and enforce our rules | Contract — Art. 6(1)(b); legitimate interests in running a fair, secure server — Art. 6(1)(f) |
| Security records: sessions, rate limits, flow state, ban linkage | To protect accounts, stop password guessing, prevent ban evasion and keep the service available | Legitimate interests — Art. 6(1)(f) |
| Optional display name and uploaded picture | To let you personalise how other players see you | Consent — Art. 6(1)(a); withdraw it by removing the picture or name |
| Messages you send us | To answer you and keep a record of support and moderation decisions | Legitimate interests — Art. 6(1)(f) |
| Records we are legally required to keep | To comply with the law and lawful requests | Legal obligation — Art. 6(1)(c) |
Where we rely on legitimate interests, we have considered that the processing is limited to what running a public game service needs, that it is what players reasonably expect, and that your rights are respected through the controls in section 12. You may object to that processing at any time.
7. Signing in with Microsoft, Google, Steam or Discord
You can sign in with Microsoft/Xbox, Google, Steam or Discord. The identity check happens on our server, not in your launcher.
- Microsoft/Xbox — we verify your identity and, where Xbox profile access is available, import your Xbox gamertag and gamer picture. Minecraft Java Edition requires a linked Microsoft account with verified Java access; signing in with Google, Steam or Discord alone does not grant Minecraft access.
- Google — we request only
openid,profileandemail. See section 7. - Discord — we request only
identifyandemail. - Steam — we verify your Steam identity through Steam's OpenID endpoint. Public profile metadata is fetched only if it is available; we do not receive your Steam password.
For Google and Discord we use the confidential authorisation-code flow, and the code is exchanged on our server against our own registered client and exact callback address. We never store a provider's access token or refresh token — only the verified identity and profile data the provider returns. Your provider password is never seen by us.
Provider sign-in happens in your normal browser. The website opens Microsoft's own sign-in page for a Microsoft account, and a separate sign-in window for configured Google, Steam and Discord providers. Microsoft sign-in is also available in the launcher. No Company password or session token is ever placed in a provider URL.
8. Google user data
If you choose Sign in with Google, we ask Google only for your basic account information:
- openid — the stable identifier that tells us which Google account this is;
- profile — your name and profile picture, used for your imported display name and picture;
- email — your email address and whether Google has verified it, so it can be used as a sign-in key and for account recovery.
We do not request, access or store Gmail, Google Drive, Calendar, Contacts, Photos, location or any other Google service data, and we request no Google scopes beyond those listed above.
Limited Use. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. In particular, we do not use Google user data for advertising, do not sell it, do not use it to build profiles for any purpose other than providing our service, and do not transfer it to anyone except as needed to provide or improve the service, to comply with applicable law, or as part of a merger or acquisition with notice to you. No human reads your Google user data except where you have asked us to, where it is necessary for security or to fix a problem, or where the law requires it.
You can remove Google sign-in at any time by asking us to unlink it. Where Google is your only sign-in method, ask us to delete the account instead (section 12).
10. Where your data is processed
Our account service and its database run on Amazon Web Services in the United States (us-east-2, Ohio). GitHub, Microsoft, Mojang, Modrinth, Google, Valve and Discord may process data in other countries under their own safeguards.
Where personal data leaves the UK, we rely on the safeguards those providers publish for international transfers, including the UK International Data Transfer Addendum and standard contractual clauses. You can ask us for more detail about the safeguard that applies to a particular transfer.
11. How long we keep it
| Data | Kept for |
|---|---|
| Your account, provider links, verified email and profile | While your account exists, then deleted when you ask us to delete it |
| Signed-in sessions | Until they expire, are revoked, or you sign out — renewed sessions last at most 30 days |
| Sign-in flow state and nonces | 10 minutes, then expired |
| Sign-in rate-limit counters | A short rolling window, normally well under a day |
| Sealed Microsoft session | Until Microsoft refuses it, or until you ask us to erase it or to delete your account |
| Server logs — chat, commands and connection records | Normally no more than 90 days, kept longer only for an active investigation |
| Moderation and ban records | While the restriction is in force and up to 12 months after it ends, so a ban cannot simply be evaded |
| World data and world backups | For as long as the server runs, as a rolling set of backups |
| Messages you send us | Up to 24 months after the matter is closed |
When a retention period ends we delete the data or make it anonymous. Deletion is permanent: an in-game world edit, a ban record or chat log that we have deleted cannot be recovered.
12. Your rights
Under the UK GDPR you have the right to:
- be informed — this policy;
- access — a copy of the personal data we hold about you, and information about what we do with it;
- rectification — correction of data that is wrong or incomplete;
- erasure — deletion of your account and the personal data attached to it, subject to the retention periods above for anything we must keep;
- restriction and objection — asking us to limit or stop processing based on legitimate interests;
- portability — a machine-readable copy of the data you gave us, where that applies;
- withdraw consent — at any time, where we relied on consent, such as an uploaded profile picture;
- complain — to a supervisory authority. In the UK that is the Information Commissioner's Office.
To use any of these rights, email legal@easter.company from the address connected to your account, or tell us your Company username and the provider you sign in with, so we can be sure who is asking. We answer within one month, and we may extend that by up to two further months for a complicated request, in which case we will tell you why. Asking us to act on your rights is free.
We will not treat you differently for exercising a right.
13. How we protect it
- Passwords are stored only as salted scrypt verifiers; session tokens only as hashes.
- The Microsoft session we hold is sealed with AES-256-GCM, with the account identifier bound as encryption context and the key held outside the database. Revocation erases it.
- Provider sign-in uses single-use state with a ten-minute expiry, verified server-side, so a replayed or forged callback is refused.
- Traffic between the launcher, the website and our API uses HTTPS. The launcher's own web content is isolated: no Node access, a strict content security policy, and no privileged content loaded from a remote address.
- Our database access is split by role, and each service can reach only the tables it needs. Secrets are held in a managed secret store and never in the launcher, the website or this repository's files.
- Our storage is private rather than public, and the one long-lived secret we hold — your Microsoft refresh token — is encrypted with AES-256-GCM before it is stored.
No system is perfectly secure, and we will not pretend otherwise. If a breach ever affects your personal data, we will tell you and the ICO where the law requires it, and we will tell you what we know, what we have done, and what you should do.
If you think you have found a security problem, please email support@easter.company before doing anything else, and do not try to access another player's data to prove it.
We do not ask for, and do not want, special category data such as health information, religion, ethnicity, political opinions or biometric data. Please do not put it in your profile, your username or public chat, and do not send it to us by email.
14. Children and age limits
Easter Co. SMP is intended for people aged 13 and over, which matches the minimum age for a Minecraft account. We do not knowingly collect personal data from anyone under 13. If you are under 13, please do not create an account, sign in or play.
If you are under 18, you should have a parent or guardian's agreement before creating an account or using the server.
If you are a parent or guardian and you believe a child under 13 has given us personal data, email legal@easter.company and we will delete the account and its data.
15. Changes to this policy
We may update this policy as the service changes. The "Last updated" date at the top always says which version applies. If a change materially affects what we collect or how we use it, we will announce it on the website and in the launcher before it takes effect, and where the law requires it we will ask for your consent first.
16. How to contact us
Easter LTD — privacy and data protection
Email: contact@easter.company
If you are unhappy with our answer you can complain to the Information Commissioner's Office, or to the supervisory authority in the country where you live or work.