Privacy

The short version

You never make an account. A room is a question, some options, the first names people type in, and how each person split five hype across the options. How you spent your hype is private until everyone in the room has committed. After that, the room shows totals — never a list of who chose what.

What SamePage stores

Things you type

• The question — up to 120 characters.
• The options — two to eight, up to 80 characters each.
• A display name — up to 30 characters, entered per room. It is whatever you type. There is no requirement that it be your real name.

How you played

• Your hype allocation — how many of your five points you put on each option, and when you committed.
• The aggregate result — per-option totals, how many people backed each option, and the largest single stack on each option. Written once when the room resolves.

Identifiers

• An anonymous sign-in. The first time you create or join a room, your browser is signed in anonymously with Supabase. That produces a random identifier with no email address, no password and no profile. It exists so the database can tell one player from another inside a room.
• A session cookie. The anonymous session is stored in a cookie so the server can render your room. It is strictly necessary — without it the product cannot tell whether you are in a room. SamePage sets no other cookies, and no analytics or advertising cookies of any kind.
• Two things held on your device only. While you are deciding how to spend your hype, that in-progress split is saved in your browser's session storage so a reload does not throw it away; it is deleted the moment you commit. And if you choose “Run it back”, the question, the options and the name you were using are carried across that one step so you do not have to retype them. Both live only in the tab you are using, never leave your device, and are discarded when you close it.

Technical information

SamePage itself does not collect analytics, does not embed third-party scripts, and does not load fonts from anyone else — the typeface is served from the same origin as the site. However, the infrastructure that runs it processes ordinary request data such as IP address, timestamp and browser user agent in its logs, as any web service does. Today that means Supabase (database, anonymous authentication and realtime) and HOSTING PROVIDER TO BE CONFIRMED.

Who can see what

Anyone with the room link

• The question and the list of options.
• The first name of the person who created the room, and how many people are in it.
• Once the room has resolved: the winning option or options, each option's percentage share, and the ranking.

Someone holding only the link does not see the list of players, the number of players, raw hype totals, or anything about how any individual spent.

People in the room

• Everyone's display name, and whether each person has committed yet. Not what they committed.
• After the room resolves: totals per option, how many people backed each option, and — only in rooms of three or more — the largest single stack on an option, without saying whose.
• Your own allocation, shown only to you.

Nobody, ever

There is no screen, no link and no API call anywhere in SamePage that maps a person to what they spent. Individual allocations are stored in a table that no browser has permission to read at all — every read goes through a function that returns aggregates only.

An honest limit on anonymity

Aggregates can be reasoned about. In a room of two people, seeing the totals and knowing your own allocation tells you the other person's exactly — that is arithmetic, not a leak, and no product design can prevent it. Small rooms allow partial inference for the same reason. SamePage therefore withholds the largest-single-stack detail in rooms of fewer than three people, and does not promise that your choices are unknowable — only that SamePage will never publish them.

How long it is kept

Rooms are currently kept until they are deleted. RETENTION PERIOD DECISION REQUIRED — a retention window for abandoned and completed rooms has not yet been set, and this section must state a specific period before launch.

Deleting a room

The person who created a room can delete it. Deleting removes the question, the options, every player's display name, every hype allocation and the result — permanently, and for everyone with the link. Authorisation is the creator's anonymous session, not possession of the link: someone who was merely sent the result cannot delete it.

Because sign-in is anonymous, clearing your browser storage discards the identity that owns your rooms. SamePage cannot restore that, and cannot verify ownership afterwards.

Service providers

• Supabase — database, anonymous authentication and realtime messaging. Stores everything listed above. SUPABASE REGION AND DATA PROCESSING TERMS TO BE CONFIRMED
• HOSTING PROVIDER TO BE CONFIRMED — serves the application and processes request logs.

INTERNATIONAL TRANSFER LANGUAGE REQUIRES REVIEW — depending on where the database is hosted and where users are, this section may need transfer-mechanism wording.

Security

Individual allocations live in tables with no read permission granted to any browser-facing role. Every read and every write goes through a small set of server-side functions that re-derive who you are from your session rather than trusting anything the browser sends. Room codes are generated from a cryptographic random source. Traffic is served over HTTPS in production. No system is perfectly secure, and SamePage does not claim otherwise.

Children

MINIMUM AGE DECISION REQUIRED — a minimum age has not been set. This depends on the jurisdictions SamePage is offered in and must be decided before launch.

Your rights

Depending on where you live you may have rights to access, correct, delete or export your personal data, or to object to its processing. Because SamePage holds no account and no contact details, the practical route for most of these is deleting the room. For anything else, contact us.

PRIVACY RIGHTS PROCESS REQUIRES LEGAL REVIEW

Changes

If this policy changes, the date at the top changes with it. Material changes will be described here rather than made quietly.

Contact

CONTACT EMAIL REQUIRED · LEGAL ENTITY AND ADDRESS REQUIRED