Boardgammon Privacy Policy

1. What we collect

Account and identity

• Email address when you sign in by magic link or through Apple, Google, or Google Play Games.
• Display name and the Boardgammon user ID we mint for your account.
• Provider subject identifiers for Apple, Google, Google Play Games, and email sign-in.

Gameplay

• Match state, moves, dice commit-reveal proofs, and the replay hash chain that makes online games auditable.
• Ratings, games-played counters, puzzle progress, streaks, and daily puzzle activity.

Social and safety

• Table reactions and canned-message catalog IDs. Boardgammon does not support free-form chat in v1.
• Friend relationships, blocks, mutes, and abuse reports.

Notifications, purchases, and diagnostics

• Push tokens and the app version / locale received with them.
• Purchase entitlement state for Pro and similar unlocks. Apple and Google handle payment details directly.
• Crash and performance telemetry through Sentry, plus aggregate product-usage analytics through Firebase.

2. Optional in-match voice chat

Voice chat is optional, available only to the two seated opponents in a live realtime match, and requires both players to opt in. Either player can mute the other at any time. Boardgammon uses WebRTC with relay-only TURN transport.

• Boardgammon does not record or store audio content.
• We store only voice metadata: who called whom, when the call started and ended, duration, end reason, and relay-usage estimates.
• We also store a self-attested date of birth and a voice opt-in flag so voice can fail closed when age or consent is missing.
• Cloudflare Realtime TURN relays encrypted media and necessarily sees connection metadata and IP addresses as a service provider.
• The safety claim is limited to hiding each player's IP from the other player. It does not hide IPs from Cloudflare or Boardgammon ops.

3. What we do not collect

Boardgammon does not collect precise location, contacts, calendar, photos, videos, health data, free-form chat transcripts, or recorded audio. We do not sell personal data.

4. Retention

• Account rows, social data, push tokens, and entitlement state are retained until deletion is requested.
• Replay and fair-play audit records are retained so completed online games remain verifiable. When an account is deleted, player identity in past game history is anonymized instead of removing the audit chain.
• Diagnostics retain the provider defaults, typically 30 to 90 days.
• Short-lived auth codes are deleted on use or expiry.

5. Account deletion and data requests

Users can request deletion through the app or by contacting Boardgammon directly. This section is the public delete-account reference for app-store disclosures.

1. In the app, open Settings → Account → Delete account.
2. Confirm the deletion request from the signed-in account.
3. Or email [email protected] from the address tied to the account.

Deleted data includes the account row, linked provider subjects, push tokens, social rows, blocks, mutes, reports filed by the user, and voice metadata rows tied to the account.

Completed match audit logs are kept in anonymized form so previously played online games remain provably fair and replayable. Voice audio is never stored, so there is no audio archive to delete.

Authenticated API surfaces also exist for export and deletion: GET https://api.boardgammon.com/privacy/training-export and DELETE https://api.boardgammon.com/privacy/users/{userId}.

6. Service providers and processors

• Apple App Store and Google Play for app distribution and in-app purchases.
• RevenueCat for entitlement validation and purchase-state handling.
• Cloudflare Realtime TURN for encrypted relay-only voice media and connection metadata.
• Sentry for crash and performance telemetry.
• Firebase Analytics for aggregate usage analytics.
• AdMob for mobile ad delivery where applicable.
• Hetzner for production hosting in the EU.

7. Security and transport

Boardgammon uses HTTPS only. The production stack terminates TLS at Cloudflare and again at the origin. Voice media uses standard WebRTC DTLS-SRTP through relay-only TURN.

8. Changes to this policy

Material changes are announced in the app release notes and on this page. Minor wording and link corrections may be made without separate notice.

9. Contact

Boardgammon
Peyman Ghaderkourehpaz
[email protected]