Thursday Night
Privacy Policy
Effective August 11, 2026 · Last updated August 19, 2026 · Replaces the policy dated July 11, 2026
Thursday Night is built to need very little about you. But it is no longer true that it needs nothing — planning a night involves email addresses, phone numbers, and who's coming. This policy says exactly what exists, where it lives, and how to get rid of it.
The controller of this information is Thursday Night Studios LLC, Massachusetts, USA. Questions, requests, and deletions: support@thursday-night.com.
Two halves, very different
Thursday Night has a VR/desktop app and a website, and they collect wildly different amounts.
- The app collects almost nothing. No account, no sign-in, no analytics, no telemetry, no advertising, no tracking SDKs. Nights are hosted on a player's own PC and never touch a server of ours.
- The website collects real personal data, because scheduling a night means knowing who to invite and how to reach them.
What the website stores
When you plan or join a night at thursday-night.com, the following is stored in our database:
| What | Why |
|---|---|
| Email address | Signing in (we email you a link — there are no passwords), and sending you invites and reminders. |
| Phone number — only if you give one | Sending an invite as a text message. We deliver these through carrier email-to-SMS gateways, which means your number is used to build a gateway address and the message passes through your mobile carrier. |
| Your friends list — names, and the email or phone you saved for each | So you don't retype your crew every week. |
| Nights and RSVPs — title, date and time, venue, the movie options, who was invited, who voted for what, who said they're coming | It's the actual product. |
| Host records — which account owns a night, and host tokens | So only the host can edit their own night. |
| Sign-in and device tokens, and per-invitee codes | Keeping you signed in, and letting an invited person open their personal link without an account. |
| Poster images for a night's ballot | Cover art on the voting screen, including generated parody posters. |
| Terms agreement — which version of these documents you accepted, and when | So we both have a record of what you agreed to. We do not store your IP address or your browser with it. |
We do not collect: payment details, location, contacts from your phone, biometrics, or anything about you from other services. We do not run analytics or advertising, and we never sell or rent your information.
Who processes it (our sub-processors)
| Provider | Role |
|---|---|
| Supabase | The hosted Postgres database and file storage where the data above lives. |
| Cloudflare | Serves this website and runs the worker that handles the API, proxies sign-in links, and sends reminders on a schedule. Standard request logs. |
| Resend | Delivers transactional email — sign-in links, invites, reminders. |
| Your mobile carrier's SMS gateway | Delivers text invites, when a phone number is used. |
| TMDB and fanart.tv | Looked up for poster artwork. We query them for a movie title; we don't send them anything about you. |
These providers process data on our behalf under their own terms, and are located in the United States. Nothing is shared with anyone else.
Voice chat
Your microphone audio never reaches us. We do not receive, record, store, or upload your voice, and none of it is sent to any server of ours or to a third party.
Voice is captured only while your mic is unmuted, and it is transmitted live to the other people in your room, relayed through the host player's own computer. Browser participants connect directly to the host. A public STUN server (Cloudflare's) is used to help two computers find each other's network address — it carries no audio. There is no TURN relay and no voice server, so your audio physically cannot travel through anything we operate. You can mute at any time, and everyone can see when you're muted.
The honest caveat
We audited the code before writing this, and the flat claim "voice is never recorded anywhere" would be an overstatement, so here is the precise version. Two features can write audio to the host's own hard drive — never to us, never uploaded:
- Screen sharing. A legacy compatibility mode of the screen-share feature captures the host's screen along with their computer's speaker output — which can include other people's voices as the host's PC plays them — into a temporary video file on the host's machine. It is overwritten the next time a share starts. This mode is off by default.
- A diagnostic flag. A developer command-line option used for audio-tuning tests writes short recordings of the app's audio output to the host's local disk. It is not reachable from any menu and is off unless deliberately enabled.
Both produce files on the host's own computer only, under that person's control. We never see them. If you're in someone's room, the practical takeaway is the same as any video call: the person hosting could record their own screen and speakers if they chose to, exactly as they could with any other software on their PC.
What the app keeps on your device
- Your display name, so friends know which avatar is you. It's shown to people in your room and saved on your own device.
- Your settings and avatar look, saved locally.
- Per-person volume preferences — if you turn someone down, that preference is saved on your device next to their display name.
None of this is sent to us.
Network addresses and room codes
Joining a room uses a 7-character room code. IP addresses are used to make the connection between players, the way a phone number is used to place a call, and are not logged or stored by us beyond the life of the session. There is one exception, and it is the room-code registry described just below: because a room code is a short form of the host's address, an entry there holds that address for up to 12 hours after the host's last check-in.
Two specifics worth naming:
- When you host, your computer asks a public service (api.ipify.org) for its own public network address so it can build your room code. No personal information is sent with that request.
- If you host with the browser-viewing feature on, your computer publishes {room code → a temporary tunnel address} to a small registry we run at thursday-night.com, so a friend typing your code gets sent to the right place. That entry is your room code — which, as above, is a short form of your public network address — mapped to a temporary tunnel address. It holds no name, email address or account information, and it expires automatically within 12 hours.
How long we keep things, and how to delete them
Website data is kept while your account exists. Sign-in tokens expire on their own. Registry entries expire within 12 hours.
To delete your account and everything attached to it, email support@thursday-night.com and ask. We'll do it and confirm. Being straight with you: there is no self-service delete button yet. It's a known gap and it's on the list. Until it exists, the email is the mechanism, and it is a real one.
Deletion removes your account, your friends list, your nights and RSVPs, and your sign-in tokens. Nights you were invited to by someone else belong to that host and may keep a record that an invitation existed. Backups roll off on their own within about 30 days.
Your rights
Wherever you live, you can ask us to show you what we hold about you, correct it, delete it, or send it to you in a portable form. Email support@thursday-night.com and we'll handle it — we aim to respond within a few days and no later than 30 days. We won't treat you differently for asking. We don't sell or share personal information for advertising, so there is nothing to opt out of.
Children
Thursday Night is for people 13 and older, matching the app's age rating. We don't knowingly collect information from anyone under 13. If you believe a child under 13 has given us information, write to us and we will delete it.
Security
Connections use HTTPS. Sign-in is by emailed link rather than a password, so there is no password of yours to leak. API keys and database credentials are held in managed secret storage, never in the app or the website. No system is perfectly secure, and we won't pretend otherwise — but there is deliberately very little here to steal.
Changes
If a future version changes what we collect, this page is updated before that version ships, and the date at the top changes with it. Material changes will be announced here.
Contact
Thursday Night Studios LLC — Massachusetts, USA
support@thursday-night.com