Skip to content
SHAREHOLDER PARTY

Privacy and Cookies

Written to be read. It is a small game and there is not much data, so this page can afford to be specific instead of defensive.

Shareholder Party is run by one person. There is no data team, no customer profile and nothing to sell. What follows is the complete list of what is stored, where, and why.

Playing as a guest

You can play everything without an account. To do that, the site needs to be able to tell that the person taking turn four is the same person who took turn three, so it sets one cookie:

  • sp_guest holds a random identifier and nothing else. No name, no email, no IP address, nothing about your device. It is httpOnly, so the page's own JavaScript cannot read it, and it is cryptographically signed so nobody can edit it to impersonate another player. It lasts a year and is used only to identify you inside a game room.

That is the only cookie the game itself sets. Clear it and you are a brand new employee, with no way to get back into a game you were part of.

What your browser keeps locally

Two things live in your browser's local storage. They never leave your device unless you are signed in, and we cannot read them from here:

  • Your display name, so you are not asked for it before every game.
  • Your daily puzzle progress: which days you have completed, what you scored, and the half-finished state of today's puzzle so a refresh does not restart it. This is what your guest streak is calculated from. Old dates are pruned automatically.

Clearing site data resets your name and your streaks. That is unavoidable for guests, and it is the main practical reason accounts exist.

Accounts

Accounts are optional and only add persistence across devices, plus a place on the leaderboard. If you create one, we store:

  • Your email address, used for signing in, resetting a password and nothing else.
  • A username and a display name you choose. The display name is shown to other players in a room.
  • Your daily results: which game, which date, what you scored.

Passwords are handled by Supabase Auth, which stores them hashed. We never see them. No marketing email is ever sent, because there is no marketing.

Finished games

When a game completes, the result is recorded: the room code, the settings, when it started and finished, and one row per player with their display name, whether they were a temp, placement, Shareholder Value, objectives, activity wins, laps, tiles moved and how many memos landed on them. Those rows are attached to your account if you have one, or to the random guest identifier if you do not.

These records are public in the sense that they feed the leaderboard and profile pages. They contain no email address and no message content. Live rooms in progress are held separately and deleted once they go stale, so an abandoned lobby does not sit around forever.

Messages you send us

The contact form stores the subject, the message and the email address if you chose to give one. That is all it stores. It is read by one person, kept while it is useful, and deleted when it is not. It is never used to contact you about anything other than the thing you wrote in about.

Analytics, if it is switched on

This deployment may run PostHog product analytics. It is optional: with no project key configured, no analytics code initialises at all and nothing is collected.

When it is on, it is deliberately restrained:

  • Page views, page leaves, and a small number of named events such as “a room was created” or “a daily was completed”.
  • The usual technical context that comes with any web request: rough location from your IP address, browser, operating system, referring page and screen size.
  • An anonymous identifier stored in local storage and a cookie, so two page views in one session are not counted as two people.
  • Autocapture is turned off, which means it does not record every click, keystroke or form field. There is no session replay and no heatmapping.

It is used to answer questions like “does anybody finish a game” and “which daily do people give up on”. PostHog is configured against its EU cloud region.

Advertising, if it is switched on

This deployment may run Google AdSense to cover hosting. It is also optional: with no AdSense client id configured, the script is never loaded, no ad slot renders and there is no third-party code on the page at all.

When it is on, Google's script is loaded from Google and Google may set its own cookies or read existing ones to measure and personalise advertising. That processing is Google's, under Google's terms, and is not something we can see or control. Ads never appear during a live turn or an activity, and an ad slot that does not fill leaves no visible gap. If you want to understand or change what Google does, these are the pages that matter:

What we do not do

  • We do not sell or rent your data. There is nobody to sell it to and nothing worth buying.
  • There are no tracking pixels, no social login trackers, no advertising networks and no third-party scripts beyond the two named above.
  • We do not build profiles of you, and we do not use anything you do here to target you elsewhere.
  • We do not knowingly collect anything from children, and accounts are for 13 and over.

Where it is processed

Hosting is on Vercel and the database is Supabase, both configured to EU or UK regions, as is the analytics if it is enabled. Some technical processing, such as the content delivery network that serves the page to you, is inherently global. Where a provider transfers data outside the UK or EU, it does so under the standard contractual protections in its own terms.

Your rights

Under UK GDPR you can ask us to do all of the following, and we will, free, within a month. In plain English:

  • See it. Ask for a copy of everything held about you.
  • Fix it. Ask us to correct anything wrong.
  • Delete it. Ask us to delete your account and your records.
  • Take it. Ask for your data in a portable format.
  • Object. Tell us to stop processing it, including for analytics.

The lawful bases are simple. Running the game for you is contractual necessity. Keeping the site working, secure and not overrun by abuse is legitimate interests. Optional analytics and any advertising cookies rest on consent, which you can withdraw with your browser or with the Google settings above.

To delete your account: send a message from the contact form, using the email address on the account or telling us the username, and ask for deletion. The account, the profile and the daily results go. Completed game rows are kept but the link to your account is removed, so the row becomes anonymous rather than vanishing and rewriting other people's finished games.

Guests have nothing to delete on our side beyond a random identifier. Clearing your cookies and site data does it.

If you are unhappy with how we have handled a request you can complain to the Information Commissioner's Office, the UK regulator.

Honest limitations

We hold no security certifications and claim none. This is a game made by one person, hosted on mainstream providers, with sensible defaults: no passwords stored by us, no payment details anywhere, service-role database access confined to the server, and row-level security on every table. That is the accurate description, and it is not the same thing as an audit.

Changes to this page

If what is collected changes, this page changes with it, and the change is described here rather than buried. There is no version history worth publishing yet.

Related reading: terms of use, about, how it works and contact. Or go and play: a game, open rooms, the four dailies.