Privacy Policy

1. Scope

This Privacy Policy explains how PokerNight (“we,” “us,” or “our”) handles information when you use the PokerNight mobile application, related invitation links, support channels, and this website.

PokerNight is a software tool for organizing and recording private home poker sessions. It is not an online casino, gambling operator, or payment processor.

2. Data we handle

Account and authentication data

When you create or access an account, we process an account identifier and authentication information such as your email address. Depending on the sign-in method you choose, Supabase Authentication, Apple, or Google may provide an authentication identifier and profile metadata such as a name, email address, or profile image. Authentication sessions and refresh tokens are stored on your device so you can remain signed in.

Profile data

Your profile may include a display name, nickname, username, avatar, language preference, and—in supported or migrated records—an optional phone number. Usernames, display names, nicknames, and avatar URLs are stored in the public-profile portion of the service and may be visible to authenticated users through profile search or social features. Uploaded profile avatars are stored in a publicly readable avatar bucket.

Player and guest records

A game host can create roster entries for themselves, registered players, and guests. These records may include a player name, nickname, email address, phone number, avatar choice, account-link status, roster status, creation/removal timestamps, number of games, and derived profit or loss statistics. A roster record may be linked to a registered PokerNight account through an invitation or connection flow.

Someone else may enter information about you as a guest or roster player. Those records belong to that host’s roster and can remain in their historical game records even if you later delete your own PokerNight account.

Game, activity, and settlement data

PokerNight stores information entered or generated for private sessions, including:

• game identifiers, owner, state, timestamps, chip conversion, currency, and participating players;
• buy-ins, rebuys, corrections, cash-outs, chip quantities, and final chip counts;
• user-entered payment-method labels (such as cash, Bit, or bank transfer) and payment-status records;
• calculated commitments, entitlements, profit or loss, settlement balances, and who-pays-whom instructions;
• game history, activity views, trends, records, leaderboards, and player statistics derived from finalized games; and
• technical command receipts, revisions, and event history used to keep the game ledger consistent.

PokerNight does not need payment card numbers or bank-account credentials to calculate a session. Values and payment-method labels are bookkeeping records; the app does not execute the transfers they describe.

Connections, invitations, and links

We process connection requests and statuses, invitation identifiers, link tokens or token digests, inviter and recipient identifiers, expiration and claim timestamps, and player-account links. These records let users connect, claim the correct roster entry, or access game data made available to them.

Device and technical information

The reviewed application uses network-connectivity status to manage online actions and connects to Supabase over the internet. Like most hosted services, Supabase and network infrastructure may receive request metadata such as IP address, request time, and technical headers. The exact infrastructure logging, region, and retention settings depend on the deployed Supabase configuration and must be confirmed by the operator.

Support information

If you contact support, we process the contact details, message content, attachments, and troubleshooting information you choose to send.

3. How we use data

We use the information described above to:

• create and authenticate accounts;
• provide profiles, rosters, connections, invitations, and account-linking features;
• run the game-management ledger and synchronize private session updates;
• calculate results, settlement instructions, history, and statistics;
• protect the consistency and integrity of game records;
• provide support and troubleshoot the service; and
• comply with applicable law and enforce our Terms.

4. Visibility and sharing

Data is shared within the product only as needed for its features:

• Game hosts can access the rosters and games they manage.
• Registered participants can access game or result data made available through their linked player identity and game membership.
• Connected or authenticated users may see discoverable profile fields used for search, connection, and invitation features.
• Anyone with an avatar URL may be able to view an uploaded avatar because the avatar storage bucket is configured for public reads.
• Service providers process data on our behalf as described below.

We may also disclose information where required by law, to protect rights and safety, or in connection with a business transfer, subject to applicable legal requirements.

5. Service providers and external services

The reviewed app integrates the following external services:

• Supabase for authentication, hosted PostgreSQL database, file storage, real-time synchronization, and server-side functions.
• Apple when you choose Sign in with Apple.
• Google when you choose Google sign-in.
• Expo / EAS for the app’s build and distribution infrastructure. Confirm whether any production update or observability service is enabled before publication.

These providers process information under their own terms and privacy practices. Data may be processed outside your country depending on the operator’s configured infrastructure and the providers used. The operator must confirm the Supabase project region and any legally required transfer disclosures before publishing this policy.

The reviewed source code did not contain an advertising SDK, behavioral analytics SDK, third-party crash-reporting SDK, push-notification integration, or payment-processing SDK. This statement is a code-audit result, not a substitute for verifying production configuration and business operations.

6. Retention and deletion

The reviewed code does not define one universal automatic retention period. Account, roster, game, history, and statistics data generally remain until the relevant user deletes them, resets owned history where supported, deletes the account, or the operator removes them as required by law. Invitation and link records can have their own expiration or status lifecycle.

The account-deletion backend is designed to remove the authenticated user’s account, profile records, uploaded avatar files, owned games, owned players, owned tables, connection records, and owned invitation-link records. It also removes the authentication user record.

Deletion does not necessarily erase records independently created and owned by another user. For example, your link to another host’s player row is removed, but that host’s roster entry, participant snapshot, and historical game records may remain without the link to your account. Backup and provider-level retention behavior must be confirmed from the production Supabase configuration.

To delete your account, use Settings → Account → Delete account in PokerNight, then confirm Delete account permanently. If you cannot access your account or the app, contact xlioramarx@gmail.com for help. See Account deletion support.

7. Security

We use measures intended to limit access to data, including authenticated sessions, database row-level access policies, scoped server-side functions, and restricted client write paths for financial ledger records. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.

8. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or receive a copy of personal data, or to object to certain processing. You can edit supported profile fields and delete your account in the app; contact us only if you need help accessing the app or exercising another privacy right. We may need to verify your identity before fulfilling a request.

You can remove connections in the app. Your device settings and the relevant Apple or Google account controls may provide additional options for third-party sign-in.

9. Children and age restrictions

PokerNight is not directed to children under 13. Private poker activity may be subject to higher minimum ages or other restrictions in your jurisdiction. Users are responsible for following local laws and for not providing children’s personal information through guest or roster records.

10. Changes to this policy

We may update this policy as the service or legal requirements change. We will post the revised policy here. Material changes may also be communicated in the app or through another appropriate channel.

11. Contact