# FairCourt Privacy Policy

Last updated: 2026-06-05

FairCourt is designed as an offline-first pickleball host app. The core app does not require an account, Firebase, or a FairCourt server for creating events, scheduling matches, scoring, rankings, local QR boards, backups, or recap images.

FairCourt is published on Google Play by MAI THANH TU. The public developer support email for this release is khanhsaco999@gmail.com.

## Data The App Stores Locally

FairCourt stores the following on the host device:

- Event names, court count, rounds, points, format, and schedule policy.

- Player display names, skill level, status, seed order, and local avatar color.

- Generated rounds, matches, scores, ranking stats, fairness reports, reflow logs, and recap awards.

- Local entitlement state and hashed Google Play purchase-token references for Event Credit and the three independent weekly subscriptions.

- Offline live-board snapshots and QR payloads generated by the host.

- Optional backup JSON exported or imported by the host.

## Data Sharing

FairCourt shares data only when the host chooses to share it, such as:

- Sharing a recap image through the Android share sheet.

- Showing or sharing a local QR board snapshot.

- Exporting backup JSON from Settings.

Public board snapshots must not include purchase tokens, email addresses, phone numbers, owner-private data, or raw billing identifiers.

## Network Use

The core offline app does not need a FairCourt server. Google Play Billing purchase/restore flows are handled by Google Play when the host buys Event Credit or the three independent weekly subscriptions.

The current Play release verifier checks that the merged Android release manifest includes only Google Play Billing for purchases and does not request network, camera, microphone, location, contacts, broad storage, notification, SMS, phone-state, or broad package-visibility permissions.

## Purchases

Debug builds may include local fake unlocks for testing. Production Play releases use Google Play Billing for Event Credit and the three independent weekly subscriptions. Consumable credits are granted only after Google Play reports a completed purchase, FairCourt saves a hashed purchase-token ledger entry, and the app then consumes the purchase.

## User Controls

Users can:

- Keep using core scheduling and scoring offline.

- Export backup JSON from Settings.

- Import backup JSON explicitly from Settings.

- Reset all local FairCourt data from Settings.

- Delete app data through Android system settings.

## Android Backup

The current Android release disables Android Auto Backup, cloud backup, and device-transfer data extraction for FairCourt app data. This keeps the primary backup path explicit: users export and import FairCourt backup JSON from Settings when they choose to do so.

## Children And Sensitive Data

FairCourt is not intended to collect sensitive personal data. Hosts should use display names or nicknames instead of private identifiers.

## Store Disclosure Notes

For Google Play Data Safety, the release disclosure should match the exact SDKs enabled in the submitted build. With Play Billing enabled and no analytics/crash SDK added, FairCourt should be disclosed as an offline utility that does not collect or share user data through a developer server. Recap, schedule text, QR board, and backup export surfaces are specific user-initiated actions by the host. If analytics, crash reporting, cloud backup, account login, or live online board publishing are added later, this policy and Data Safety answers must be updated before release.

## Contact

Developer name: MAI THANH TU

Legal name: MAI THANH TÚ

Public developer support email: khanhsaco999@gmail.com

Legal address: To 16, Hoa Phat, Cam Le, Da Nang, DA NANG - 50710, Viet Nam

The Google Play listing must link to the public HTTPS page that hosts this exact policy. The hostable HTML copy is maintained in `web/privacy.html` and included in the Google Play distribution package.