Privacy

Information used for your events

We store your sign-in email and public profile name, event access, and the family-player names and display labels you or your organizer provide. A reusable private account contact profile stores your account-holder name, verified email relationship, phone number with country code, contact-use acknowledgement and separate communication choices. Organizers can also maintain responsible contacts and their optional email addresses.

Event records include selected squares, entry charges, recorded external payments, published results, prizes, payout records and changes made by authorized organizers. The application tracks payments made outside the website; it does not collect card or bank credentials or transfer money.

These records let you manage named players, see your squares and balances, and follow results. Other authorized event participants can see board display labels and published winners. Private contact and financial information is limited to the appropriate account and authorized organizers.

Session cookies support sign-in. Authentication and hosting services also process request and security information to operate and protect the application. Administrative changes are recorded in an audit history.

Your contact profile across games

New online event enrollments require an account-holder name, verified email, phone number with country code and acknowledgement of the contact-use notice. The same account profile is reused when you choose to join another event. Existing participants with incomplete details keep their current memberships, owned squares and balances. Organizer-managed offline participation remains separate for someone without email or a phone; missing information is recorded honestly.

Authorized organizers can see your name, verified email and participation history through their private all-games directory, including archived events and enrollments without purchases. Access follows their actual event relationship; the directory does not import unrelated authentication accounts. Family players under an account are not separate message recipients.

Supplying a phone number does not verify ownership or authorize its disclosure. Phone sharing for the organizer directory is a separate affirmative choice, not inferred from a prior optional-phone choice, a purchase or future-email permission. A withheld number is not included in that directory. Other participants never receive private account contact details through the board.

You can update your profile, withdraw phone sharing or remove your phone through Account → Contact & notifications. New authorized organizer reads use the current disclosure choice; an open directory refreshes periodically and hides phone details when a fresh check is unavailable. Information an organizer already viewed cannot be unseen. Removing required information may make the profile incomplete for a later new enrollment, without revoking existing event access.

Future-event invitation emails are optional and separate from joining the current event. Missing permission is not an opt-in. Opting out does not stop sign-in codes or current-event transactional messages. Automated texts and phone-only login are unavailable, and no SMS consent is inferred from any contact choice.

The owner’s Gmail connection

Only the authorized owner connects the configured sending account. Participants do not need to connect Gmail. When the owner authorizes Google access, the application requests gmail.send to send transactional event messages, and openid and email to verify the sender’s email address and its verified status.

This connection does not request permission to read, search or modify the owner’s inbox, contacts or other mailbox messages. It is not a participant sign-in method.

The verified sender address and an encrypted Google refresh token are stored privately. The refresh token allows authorized sending without repeated consent; access tokens are handled temporarily by the server. Encryption keys and Google client credentials stay outside browser code.

When delivery is enabled, messages such as invitations, square confirmations, payment records, official-number notices and winner updates pass through the application’s private email queue and Google’s Gmail API. The queue retains the intended recipient, message data, delivery state and safe delivery identifiers for operational history. Authentication sign-in codes use Supabase Auth and separately configured SMTP, not this Gmail API connection.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Services and sharing

Vercel hosts the website, Supabase provides authentication and database storage, and Google processes authorized Gmail messages and sender verification. Information needed to provide these services is processed by those providers. Event notifications also share the relevant event information with their intended recipients.

We do not sell personal or Google account information, use it for advertising, or use it to train AI models.

Retention and your choices

Event, financial, notification and audit records are retained for event administration, accounting, correction history and recovery. Protected backups can also retain copies. There is no fixed automated deletion schedule; closing or archiving an event does not erase the reusable contact profile, and disconnecting Google does not automatically delete these records.

For access, correction or deletion requests, contact the organizer using the contact method they provided with your invitation. Requests require review, including which records need to remain for accounting, audit history or recovery. The application does not offer an automatic account or backup deletion process.

The connected owner can remove the application’s Google access in Google Account connections. Revoking access prevents further use of that authorization; it does not delete existing event records, sent messages or stored backups. Contact the organizer about removal of stored connection information.