little partyBack to home
Privacy · Updated September 15, 2026

Privacy Policy

This policy describes how LittleParty handles information when people create parties, send invitations, RSVP, and play games.

Information we collect

  • Host accounts: name, email address, authentication records, and account settings. Password authentication is handled by Supabase; LittleParty does not store readable passwords in its party records.
  • Party and invitation details: names, dates, times, venue and address, virtual links, registry links, messages, guest-list entries, and other details supplied by a host.
  • RSVPs: guest name, email address or phone number, attendance, headcount, a private note, and an optional playful prediction.
  • Games: nicknames, answers, parent answer keys, scores, and game progress.
  • Technical information: security and authentication cookies, browser storage used for private links and answer drafts, network information used for abuse prevention, and basic request logs maintained by our providers.

How we use information

We use information to create accounts, run invitations and RSVPs, operate games, keep the service secure, prevent abuse, respond to support requests, and maintain the service. We do not use RSVP contacts to enroll guests in marketing.

Who can see information

Anyone holding a shared invitation link can see the event details shown on that invitation. The host can see the guest list and RSVP responses. During a game, participants may see questions, revealed answers, nicknames, and results as part of playing together. Private host, parent, and RSVP edit links should only be shared with the intended person.

Service providers

LittleParty uses Railway for application hosting, Supabase for authentication and database services, Cloudflare for Turnstile abuse prevention and Web Analytics, and Resend for account emails. These providers process information for LittleParty under their own service terms and privacy commitments.

Cookies and browser storage

We use essential authentication and security cookies. Browsers may also store a party access credential, private RSVP edit credential, and unfinished answer draft so the service can remember access and recover work. We do not currently use advertising pixels or behavioral advertising cookies.

First-party measurement

We measure distinct browsers using a random, first-party cookie that expires after 30 days. Our database stores a keyed hash of this identifier and the visit date; this measurement does not store your IP address, page URL, party details, or answers. We also summarize account and party activity and record sanitized API failures and slow requests to maintain the service. These records use our existing Supabase database and Railway hosting.

We honor Do Not Track and Global Privacy Control signals for visitor measurement. Blocking cookies, using another browser, or clearing storage affects visitor counts. You can also turn off this measurement below.

Website analytics

We use Cloudflare Web Analytics to understand visits, page views, referring sites, broad device and country information, and page performance. It does not use analytics cookies or track people across websites. Cloudflare does not log URL query strings in Web Analytics. We do not send account names, email addresses, party answers, or RSVP details as analytics events. Browser blockers may prevent measurement.

Retention and deletion

Hosts can delete their profile and hosted parties from My Parties. Guest data remains with the party until it is removed through the host account or a verified privacy request. We plan to remove finished parties and parties with no activity for 12 months as the automatic retention process becomes available. Until then, hosts should delete parties they no longer need, and guests can ask us to delete their information. Provider backups and security logs may remain for the provider’s limited backup or security period after active records are removed.

Your choices and requests

You can update an RSVP with its private edit link. To request access, correction, or deletion, email hello@littleparty.live. We may need enough information to verify the request and protect other people’s records.

Children and sensitive information

LittleParty is designed for people organizing and attending events, not for collecting information directly from children. Do not put medical details, passwords, private links, or other sensitive information into party or RSVP notes. Share sensitive event needs directly with the host.

Changes and contact

We will update the date at the top when this policy materially changes. Questions or privacy requests can be sent to hello@littleparty.live.

little partyMade for getting together.
Browse gamesHelp & contactPrivacyTermsFeedback
hello@littleparty.live