PokerFolio ("the app", "we", "us") helps live poker players record sessions, hands and bankroll information. This policy explains what the current Android app sends off your device, what remains local, and the choices available to you.
An account is optional. Core tracking works while signed out. Product analytics and release-build crash reporting can still send technical and app-interaction data while you are signed out.
The app stores its working database locally. It can include bankrolls, transactions, cash and tournament sessions, live-session state, venues, casinos, tags, expenses, bonuses, notes, saved poker events, spreadsheet import records, player profiles and notes, and hand histories with seats, cards and actions. App settings and a randomly generated analytics install identifier are also stored locally.
The app does not request a cloud backup unless you sign in. PokerFolio excludes its app files, preferences and databases from Android cloud backup and device-to-device transfer because they can contain sensitive financial and poker records.
The app sends product-usage events to our Supabase project. These events include event and screen names, event time, app version and build number, platform, a per-launch session identifier, and a random install UUID that persists in app preferences. Event properties can include the selected app tab, session type, poker game type, session duration, whether another session was requested, hand variant, player/action/card counts, whether a hand was linked to a live session, and replay/share format. Analytics do not intentionally include bankroll amounts, session profit, player names, notes, or card values.
If you are signed in, the analytics event also includes your Supabase user ID. If you are signed out, it does not include an account ID, but the persistent install UUID still distinguishes one app installation from another. You can disable future product analytics in More → Settings → Data.
Release builds use Google Firebase Crashlytics to report uncaught errors. Crashlytics may receive crash logs and stack traces, relevant application state, app version, device model and operating-system information, timestamps, available memory or storage information, and Crashlytics or Firebase installation identifiers. Collection is disabled in debug builds but enabled by default in release builds. You can disable future crash reporting in More → Settings → Data. Google states that Crashlytics crash data and associated identifiers are retained for 90 days before removal begins; see Firebase Privacy and Security.
When you create or use an account, Supabase handles authentication. We receive your email address, a user ID, authentication records, and, for Google sign-in, basic profile information made available by Google such as your name or profile image reference.
While signed in, the app can upload a whole-database JSON snapshot to a backup record tied to your account. This is not limited to summary totals. It can include all of the local categories listed above, including financial amounts, bankroll transactions, session details and notes, player names and notes, hole and board cards, hand actions and amounts, and imported spreadsheet rows. It also includes backup metadata such as schema version, app version and creation time. The current database snapshot excludes only the app's bundled currency-rate table and local player-avatar image files.
Supabase Row-Level Security is configured so signed-in app users can access only their own backup. The app keeps one current backup plus up to ten recent revisions for conflict recovery. Backup writes use server timestamps and revision checks so an older device cannot silently overwrite a newer backup.
If you are signed in and choose screenshot import, the selected screenshot is sent through a Supabase Edge Function to the Google Gemini API. Gemini processes the image to extract structured hand information. The current mobile path sends the image as part of the request and does not save the original screenshot to PokerFolio's cloud storage bucket. Google may handle prompts, images and responses under the Gemini API terms and the billing and data-use settings of our API account; see Gemini API Terms.
After you review and save an imported hand while signed in, the app also sends a normalized copy to Supabase cloud tables. Those rows can include the hand time, related casino or session ID, poker site and site hand ID, game and stakes, blinds and antes, pot, result, winners, rake and notes, seat positions and stacks, hole and board cards, and action sequences and amounts. They are separate from the single whole-database backup record. The normalized cloud rows do not contain the original screenshot.
If you choose to send a support message in the app, we store the message, any contact email you enter, your account email if you are signed in, app version, platform, and the product language you were reading at the time so we can reply in it. If you select attachments, the current app sends the attachment file name, MIME type and file size, but not the file contents. The selected file bytes are read temporarily on the device while you compose the message. Do not include passwords, private keys, or information you do not want included in the support record.
We do not sell your data and do not use it for advertising. Supabase hosts authentication, backups, normalized hand rows, analytics and support data on our behalf. Google provides sign-in, Firebase Crashlytics, and Gemini screenshot processing. These providers process data under their applicable terms. Data is sent over encrypted HTTPS connections.
Full account-deletion instructions are on our account and data deletion page.
The app is intended for adults of legal gambling age and is not directed at children.
If this policy changes, the updated version will be posted here with a new "last updated" date.
Questions or deletion requests: mayureshmhase.work@gmail.com.