Privacy

Who runs Seated

Seated is built and operated by Kunal Agarwal, an individual, not a company. There is no team behind it and no other party involved in running it. Write to kunal.95a@gmail.com about anything on this page.

Signing in with Google

Signing in is the only thing Seated uses Google for. It requests three scopes — openid, email and profile — and nothing else. It does not ask for, and cannot read, your Gmail, Drive, Calendar, contacts or any other Google service.

From those scopes Seated receives and stores three things: your email address, your name and the URL of your Google profile picture. Nothing else from your Google account is received or kept. The picture itself stays on Google's servers — only its address is stored, and your browser loads the image from Google when it is shown.

They are used for signing you in and deciding what you may do. The email address identifies you, and it is how an event manager grants access — to run an event, to deal at particular tables, or to see nothing at all until you are admitted. Your name and picture are shown to other staff on the same event so they can tell who did what. Your name and email address are also sent to the analytics provider so a recording of a staff session can be tied to the person who made it — see analytics and session recording. They are stored in the app's database (see below), are not sold or shared with anyone beyond the providers named on this page, and are deleted on request — see asking for your data, or its deletion.

What Seated stores about staff

• Your email address, name and Google profile picture URL.
• Your role on each event, who granted it, and which tables you are assigned to.
• Requests you make to join an event or to deal at a table, including any note you type, and the decision on them.
• An audit trail of the changes you make in the app — seating a player, editing a session, changing settings — with your user account, a timestamp, and the before and after values of what you changed.
• Every attempt to use an event invite code: the code typed, whether it worked, your account, the time, and the IP address the request came from. This exists only to stop codes being guessed, and is the one place Seated records an IP address itself.

The audit trail exists so that a disputed leaderboard position or payout can be traced back to who entered what, and when. An event's managers can read their event's audit trail.

What Seated stores about players

The players at the tables are not users of Seated. They do not sign in and they have no account. Their records are typed in by event staff so the floor can keep track of who is sitting where.

• A display name, and optionally a nickname, a phone number, a photo and short staff notes.
• Seat activity: when they were seated, sat out, came back, moved table or racked up, at which table and seat, and the hours that add up from it.
• Buy-ins recorded before that feature was withdrawn on 5 September 2026: the amount, the method (cash, chips, credit or transfer), any note on them, and whether one was later voided, by whom and why. Nothing is added to this any more — the app no longer records or shows any amount — and the rows already written are kept so past payouts stay checkable.

The leaderboard is not stored — it is worked out from those hours each time it is shown.

Staff must have a reason connected to running the event before entering someone's details, should enter only what the event actually needs, and should tell the player their details are being recorded if asked. A phone number, a photo and notes are all optional; a name alone is enough to seat someone. Photos are hidden from the board unless both the event's photo setting and that player's own setting are turned on — otherwise initials are shown. Money is never shown on the board or on the Floor TV.

One player record, shared across events. A person added at one event is one record in a single registry, so staff of a different event who search their name will find it and can see the name, the nickname, how many past events that person has been on and their lifetime hours. Adding them to a second event's roster also shows that event's staff the stored phone number, photo and notes. Bear that in mind before typing anything into a note.

If you are a player and want to know what an event holds about you, or want it removed, ask the event staff, or write to kunal.95a@gmail.com.

Who can see it

• Staff admitted to an event see that event: its roster, its tables and its sessions. A table manager works the tables assigned to them; a floor manager sees the whole event, its audit trail and its settings.
• A floor manager can download the event's sessions, leaderboard, and the buy-ins recorded before recording was withdrawn, as CSV files. What happens to a downloaded file is then in that person's hands, not the app's.
• The operator of Seated is a super admin and can technically reach any event's data. That access is used to keep the app working and to answer requests like the ones on this page.
• A paired Floor TV shows the public board for one event: names or nicknames, hours, table and seat, and photos only where both photo settings allow it. Never money.

Where the data lives

• The database is Neon Postgres, in Singapore. Everything above except photos is stored there.
• Player photos are uploaded to Vercel Blob. A stored photo has a long, unguessable web address, and anyone who has that address can open the image without signing in — so treat a photo as confidential only to the extent that its address is not passed around.
• The app runs on Vercel, in its Singapore region. Vercel keeps short-lived server logs of requests to the app, which include IP addresses, in the ordinary way any web host does.
• Usage data and session recordings go to PostHog, in the United States. This is the only data that leaves the Singapore region. What it contains is set out in the next section.

Neon and Vercel make the app run; PostHog measures how it is used. All three hold the data on the operator's behalf and are not permitted to use it for their own purposes. Nobody else receives it.

How long it is kept

An event's history is kept after the event ends. Hours played decide prizes, so the sessions, seat events, buy-ins and the audit trail behind a payout stay available for people to check a result against. Deleting them would make the payouts unauditable.

Staff accounts — the email address, name and picture URL received from Google — are kept while the account is in use, and are deleted within 30 days of a request. Where entries in an audit trail name you, they are reduced to a deleted user rather than erased, so the event's record still adds up. A player's photo, phone number and notes can be removed at any time on request without disturbing the hours. Invite-code attempt records, with their IP address, matter only for the ten minutes of rate limiting that follow the attempt; they are used for nothing else and are deleted on request. Anything not needed for a past event's record is deleted when asked.

Analytics and session recording

Seated measures how staff use it, so that problems can be found and the app improved. The provider is PostHog, in the United States. This applies to the staff app; it is not used to profile players, who never sign in.

• Usage. Which pages are opened, which actions are taken and when, plus the device, browser, operating system and the approximate location worked out from the IP address.
• Session recordings. A replay of a staff member's screen as they use the app — what was displayed, what was clicked, and what was typed into forms. Recording is not masked, so a replay of a manager working shows whatever was on their screen at the time: player names, phone numbers, buy-in amounts and settlement figures included. Handwritten signatures are the one exception — they are drawn on a canvas, which is never recorded and appears blank.
• Who. A staff member is identified to PostHog by their Seated account id, name and email address, so a recording can be tied to the person who made it. That identification is sent from the server, never from the browser.
• Players. Players are never identified to PostHog and have no profile there. They appear only where their details happened to be on a manager's screen during a recording.
• Floor TVs. A paired TV is counted so it is known whether the board was up. It is never recorded and is not tied to any person.
• Errors. When something breaks, the error and the page it happened on are sent so it can be fixed.

If you are a staff member and would rather not be recorded, or want your recordings removed, write to kunal.95a@gmail.com. Usage data and recordings are deleted on the same request basis as everything else on this page.

What Seated never does

• No data is sold, rented or traded, ever.
• No advertising, and no data used to target ads anywhere.
• No advertising trackers, and no third-party tracking across other websites. Seated does measure how staff use Seated itself — see “Analytics and session recording” below.
• No sharing beyond Neon, Vercel and PostHog — no partners, no data brokers, no marketing lists. The one exception would be a valid legal demand.
• Nothing here is used to train AI models, and it is not given to anyone else for that purpose.

Cookies

Seated sets cookies to sign you in, keep you signed in, and measure how the app is used. None of them track anybody across other sites.

• A signed session cookie, set after you sign in with Google. It carries your account id, your email address, your name, your picture URL and whether you are a super admin, so each page load knows who you are without another trip to Google.
• A few short-lived cookies the sign-in library sets while the round trip to Google is in progress — a token that protects the form, the address to return you to, and one-time values that protect the exchange. They are not used for anything after sign-in.
• On a paired Floor TV, a cookie that lasts a year. A manager generates a pairing code, the TV types it once, and the cookie lets that screen show the board without a login. It is limited to the board for that one event and holds only a random pairing token.
• A PostHog cookie holding a random id, so repeat visits from the same browser are recognised as one person rather than a new one each time. It is limited to Seated and is not used to follow anybody across other websites.

There are no advertising cookies.

Asking for your data, or its deletion

Email kunal.95a@gmail.com to see a copy of what is held about you, to correct it, or to have it deleted. Write from the address you signed in with, and say which event it concerns if you know. Requests are handled personally, normally within 30 days. Where a record is needed to keep a finished event's payouts auditable, you will be told which part is being kept and why, and everything else will go.

You can also disconnect Seated from your Google account at any time at myaccount.google.com/permissions. That stops future sign-ins, and Google stops sharing your email, name and picture with the app; it does not by itself delete what is already stored, so email the address above for that.

Google API Services User Data Policy

Seated's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In practice that means the email address, name and profile picture received from Google are used only to run the app: to sign you in, to decide what you may do in it, and — for the email address and name — to attribute a staff member's own usage of Seated so that problems can be traced to the session that caused them. They are never transferred to anyone other than the providers named on this page that run and measure the app, or as required by law; they are never used for advertising or sold to anyone; they are never used to build an advertising profile, and the usage record they are attached to covers this app alone and nothing you do elsewhere; and no human reads them except where you have asked for support, where it is needed for security, or where the law requires it.

Changes to this policy

If what the app does changes, this page changes with it and the date at the top moves. There is no mailing list to announce it on — the current version is always the one here.