Privacy Policy

Who we are

sip & play is an independently operated service based in Virginia, United States.

Information we handle

• Host accounts: name, email address, Google account identifier and verification status, account settings, and sign-in records. Existing password accounts store a password hash, not a readable password. We do not receive your Google password.
• Events: couple names, event dates and venues, questions and answers, branding choices, and other content supplied by the host.
• Guests: display names, trivia answers, scores, completion status, timestamps, and a token used to resume your attempt. Optional guest-book notes and their associated names are also stored.
• Security and support: event reports and communications you send us. The app uses a hashed account or IP-based identifier for rate limiting. Hosting and authentication providers may process IP addresses, browser information, and request logs to deliver and protect the service.

Please use a nickname if you prefer, and do not submit sensitive information such as financial details, health information, passwords, or private information about someone else without their permission.

How we use information

We use information to sign hosts in, operate and personalize events, save progress, calculate scores, display leaderboards, deliver guest-book notes, respond to requests, prevent abuse, and meet applicable legal obligations. We do not sell personal information or use guest answers or notes for targeted advertising.

Where data-protection law requires a legal basis, we rely on providing the service you request, legitimate interests in operating and securing it where appropriate, legal obligations, or consent where required. The appropriate basis depends on the activity and your relationship to the service.

Who can see it

Event links are unlisted. Hosts can optionally require a guest passcode. Without a passcode, anyone with a published event link can see its guest-facing content, play, and view leaderboard names and scores. Invited guests can still copy or forward content. Share links, passcodes, and event details accordingly.

Guest-book notes are not posted to the leaderboard. Hosts can read, download, retain, and share their event's notes. We cannot delete copies a host has already exported; contact the host about those copies.

Authorized service operators may access information as needed for support, safety, maintenance, or legal obligations. We use Vercel for hosting, Neon for database storage, and Google for host sign-in. These providers process information needed for their services and may operate in countries other than yours. Where applicable law requires safeguards for international transfers, those safeguards must apply.

We may disclose information when legally required or reasonably necessary to protect users, enforce our terms, or address fraud and security incidents.

Cookies and browser storage

For passcode-protected events, we use an event access cookie lasting up to seven days. Changing the passcode revokes prior access. We store passcodes as salted hashes, not readable text. We use a host session cookie lasting up to seven days and a short-lived Google sign-in security cookie lasting up to ten minutes. Signing out clears the host session cookie. Your browser also stores a guest attempt token so you can return to your game; that token can remain until you clear your browser's site data.

Google's sign-in component communicates with Google and may use its own cookies or storage under Google's privacy policy. Blocking cookies or clearing storage may prevent sign-in or access to your previous results. We do not currently add advertising trackers or third-party audience analytics to the app.

How long information stays

Account and event information remains while the account or event exists. For standard events, trivia attempts become eligible for deletion 90 days after the host closes the event, unless the event's management screen states a different retention period. Open events do not start this countdown. Demo attempts become eligible for deletion after 24 hours. Cleanup runs periodically, so removal is not instantaneous.

Guest-book notes are kept separately from trivia results and remain until the note, event, or account is deleted. Expired sessions, sign-in challenges, and rate-limit records are removed by periodic cleanup. Hosting logs, any backups, and records needed for security or legal obligations may remain for their applicable retention periods after removal from the active database.

Your choices and requests

Hosts can edit or delete events, delete guest-book notes, export guest-book content, and delete their accounts through event management. Account deletion removes the account's events and associated guest data from the active database, subject to applicable exceptions.

Guests can ask the event host about their event content or exported notes. A dedicated service privacy contact is not yet available; contact details will be added here. The host controls their event content and exports, but may not be able to resolve every request about information held by the service. Do not share passwords or browser tokens with anyone handling a request.

Depending on where you live, you may have rights to access, correct, erase, receive a copy of, restrict, or object to processing of your personal information, withdraw consent where processing relies on it, or complain to your local data-protection authority. We will handle requests as required by applicable law.

Children and security

The service is not directed to children under 13, and we do not knowingly collect their personal information. Please do not use the service or submit information if you are under 13. If we learn that a child under 13 has provided personal information, we will investigate and remove it as appropriate.

We use safeguards designed to protect information, but no online service can guarantee absolute security. Keep account access and guest attempt tokens private.

Changes to this policy

We may update this policy as the service changes. We will update the date above and provide additional notice where required by law. A policy update does not replace consent where consent is required.