♠ OFC MOBILE

Privacy policy

Effective October 26, 2026. OFC Mobile is operated by Jacob Gil. Questions or privacy requests: jacobgil325@gmail.com.

What we use and why

OFC is a points-only game. We use the account identifier and basic identity supplied by the sign-in provider you choose to secure your account and restore your games. Your public display name, username and approved profile photo help friends recognize you. You can use a preset avatar instead of a photo.

We store friends, invitations, table membership, private table messages, game commands and hand results to provide asynchronous games and history. Messages are visible to table members, subject to blocking and moderation. Profile photos and public names are visible to other players. We store notification device identifiers and push tokens when you enable notifications. Permissions are optional and can be changed in your device settings.

Optional contact discovery

A scan starts only when you choose to find contacts. Your phone hashes normalized contact email addresses and temporarily sends the hashes to match opted-in accounts. Hashes remain identifying data. We do not upload contact names, phone numbers or plaintext contact email addresses, create friendships automatically, or keep an address-book directory. Let contacts find me is off by default. Scan results clear when you leave Friends or background the app.

Service providers and safety

Supabase provides identity, database and legacy photo storage; Railway hosts the API and game worker; Expo provides app updates and notification delivery through Apple/Google. These services process the data needed to provide their functions. Network addresses and limited diagnostic metadata may be processed by these providers. We do not sell your data, use advertising tracking, or request access to your Gmail or Drive through game sign-in.

App update checks send Expo a persistent installation identifier together with app runtime and update identifiers; these support update delivery and installation/adoption counts. Failed update loads may also send limited error details to help diagnose update failures.

On Android, Google's Firebase Cloud Messaging and Firebase Installations also process an app installation identifier and limited device/app metadata to provide notification delivery. These SDK identifiers may be created before you enable notifications; receiving notifications still depends on your permission and in-app preferences.

Reports are visible only to authorized support reviewers and contain the reported message or public profile details, your reason and the identifiers needed to investigate. New profile photos remain private until approved. A basic text filter, reports and operator review help enforce our conduct rules; automated filtering is not exhaustive.

Retention and deletion

We keep account data while you use OFC. Request deletion in Profile → Account. Access stops immediately; the erasure process removes sign-in access, personal profile/settings, photos, social relationships, messages and notification records within 30 days. The app provides a deletion receipt so you can check completion after sign-out.

Other players retain pseudonymous shared game history and completed scores without your name or photo. Pending games end without rescoring completed hands. Closed moderation reports are retained for up to 90 days for review and then purged; personal report content is removed during account erasure. Restricted backup copies expire under the configured backup retention and are not used to restore deleted accounts to normal service. We retain information only longer where legally required.

Your choices

Edit your profile, remove a photo, disable contact discoverability, block another player, manage notifications or delete your account inside the app. Contact jacobgil325@gmail.com for access, correction, deletion or a concern about data handling. Do not send passwords, sign-in tokens or hidden cards.