Device and account data

Local matches, settings and preferences are stored on your device. Online features use a guest identity or connected account and Mesa services. Your chosen table name can be visible to participants; avoid putting private information in it.

Tables and purchases

The service processes the state needed to coordinate games, turns, participants and results. Apple handles purchases; Mesa verifies transactions and keeps benefit, coin and cosmetic records to deliver and recover content. We do not receive your complete payment-card details.

Profiles, reports and blocks

People at your tables can open your profile to see your name, equipped cosmetics and game statistics, separated into local and online results. Local results originate on the player’s device. Your profile does not show your balance, receipts or sign-in identity.

Reports store the reason, details you choose to provide, the reported name and internal references for the players and table. A copy is sent to Mesa Support for review. Block notices are sent separately and do not imply a violation. Report and notice records expire after 180 days; storage cleanup runs in the background. Support correspondence follows the retention terms below.

Blocks are linked to Mesa accounts and prevent future shared online tables while active. You can manage them in Settings. Account deletion removes profile data and report/block references from active storage; copies already sent by email are not automatically erased.

Diagnostics and providers

Infrastructure uses AWS services for identity and operations. Optional Sentry crash reports depend on consent and the published version’s configuration. They must not contain credentials, private cards or tiles, or complete purchase receipts. The app does not use behavioral advertising; this website has no analytics or collection forms.

Retention and deletion

Your local saved matches and preferences stay on your device when you delete your cloud account. Account deletion removes your active account data, wallet and owned-item records, and removes or replaces your identity in shared match history. It does not delete your Apple account or cancel an Apple subscription.

Minimal identity identifiers, deletion results and recovery hashes are retained for 180 days to support deletion recovery and prevent old credentials reopening a deleted account. We then retire the old cloud identity and retain its blocking record for a further 24 hours while issued credentials expire. Failed provider cleanup is retried; records remain protected until retirement succeeds. Storage cleanup runs in the background and may occur later than the scheduled expiry. Older records without a reliable deletion timestamp receive a 180-day period when this policy is activated.

Notification-delivery deduplication records expire 180 days after their signed event time. Online match records normally expire after seven days. Apple notification payloads can remain queued for up to four days, or fourteen days in a failure queue. Operational logs are retained for seven to thirty days. Database recovery copies can remain available for up to thirty-five days after active records are removed.

Optional crash reports are retained for up to ninety days. Support correspondence follows the support provider’s retention settings and is not automatically erased by deleting your Mesa account. Contact support@mesavenezolana.com about privacy or support correspondence.

Your controls

Review app settings, choose whether to share optional diagnostics and request account deletion. Subscription cancellation is a separate Apple control. The operator and privacy contact are listed at the end of this page.

Operator and contact

Kai Cianflone — sole proprietor of Mesa Venezolana

support@mesavenezolana.com