This site runs without ads on purpose — donate to keep it alive
← home

Privacy

Last updated 4 August 2026.

The short version

You can use this whole site without an account, and we do not track you when you do. If you sign in, we store the minimum needed to know who you are and which servers you have proven you own. There are no ads, no third-party analytics, and nothing is sold or shared for marketing.

If you browse without signing in

We set no cookies and run no analytics or tracking scripts. Our host, Railway, keeps ordinary server logs (including IP addresses) as part of operating the service.

The one bit of state is a filter you set on the all-servers page, which your browser keeps in its own session storage so the back link can restore it. It never reaches us.

If you sign in

We receive from your chosen provider, and store:

  • Google — your account identifier, email address, whether that email is verified, your name, and your profile picture URL.
  • Discord — your account identifier, email address, whether that email is verified, your username, and your avatar URL.

We never receive your password, and we never ask for one. We request the narrowest permissions each provider offers for signing in, and nothing that would let us read your mail, your servers, or your contacts.

We use the email address to recognise you across providers and to reach you about your account. We do not send marketing email.

Cookies

One cookie keeps you signed in. It holds a random session identifier and nothing else — no personal data is stored inside it. It is marked HttpOnly (unreadable by scripts), Secure in production, and SameSite=Lax.

It lasts up to 30 days, and expires after 14 days without use. Signing out deletes both the cookie and the session record on our side immediately.

During sign-in a second short-lived cookie holds the one-time values that protect the login handshake. It is deleted the moment you land back on the site, and never lives longer than 10 minutes.

We use no advertising, tracking, or analytics cookies of any kind.

Server data

Player counts and MOTDs come from public status responses, the same thing any player's Minecraft client sees when listing a server. They are properties of the server, not of any person, and we do not record who is playing.

If you claim a server, we store the link between your account and that server, when it happened, and the verification attempts — including the MOTD we read at the time, so we can help you if verification fails.

Text you write as a server owner — display name, description, blurb — is public by design.

Where it lives

Everything is in a single SQLite database file on a persistent disk attached to our application server at Railway. It is not shared with any other application, and we do not run a separate analytics or advertising pipeline.

Who else is involved

  • Railway — hosting and storage.
  • Google and Discord — only if you choose to sign in with them.
  • PayPal— only if you choose to donate. Donations happen on PayPal's site; we never see your payment details.
  • Google Fonts— the site's fonts are served from our own domain, so your browser does not contact Google to render a page.

We do not sell, rent, or trade your data, and we never will.

How long we keep it

Sessions are deleted when they expire, or immediately when you sign out. Account data is kept until you delete your account. Verification attempts are kept while the claim is live and cleared out afterwards.

Player-count history is kept indefinitely — it is the entire point of the site, and it describes servers rather than people.

Your choices

You can delete your account from your dashboard at any time. That removes your account record, your linked provider identities, and every session, and releases any servers you had claimed. Public measurements of those servers remain, because they were never yours to begin with.

You can also ask us for a copy of what we hold about you, or ask us to correct it, by emailing the address below.

Children

This site is not directed at children under 13, and accounts require a Google or Discord account you are old enough to hold. If you believe a child has created an account, email us and we will remove it.

Changes

If this policy changes, the date at the top changes with it. If a change materially affects what we collect or why, we will say so on the site.

Contact

Privacy questions, data requests, or deletion: kaiwojciak@gmail.com.

See also our terms of use.