Privacy

No account exists, and every page you get is byte-for-byte the same page everyone else gets. But the site does count its visits, so browsing is not invisible — here is exactly what that means.

The site runs its own copy of Umami, an open-source visit counter, on its own server. Each visit gets a pseudonymous session identifier — a number derived from your IP address, your browser's user-agent string, and a secret value. It is not an account, and it is not nothing either: for one calendar month, it ties together the pages you view and the things you click, along with your device type, browser, operating system, screen size, language, and your country, region, and city. That window is deliberate — it is how the site can tell how many visitors come back, which is the main thing a one-person site needs to learn to get better. The secret value changes at the start of every month, so last month's identifier cannot be connected to this month's — the site can recognize a returning visitor within a month, so long as their network address and browser have not changed, and it cannot follow anyone across months. This data sets no cookie, writes nothing into your browser, and never leaves the site's own server — and it ages out rather than living forever: a monthly cleanup deletes anything older than 400 days, and the counter's own backups rotate away within a further eight weeks.

One honest limit, one honest exception, and one off switch. For past months there is no practical way to look a visitor up in these records: matching rows to a person would take the network address and browser details you used back then — information neither you nor the site is likely to still have — so those rows leave only by aging out on the schedule above. The current month is different: if you write in promptly, while your address and browser are what they were, the site can usually find that month's rows — ask (the “Deleting it” section below covers how to reach the site), and it will try. And if you want the counting to stop entirely, you can: set umami.disabled to 1 in your browser's localStorage — the counter checks for that before doing anything — or use any content blocker. The site works identically either way.

Like any website, the servers in front of this one also keep ordinary short-lived access logs — the requested address, the time, your IP address, your browser's user-agent string — which is how a site gets debugged and how abuse gets blocked. They are not shared. The visit counter above is the one record that outlives them.

If you pick a favorite team, that choice is saved in a cookie named sb_bias in your own browser. It holds one thing — the team's short name, like alabama. Clearing your cookies erases it completely, and it is what lets pages highlight your team.

One thing said plainly rather than buried: at the moment you pick a team, the visit counter records which team was picked, tied to that month's session identifier. Which teams people pick is the question this site exists to ask, so that is the one choice it counts by name — under the same rules as everything above: reset monthly, kept on this server, shared with nobody.

Signing in creates an account. Google tells us three things about you, and we keep them:

• Your email address — so the account is recoverable and so the site operator can reach you about it.
• Your name — so the site can greet you instead of a user number.
• Your Google account's ID — an opaque number Google issues. It is what actually identifies you at sign-in, so changing your email address does not lose your account.

Using the site adds two more:

• Your favorite team — so your bias follows you to any browser you sign in on, instead of living in one cookie on one device.
• Your sign-in sessions — one row per browser you are signed in on, holding an expiry date and a one-way hash of the session token — never the token itself, and never a password. Google handles the password; the site never sees one.

Google's consent screen asks for your basic profile, so it says the site can “see your personal info” — that bundle also carries things like your profile photo, your given and family names and your locale. We keep only the three things listed above. The rest is discarded on arrival and never written down. Your contacts, your calendar, your Gmail and your files are never requested at all.

Being signed in also sets a cookie named sb_session in your browser. It holds a random token — not your email, not your name — and it is what keeps you signed in between pages. Signing out deletes it and the matching session row.

Nobody. It is not sold, shared, or handed to an advertising company or anyone else's analytics service — the visit counter above is the site's own copy of Umami, not a third-party service, and it reports to no one. Everything lives on the site's own server: account data in the site's database, visit counts in the counter's separate one. The only third party in the picture is Google, and only because you chose to sign in with it.

You can have your account — and everything the site holds under it — deleted, permanently. Signing out ends a session; deleting the account removes the row itself, the sessions with it, and your saved team. The near-exception is the anonymous visit counts: they are not tied to an account, and — as described above — past months cannot be matched to a person, so those age out on their own schedule; the current month's rows usually can be — ask promptly and the site will try.

To do it, contact the site operator. A published address for these requests is being set up and will appear here the moment it works — we would rather say that than print an address today and quietly drop your request.

You can also just stop signing in. Sessions expire on their own, and clearing your cookies removes the favorite-team cookie from your browser — though that alone does not delete the account.

If what the site stores ever changes, this page changes with it. It is the description of what the code actually does, not a legal document written around it.