Privacy Policy

Section 01

Overview

PokerSharp is a mobile poker training application ("the App") designed to help players develop Game Theory Optimal (GTO) intuition for No-Limit Texas Hold'em. The App is developed and published by Your Custom Web Design Inc. ("we," "us," or "our").

The App is built so that you do not need an account. Without one, your hand history and settings stay on your device and are never transmitted to us. You can optionally create a PokerSharp account by signing in with Google; the account stores your hands, settings, bankroll and chips on our servers so they follow you to another device (Section 06). Beyond that, the exceptions are usage events, which are summaries of what you did, never the records themselves, and the questions you choose to ask the in-app coach, which carry a summary of that one hand (both in Section 07), and a hand you choose to share, which is published at its own link (Section 08). The App's training features work fully offline.

Eight narrow categories of data can leave your device, each described in its own section of this policy:

Advertising signals: the free version displays ads served by Google AdMob; the AdMob SDK communicates with Google's servers when your device is online (Section 03).
Purchase validation: if you buy PokerSharp Pro (a one-time purchase, not a subscription), the purchase is billed by Google Play or the Apple App Store and validated through RevenueCat, a purchase-management service. When you are signed in to a PokerSharp account, RevenueCat is told your account id (Section 04).
Voluntary bug reports: if you explicitly choose to send a bug report from within the App, that report is transmitted to a reporting endpoint we operate (Section 05). This endpoint receives a bug report only when you press send, and the usage data described in Section 07 only while that switch is on. Coach questions (below), hands you choose to share (below) and the optional PokerSharp account (next) are served by the same Cloudflare-hosted service.
Optional PokerSharp account: if you sign in with Google, we store your Google account id and email address, and your synced hands, settings, bankroll and chips, in a database we operate on Cloudflare. Nothing is sent unless you sign in (Section 06 and Section 15).
One-time Google Drive import: if you used the former Google Drive backup, the App can, once and only if you agree, read that backup from your own Google Drive and copy it into your account (Section 06).
Usage data: while the App is in development it records which modes you use and how long decisions take, under a random install identifier with no personal information in it, and may occasionally ask you one short question. You can switch this off in Settings (Section 07).
Ask the Coach: if you choose to ask the in-app coach about a hand, your question, a summary of that hand and the earlier turns of that conversation are sent through our endpoint to a third-party AI provider, which writes the reply. This happens only when you send a question (Section 07).
Hands you choose to share: if you tap Share, Copy link or Save image in the share preview for a Live hand, that one hand and two picture cards of it are uploaded to our endpoint and published at a link that anyone who has it can open. Nothing is sent until you tap Share (Section 08).

This Privacy Policy explains precisely what data the App stores locally, what data each of those eight channels transmits, and what we do (and do not do) with any of it.

By installing and using PokerSharp, you agree to the practices described in this policy. If you do not agree with any part of this policy, please discontinue use of the App.

Section 02

Data We Collect and Store

The App stores the following data locally on your device, using Android's and iOS's standard on-device storage APIs (React Native AsyncStorage and SQLite). Signed out, none of this data is transmitted to us, except a single hand you choose to share (Section 08). If you sign in to a PokerSharp account, some of it is also stored in your account on our servers (Section 06). For the separate, narrower categories of data that can be transmitted, see Sections 03–08.

Apart from the PokerSharp account row above, the data listed contains no personally identifiable information (PII): no name, phone number or location is collected, inferred or stored. If you sign in, your email address and Google account id are personal information and are stored as described in Section 06. The optional display name you may type for a hand you share is published with that hand only (Section 08); a nickname works just as well as your real name.

Section 03

Advertising and AdMob

The free version of PokerSharp is supported by advertising. We use Google AdMob, Google's mobile advertising platform, to serve banner ads and (optionally) opt-in rewarded ads within the App. We do not operate any other advertising network, mediation layer, or attribution SDK.

What Google AdMob Accesses

To serve ads, the AdMob SDK embedded in the App may access the following device-level signals and transmit them to Google when your device has an internet connection:

Personalized vs. Non-Personalized Ads

Where required by law (the European Economic Area, the United Kingdom, California, and several other US states), the App presents a Google-provided consent form on first launch via the Google User Messaging Platform ("UMP"). Your choice on that form determines whether you see personalized ads (selected based on your inferred interests) or non-personalized ads (selected only based on context and approximate location). Either way, the App continues to function fully.

Outside those jurisdictions the App defaults to serving personalized ads consistent with Google's standard AdMob behavior. You can change this preference at any time from the "Ad privacy options" link in the App's Settings, which re-opens the same Google-provided form.

Opting Out at the Device Level

Independent of the in-App consent flow, you can reset or limit ad tracking at the operating-system level:

Android: Settings → Google → Ads → Delete advertising ID (or, on older devices, Opt out of Ads Personalization).
iOS: Settings → Privacy & Security → Tracking → toggle off Allow Apps to Request to Track, and / or revoke tracking permission for PokerSharp specifically.

Resetting or deleting your advertising ID prevents AdMob from associating future ad interactions with prior ones, severing the strongest signal used for personalization. The App will continue to show ads but they will be non-personalized.

Rewarded Ads

In addition to passive banner ads, the App offers optional rewarded ads: short video ads you can choose to watch in exchange for in-App chips (the free version's hand meter) or, once a day, five extra Ask the Coach questions for that day. Rewarded ads are opt-in: you tap a button to start one. The same AdMob data-flow described above applies; no additional data is collected for rewarded ads beyond what AdMob accesses for banner ads.

Section 04

Pro Purchases and RevenueCat

The App offers an optional one-time purchase, PokerSharp Pro, which removes advertising and the chip meter and unlocks additional study features. Payment itself is handled entirely by the platform you bought the App from: Google Play on Android or the Apple App Store on iOS. We never receive, store, or process your name, billing address, or payment card details; those stay with Google or Apple under their own privacy policies.

To validate purchases and keep track of whether a given installation is entitled to Pro, the App uses RevenueCat, a third-party purchase-management service. When the App starts (and when a purchase or restore occurs), the RevenueCat SDK communicates with RevenueCat's servers and transmits:

If you never purchase Pro, the RevenueCat SDK still performs a lightweight entitlement check (the identifier and basic device context above) so the App knows whether to show ads. No purchase data exists in that case because there is no purchase.

Your training data (hand history, decisions, accuracy, settings) is never sent to RevenueCat, Google, or Apple. Purchase validation is completely separate from your training activity.

Section 05

Voluntary Bug Reports

The App includes a built-in bug-reporting tool. It can be opened by shaking your device, from Settings → Support → "Report a Bug," or via a prompt after you take an OS screenshot inside the App. If the App crashes, it shows a screen offering to send a crash report, which carries the error message and technical details in place of a screenshot and goes only if you tap send (if it cannot be sent at that moment, the App retries it the next time you open the App). A bug report is sent only when you review it and explicitly tap send. The automatic exceptions are the small background error reports described in Section 07. It is part of the usage data, carries no screenshot, and stops when you turn that switch off.

When you choose to send a bug report, the following is transmitted over an encrypted connection (HTTPS) to a reporting endpoint that we operate:

A screenshot of the App screen as it looked when you triggered the report;
The description you type, if any;
Technical context: the screen you were on and its state (for example the game mode and the hand on screen), app version, device make and model, operating system version, basic hardware and display details, language and time zone;
A summary of your last five training hands (the mode, positions, hole cards, scenario and whether your answer matched GTO), so we can reproduce the problem;
Your install identifier (Section 07), so a report can be matched to that phone's usage data.

Bug reports are used for exactly one purpose: diagnosing and fixing the problem you reported. They are not used for advertising, analytics, or profiling; they carry no name or email address (unless you type one into the description); and they are not shared with any third party other than the service providers that store them for us. Each report is filed as an issue in a private GitHub repository that only we can access, and its screenshot is stored on Cloudflare at a long, random, unlisted address that the issue links to, so anyone who obtained that address could open the image. While you are signed in, the install identifier in a report is also stored with your account's sign-in session (Section 06), so a report from that phone could be associated with your account, and a screenshot of the Settings account card shows the email address you are signed in with. Reports are retained only as long as needed to investigate and resolve the issue, then deleted.

Section 06

PokerSharp Accounts and Sync

PokerSharp accounts exist and are optional. You can use every training feature without one. If you choose to sign in (on the welcome screen the first time you open the App, or later in Settings → Account → Sign in with Google), the App keeps your hand history, settings, bankroll and chips in your account, so they carry across devices. Until you sign in, nothing in this section applies and nothing is sent.

What We Store, and Where

Your Google account id and email address: Google's sign-in gives us a stable Google account identifier (the "sub") and your email address. We store both, and refresh the email each time you sign in. We do not receive your Google password. We use the email to identify your account when you ask for deletion or support, and for nothing else;
An internal account id: a random identifier we generate for your account. It is never your Google id or email;
Synced hands: the hand-history records described in Section 02, compressed on your phone before upload;
Settings: the gameplay, display and sound settings that follow you between devices;
Bankroll: your bankroll sessions and spots;
Chips: your chip balance, daily-bonus streak and last-claim time, the day's ad-reward counts, and a record of your chip changes (spends, refunds, ad and bonus rewards), kept while the account exists. The server keeps these so that it can enforce the daily limits itself and apply each reward or refund exactly once;
One sign-in session per device: a sign-in token for each phone you are signed in on, stored by us only as a one-way hash together with that phone's install identifier and its sign-in and last-use times. On your phone the token is kept in the operating system's secure storage.

All of this is stored in a database we operate on Cloudflare, over encrypted connections (HTTPS). The database is located in western North America. We do not store your Google sign-in token. A sign-in session ends after 180 days without use, and an account keeps at most 10 sessions (the oldest is ended first). We also keep short-lived counters (deleted after about three days) that count failed sign-in attempts per network address, to limit abuse.

Your Pro purchase is not stored in your account. It stays with Google Play and RevenueCat (Section 04), which is told your account id while you are signed in.

How Long We Keep It

We keep your account data until you delete your account. An account with no sign-in and no sync for 24 months is deleted automatically, by the same process as a deletion you request. An account holds up to 100,000 hands; beyond that, new hands stay on your phone only.

Deleting Your Account

You can delete your account in the App under Settings → Account → Delete account. The confirmation offers an extra, unticked option to also clear this phone's hand history and bankroll. You can also delete it without the App at api.pokersharpgto.com/account/delete by signing in with the same Google account (that page uses Google's sign-in button, which your browser loads from Google). Deletion takes effect for sign-in immediately: every session ends and a new sign-in starts a fresh, empty account. The stored data is then removed in the background, which normally finishes within minutes and can take longer for a very large account.

Deletion removes your account record and Google identity, your synced hands, settings, bankroll and chips, the Ask the Coach history and the shared hands you made while signed in, and the customer record held for your account id at RevenueCat. What survives deletion: the usage events and survey answers (Section 07), which carry no account id (the install identifier in them may match one that was stored with your account's sign-in session, which is deleted with the account); your Pro purchase, which stays with Google Play; coach conversations and shared hands you made while signed out, which were never linked to your account and are deleted when they expire on their own schedules (Section 07 and Section 08); and daily usage counters (for example the coach's daily question allowance), which carry no account. Data saved only on your phone stays there unless you tick the option to clear it.

Signing Out and Switching Accounts

Signing out keeps your hands on the phone and in your account; chips stay with the account, so the phone starts at 0 chips until you sign back in. If you later sign in to a different account on the same phone, the App asks once whether to add this phone's existing data to that account.

The Former Google Drive Backup

Google Drive sync has been removed from the App. Earlier versions could back up to a hidden app-private folder in your own Google Drive, without any PokerSharp server. If you used it, after you sign in the App can offer a one-time import. If you agree, Google asks you to allow the narrow Drive permission (drive.appdata, which reaches only PokerSharp's own hidden folder and nothing else in your Drive), and the App reads that backup directly from your Drive on your phone and uploads its hands, settings and bankroll into your account. After a successful import the App offers to delete the Drive copy; if you keep it, it stays in your Drive under your Google account. The import does not revoke the Drive permission. Deleting your account in the App revokes the App's access to your Google account, including this permission; you can also revoke it yourself at myaccount.google.com/permissions. Data read from Google Drive is used only for this import.

The Export and Restore tools in Settings → Data work without an account and create files that stay with you.

Section 07

Usage Data (First-Party)

While PokerSharp is in development, the App records usage data and sends it to a reporting endpoint we operate, so that we can see which modes people actually use, how long decisions take, and how the free version feels in practice. This is our own small pipeline, not a third-party analytics SDK: no Firebase, no Mixpanel, no Amplitude, no Segment, and no behavioral advertising platform is integrated (Section 09).

You can turn this off at any time in the App under Settings → Privacy → Share play stats. The App shows a one-time notice explaining this the first time you reach the main menu. Turning the switch off stops all recording immediately. Events already recorded before that moment are sent, ending with a one-line record that you opted out; if they cannot be sent right away (for example while you are offline), the App retries on later launches for up to 30 days and then discards them. After that, the App does not contact the endpoint for usage data at all. The setting is per device and is deliberately not synced to your account, so switching it off on one device never silently switches it on somewhere else.

What is in it

Each event carries an random install identifier (a random string generated on first launch, not derived from your device or from you), a per-launch session identifier, your app version, platform, OS version, device make and model, basic hardware details (device type, memory size, processor type), screen size and system text size, language and time zone, and the event itself. Typical events are: the app opening and going to the background, which screen you are on and for how long, a training hand being dealt and answered (the scenario, the cards in standard poker notation, the action you took, whether it matched GTO, and how many seconds you took), a Live hand playing out, in-app chip spends and grants, ad events, paywall views and outcomes, settings changes, whether you are signed in to a PokerSharp account and when you sign in, sign out or delete it (and how many hands a Google Drive import copied), Ask the Coach use (when you open it, how long answers take, your tier, error codes, thumbs ratings and bonus questions, never the question or answer text), short survey answers, crashes (the error type and a shortened, redacted message), and the steps of sharing a hand (opening the share preview, sending, whether the upload worked, which app you picked if your phone reports it, opening a shared link in the App, and a first launch that came from a shared link, recorded with that link's code). These sharing events never carry your display name or the caption, and like every other usage event they stop when you turn the switch off.

The events themselves do not identify you. There is no name, no email address, no phone number, no postal or IP-derived location stored by us, no advertising identifier, and no PokerSharp account id or email in the events themselves. One link does exist while you are signed in: your install identifier is stored with your account's sign-in session on our server (Section 06), so usage data from that phone could be associated with your account. This happens whether or not the Share play stats switch is on, because the sign-in session carries the identifier either way (Section 15). The install identifier is shown to you in Settings → About → Install ID so that you can quote it if you ever want your data deleted.

Automatic error reports

While this switch is on, the App may also send a small automatic error report when something goes wrong in the background (an error that did not crash the App and that you may never have noticed). It contains the error message and stack trace, the screen you were on, the app version, device model and operating system version, the install identifier, and a summary of the last five training hands. No screenshot is taken and no description is asked for, and at most three such reports are sent per launch. Likewise, when Ask the Coach fails for a reason you did not cause, the App sends a short automatic report with the error code and timings, the same technical details, the install identifier and the last-five-hands summary, but never your question, the answer or the hand you asked about; at most five are sent per launch. Like bug reports, these reports are filed in our private GitHub repository (Section 05). Turning the switch off stops them too. A bug report you send yourself from the bug-reporting tool (Section 05) is separate and unaffected.

Short in-app questions

From time to time the App may show a single-question card, for example asking what you would pay for PokerSharp Pro or how the free version feels. Answering is optional, skipping is one tap, and a question is asked at most once. Some questions offer an optional comment box. Anything you type there is stored as you typed it, after the App removes email addresses and phone numbers it can recognise, and after trimming it to 280 characters. Please do not include your name or any other personal detail in that box; the card says so too.

Coach conversations

The App has an optional Ask the Coach feature, shown after you finish a hand or when you view your stats. Nothing is sent until you type or tap a question and press send. When you do, the App sends the question, a text summary of the hand or the stats you are asking about (the cards, positions, bet sizes and the solver's recommendation, not your hand history as a whole), and the earlier turns of that conversation. They are sent over HTTPS to the endpoint we operate, which forwards them to a third-party AI provider acting as our processor, so that its model can write the reply. The question itself carries no name or email. If you are signed in, the App also sends your sign-in token so that we can tell whether your account has Pro and can tag that conversation with a one-way hash of your account id, which is how deleting your account removes it (Section 06); signed out, nothing links the conversation to an account, and the App instead sends the RevenueCat identifier (Section 04) so that our endpoint can check with RevenueCat whether you have Pro. On Android, the App also asks Google Play Integrity for a token that our endpoint checks with Google, to confirm the question comes from a genuine copy of the App; we keep only the resulting verdict label. Please do not type personal details into a question.

Unless you have turned off Share play stats, we keep each question and answer for 90 days, stored against a one-way hash of your random install identifier (and, for Pro, a hash of the purchase identifier) rather than the identifier itself, so that we can check the quality of the answers and improve the coach. They are never used for advertising. If you turn the switch off, the App asks the endpoint to delete everything already logged for your install (except an answer you reported, below), and new questions are no longer logged. The coach and its follow-up questions still work with the switch off: your conversation is held for 24 hours, sliding forward while you keep using it, so a follow-up can refer to the earlier turns, and is then deleted. If you use Report this answer, or give an answer a thumbs-down with a note you type, that one question and answer (and your note) are kept for at least 30 days, even with the switch off, so that we can review the report. A reported answer is also filed, with your note, as an issue in our private GitHub repository (Section 05); its text is removed from the issue when the stored copy expires. To have coach data deleted sooner, contact us with your install identifier (Section 17).

Where it goes and how long it is kept

Events are sent over HTTPS, in batches, to the same endpoint that receives voluntary bug reports (Section 05), and are stored in a database we operate on Cloudflare. They are not shared with, sold to, or accessible by any third party, and they are never used for advertising or ad targeting. We keep them while the App is in active development and delete them when they are no longer useful for that purpose. You can have your data deleted at any time by contacting us with your install identifier (Section 17).

Section 08

Hands You Choose to Share

After a Live hand, and on that hand's review screen in your hand history, the App offers a Share button. It opens a share preview showing the picture card, the caption and an optional display name. Nothing leaves your device until you tap Share, Copy link or Save image in that preview. Opening the share preview makes one empty request to our endpoint to prepare the connection; no hand is sent with it. When you do, the App uploads that one hand over HTTPS to the endpoint we operate (Section 05), which stores it and publishes it at a short link. The App then passes the picture, the caption and the link to your phone's own share menu, and the app you pick there (a messenger, for example) handles them under its own privacy policy.

What is sent

The hand itself: the table size, your position, your hole cards, the board, each player's actions with bet sizes in big blinds, the pot and your result in big blinds, and, if the hand reached showdown, the opponent's shown cards and the names of the made hands;
Your display name, only if you typed one in the preview and left it switched on. It is checked against a list of offensive words, kept on your device for next time, never synced to your account, and never included in usage data;
Two picture cards of the hand: the image you share and a wider version that messaging apps show as the link preview;
Technical context: your app version, the link's random code, and your random install identifier (Section 07), which our endpoint turns into a salted one-way hash on arrival; the identifier itself is not stored.

Nothing else from your hand history is sent: no other hands, no timestamps from your device, no session details, and no GTO grades. We record when the hand was shared. The opponents are the App's computer players, so no other person's data is involved, and every amount is in big blinds of practice chips, never money.

Who can see it

Anyone who has the link can see the shared hand: the picture card, a written recap of the hand, and your display name if you added one. The link works like an unlisted address. Its code is random, the page asks search engines not to index it, and we publish no list of shared hands, but anyone you send it to can pass it on, and apps that show link previews fetch the preview picture when the link is posted. Share only what you are happy for anyone to see, and use a nickname if you would rather not show your real name. If you already have the App and open a shared link, the App downloads that hand from the same endpoint to show it; that request carries nothing from your own hand history.

The install hash

With each shared hand we store a salted one-way hash of your random install identifier, used only to limit spam (a cap on how many hands one install can share each day) and to let the same install finish an upload that was interrupted. Daily counters also keep a salted hash of the IP address an upload came from, for the same purpose; those counters are deleted after three days. These hashes are never shown on the page or to anyone else, are used only for the spam caps and for finishing an interrupted upload, and we do not use them to link a shared hand to your usage data (Section 07) or to anything else about you. This does not depend on the Share play stats switch: sharing is something you do on purpose with its own tap, so it works with that switch off and the hash is stored either way. The separate usage events about sharing (Section 07) do follow the switch.

How long it is kept and how to delete it

A shared hand, its two pictures and its stored hash are kept for one year and then deleted; after that the link shows a general PokerSharp page instead. To have a shared hand removed sooner, email its link to support@ycwdesign.com, or use the Report this hand link at the bottom of the shared page, and we will delete it (Section 17). You can also delete it yourself in the app under Settings, Data, Shared hands (for shares made on that phone); copies already saved or forwarded by others cannot be recalled. A hand shared while you are signed in is tagged with a one-way hash of your account id and is deleted when you delete your account; a hand shared while signed out is not linked to any account, so the link is the only way to tell which hand is yours. Keep the link if you may want the hand removed later.

Install referrer

On Android, the App reads the Google Play install referrer once, on its first launch after installation (or on the next launch if Google Play did not answer in time). The referrer is a short label Google Play hands to a newly installed app describing the link that led to the install. If that link was a shared hand's link, the App records an usage event carrying the link's code, so that we can count how many installs shared links bring in (Section 07). The referrer contains nothing about you, and that event follows the usage-data switch like every other usage event.

Counting on the shared pages

The shared-hand pages count, on our own server, how often they are viewed (counted from a sample of views) and how often their install buttons are tapped. These are plain totals per shared hand and per day. The pages set no cookies, run no scripts and no third-party analytics, and the counts are not tied to any identifier of the visitor; link-preview robots are left out. Unlike the rest of our website, the pages load the "Outfit" typeface from our own server, not from Google Fonts (Section 20).

Section 09

Data We Do Not Collect

The eight narrow channels described above are AdMob ad-serving signals (Section 03), RevenueCat purchase validation (Section 04), bug reports you explicitly send (Section 05), the optional PokerSharp account, including the Google Sign-In exchange with Google (Section 06), the one-time Google Drive import (Section 06), usage data you can switch off (Section 07), the questions you choose to ask the in-app coach (Section 07), and the hands you choose to share (Section 08). Setting those aside, the following categories of data are not collected, stored, transmitted, or processed by PokerSharp under any circumstances:

Personal & Identity Information

Unless you choose to sign in, the App does not collect names, email addresses, phone numbers, usernames, profile photos, dates of birth, or any other personal identifiers, and no account is required. If you sign in with Google, we store your Google account id and email address (Section 06); we do not collect your phone number or date of birth. The only name that can ever leave your device is the optional display name you may type yourself on a hand you share, which is published with that hand (Section 08).

Device & Hardware Identifiers

We do not access, read, or transmit hardware or software identifiers: IMEI, IMSI, MAC address, Android ID, serial number, or any similar device fingerprint. The only device-level identifiers the App handles are the operating system's advertising ID (accessed only by the Google AdMob SDK, Section 03) and the random ID used for the Pro entitlement (used only by the RevenueCat SDK, Section 04; your PokerSharp account id when you are signed in). We do not receive the advertising ID. You can reset or delete the advertising ID at any time from your device's privacy settings; see Section 03 for instructions.

Precise Location Data

The App does not request, access, or store your precise geographic location. No GPS permission is requested at installation or during use. Google AdMob may infer an approximate region from your IP address for the purpose of ad targeting and legal compliance (see Section 03); that inference happens on Google's side, not ours.

Usage Analytics & Telemetry

The App does not include any third-party analytics SDK such as Firebase Analytics, Mixpanel, Amplitude, Segment, or similar. No crash reporting service, performance monitoring tool, or behavioral analytics platform is integrated, and no usage data of any kind is shared with an advertising network. What the App does record is our own usage data, described in full in Section 07, which you can switch off in Settings. The AdMob SDK measures only ad-related events (impressions, clicks, video completions), not in-App training behavior, and the RevenueCat SDK records only purchase and entitlement events, not training behavior.

Financial & Payment Information

No payment card numbers, billing addresses, or bank details are ever collected, received, or handled by the App or by us. Purchases of PokerSharp Pro are processed entirely by Google Play or the Apple App Store on their own payment infrastructure. What we can see, via RevenueCat, is purchase status: that an installation holds an active Pro entitlement for a given product. Signed out, that is never who you are; signed in, the entitlement is held under your account id, which we can associate with your account's email. We never see how you paid. See Section 04.

Network Communications

The App's outbound network traffic is limited to exactly eight channels: the AdMob SDK's communication with Google's ad-serving infrastructure (Section 03), the RevenueCat SDK's purchase-validation calls (Section 04), bug reports you explicitly choose to send (Section 05), your PokerSharp account's communication with our servers if you have signed in, including the Google Sign-In exchange with Google's account servers (Section 06), the one-time read of your own Google Drive backup if you agree to the import (Section 06), the usage batches described in Section 07, which stop entirely once you switch that setting off, and the coach questions you choose to send, which go to the endpoint we operate and from there to a third-party AI provider's model API, together with the Google Play Integrity check on Android (Section 07), and the hands you choose to share, which go to the same endpoint, together with the App downloading a shared hand when you open its link (Section 08). Our servers are the Cloudflare-hosted service reached at the addresses used for these features, including api.pokersharpgto.com. We operate no other server, API endpoint, content delivery network, or remote service that the App contacts. With your device offline, the App's training features (drills, range charts, hand history, analytics) function normally; only the ad slots remain blank.

Section 10

How Local Storage Works

PokerSharp stores data in two on-device stores: a SQLite database (your hand history records) and React Native AsyncStorage (settings and preferences), which maps to the platform's native key-value storage: SharedPreferences on Android and NSUserDefaults / SQLite on iOS. Both stores are sandboxed to the App by the operating system.

This means:

Other apps on your device cannot read PokerSharp's stored data. The operating system enforces this isolation. Data stored by the App is not included in any cloud backup service unless you have explicitly enabled full-device encrypted backup through your platform's backup settings (Google One on Android; iCloud Backup on iOS), and in that case the data is controlled by you, not by us. Separately, if you sign in to a PokerSharp account, the synced copy held in your account is held by us (Section 06).

We have no access to the data stored locally on your device, regardless of how it is backed up; the only copies we hold are what you chose to sync to an account or share. If you restore a device from a backup that includes PokerSharp's data, that data will reappear on your device, and if you are signed in it syncs with your account as usual.

Section 11

Third-Party Service Providers

We engage the following third-party service providers in connection with the App:

Google AdMob, which serves advertisements as described in Section 03. The narrow set of device signals AdMob accesses (advertising ID, approximate region inferred from IP, device and connection information, ad interactions) flows directly from your device to Google. We do not receive that data; Google handles it under its own privacy policy.

RevenueCat, which validates PokerSharp Pro purchases and tracks the Pro entitlement as described in Section 04. RevenueCat receives an installation identifier (or, when you are signed in, your PokerSharp account id) and store receipt data, acting as our processor under its own privacy policy.

Anthropic, which writes the replies in Ask the Coach as described in Section 07. Anthropic receives the questions you send, a summary of the hand or stats you asked about and the earlier turns of that conversation, from our endpoint and not from your device directly, and no name or email address. It acts as our processor and, by default, does not use that content to train its models; it handles the data under its own privacy policy.

Cloudflare hosts the service that receives bug reports, usage data, coach questions, shared hands and PokerSharp account data (Section 06), acting as our hosting and infrastructure provider under its own privacy policy.

GitHub stores the bug reports, automatic error reports and reported coach answers that our endpoint files as issues in a private repository only we can access (Section 05 and Section 07), acting as our service provider under its own privacy statement.

A note on Google: signing in uses Google Sign-In, which gives us your Google account id and email address (Section 06). The one-time Google Drive import reads your own Drive backup directly from your phone; Google acts as your storage provider under your agreement with Google, and that data does not pass through us until the App uploads it to your account.

Beyond these providers (and the endpoint we ourselves operate, Section 05), we do not share, sell, license, rent, trade, or otherwise disclose any data related to your use of PokerSharp to any third party. The App does not integrate with any social platform and does not embed any other third-party SDK that independently collects or transmits data. When you share a hand (Section 08), the App passes the picture, caption and link to your phone's own share menu; the app you pick there receives them from you, under its own privacy policy, and we send nothing to it ourselves. There are no data-broker relationships and no joint-venture data arrangements.

Specifically, your training data (hand history, decisions, settings, accuracy metrics) is never accessible to RevenueCat or to Google's advertising systems, and is accessible to us only as the account data you chose to sync. Apart from the summary of one hand that goes to the coach when you ask about it (Section 07) and a hand you choose to share (Section 08), it leaves your device only if you sign in to a PokerSharp account, in which case it is stored in your account on our servers (Section 06), and it is never shared with RevenueCat, advertisers or other third parties.

Section 12

We Do Not Sell Your Data

We do not sell, rent, license, or trade your personal information to any third party for monetary consideration. We have no data-broker relationships. We do not run an analytics partnership, a list-rental program, or any other arrangement under which information about you would be transferred to a buyer.

The California Consumer Privacy Act (CCPA) and similar state privacy laws define "selling" and "sharing" broadly enough that targeted advertising can, depending on jurisdiction and interpretation, fall within the scope of those terms. In the interest of transparency:

If you have consented to personalized ads through the Google UMP form (see Section 03), the AdMob SDK transmits your advertising ID and the other signals listed in Section 03 to Google so that Google can deliver personalized ads on our behalf. Some US state privacy frameworks treat this transmission as "sharing for cross-context behavioral advertising," and California users in particular have the right to opt out under CCPA's "Do Not Sell or Share My Personal Information" provision.

To exercise that opt-out, open the App, go to Settings, and tap "Ad privacy options" to re-open the Google consent form and switch to non-personalized ads. You can also reset or delete your advertising ID at the device level per the instructions in Section 03. Either action stops the signals from being used for personalization.

The Pro entitlement data handled by RevenueCat (Section 04) is processed solely to deliver the service you purchased: it is not sold, shared for advertising, or used for any cross-context behavioral purpose.

No training data (your hand history, decisions, accuracy, or settings) is sold, shared, or monetized in any way. That data stays on your device (or, if you sign in, in your account on our servers, see Section 06), and is never sold. A hand you choose to share is published at its link for anyone to see (Section 08), but it is never sold or used for advertising either.

Section 13

Law Enforcement and Legal Disclosures

From time to time, governments, courts, or law enforcement agencies may request that software developers disclose user data in connection with legal proceedings or investigations. We want to be transparent about how such requests would be handled in relation to PokerSharp.

Unless you sign in, we hold no user-attributable information: your training history and settings exist only on your device. If you sign in to a PokerSharp account, we hold that account's data (Section 06), including the email address and Google account id, and a legal demand could reach it. In addition, a demand directed at us could yield transient bug reports (which carry no name and are deleted after resolution, but which can be associated with your account while you are signed in, as described in Section 05), the usage events described in Section 07, which are keyed to a random install identifier rather than to a person (while you are signed in, that identifier is also stored with your account's sign-in session, so the two could be associated), and the hands you have chosen to share (Section 08), which are already public at their links and are stored only with a salted hash of that install identifier and any display name you typed. Without an account, there is no identity for us to provide.

The advertising signals transmitted from your device to Google via the AdMob SDK (see Section 03) are held by Google, and the purchase records handled by RevenueCat (see Section 04) are held by RevenueCat and the app-store platforms, not by us. A Google Drive backup you made earlier lives in your own Drive, held by Google under your account. Any legal request concerning that data would need to be directed to those companies rather than to us.

In the event we are ever required by law to disclose information, we would comply with applicable legal obligations to the extent of what we hold. We would not proactively volunteer information about users, and we would take reasonable steps to notify affected users of any legal request to the extent permitted by law.

Section 14

Business Transactions

In the event that PokerSharp or its parent business is involved in a merger, acquisition, asset sale, or similar corporate transaction, users will be notified of any change in ownership or control via a notice on this page or within the App itself, prior to any such change taking effect.

We hold no user records beyond PokerSharp accounts (Section 06), bug reports (Section 05), the usage data and coach conversations (Section 07) and the hands you choose to share, with any display name you added to them (Section 08). In such a transaction, those would transfer only under the commitments in this policy. The privacy commitments in this document would be represented to any acquirer as binding obligations carried forward with the App.

Section 15

Accounts and Sign-In

PokerSharp does not require you to create an account or sign in to use any feature of the App. There is no registration form, no email verification and no password: the only way to create a PokerSharp account is Sign in with Google, offered on the welcome screen the first time you open the App (where you can also continue without an account) and at any time in Settings → Account. Each Sign in with Google button notes that by signing in you agree to this Privacy Policy. Signing in creates an account identified by your Google account id; Google handles your Google credentials, and we never see your Google password.

What the account holds, where it is stored, how long it is kept and how to delete it are in Section 06. In short: your Google account id and email, your synced hands, settings, bankroll and chips, and one sign-in session per device, in a database we operate on Cloudflare; kept until you delete the account, or deleted after 24 months with no sign-in or sync; deletable in the App under Settings → Account → Delete account, or at api.pokersharpgto.com/account/delete.

Signed out, there is no profile data associated with you: your training history, preferences and progress are stored on your device and are associated with the App installation, not with any named identity. The usage data (Section 07) carries no account id, but while you are signed in your install identifier is stored with your account's sign-in session, so usage data from that phone could be associated with your account. PokerSharp Pro works with or without an account: entitlement is tracked against an anonymous random identifier, or against your account id when you are signed in (Section 04), and can be restored on a new device through your Google Play or App Store account using the "Restore purchases" option; signed out, the store, not us, knows who made the purchase.

If you uninstall and reinstall the App without an account, your local training data is cleared and there is no way to recover it, because it was never stored outside your device. If you were signed in, signing in again restores your hands, settings, bankroll and chips from your account.

Section 16

Children's Privacy

PokerSharp is rated for users aged 18 and older, consistent with its classification as a simulated gambling application under Apple App Store Guideline 5.3 and the Google Play IARC rating system. The App is not directed at children under the age of 13 (or under 16 in the European Economic Area), and we do not knowingly market it to or knowingly collect information from anyone under those ages.

The App is distributed under an 18+ age rating on both stores, so the store's own age gating applies before download, and the App itself carries a standing 18-and-over notice in Settings → About. By installing and using the App, you represent that you meet the minimum age requirement.

Because the App is not directed at children, Google AdMob serves ads in this App as a non-child-directed integration; AdMob's targeting therefore does not apply child-specific COPPA / GDPR-K protections by default. If you believe a person under the applicable minimum age is using the App, please contact us at the address below and we will investigate; we will also take reasonable steps to disable any such installation and ensure that AdMob's data flow is severed for that device (for example, by guiding the parent or guardian through resetting or deleting the advertising ID).

Section 17

Your Rights and Data Deletion

Accessing Your Data

All training data generated by your use of the App is accessible to you directly within the App itself. Your hand history, session analytics, and settings are visible in the Hand History screen and the Settings panel at any time. Signed out, we have no copy of this data on our side. If you are signed in, your account holds a synced copy (Section 06); you can save your own file with the Export tool in Settings → Data, and you can email us at the address below to ask what we store about your account. A hand you chose to share is visible to you at its link (Section 08).

Deleting Your Training Data

Because all training data is stored locally on your device, you have complete control over it. You can delete it by:

Clearing the App's storage through your device's system settings (Settings → Apps → PokerSharp → Storage → Clear Data on Android; or equivalent on iOS), or by uninstalling the App entirely. Either action permanently removes all locally stored data. Unless you signed in to a PokerSharp account or shared a hand, there is no remote copy to request deletion of, because none was ever created. If you signed in, clearing your phone does not remove the copy in your account; see the next heading.

Deleting Your PokerSharp Account

If you signed in to a PokerSharp account (Section 06), you can delete it yourself at any time: in the App via Settings → Account → Delete account (with an optional, unticked box to also clear this phone's hand history and bankroll), or without the App at https://api.pokersharpgto.com/account/delete by signing in with your Google account. Deletion removes your account, Google identity, synced hands, settings, bankroll and chips, the Ask the Coach history and shared hands you made while signed in, and your RevenueCat customer record. It does not remove usage data and survey answers, your Pro purchase at Google Play, coach conversations and shared hands made while signed out (they expire on their own), or usage counters; see Section 06. An account with no sign-in or sync for 24 months is deleted automatically.

If you used the former Google Drive backup, the copy in your own Drive is yours to remove: the App offers to delete it after the one-time import, or you can remove PokerSharp's hidden app data from your Google account (Drive settings → Manage apps, or myaccount.google.com/permissions). We cannot delete your Drive copy for you.

Managing Advertising Data

The advertising signals described in Section 03 are held by Google, not by us. To manage that data:

Reset or delete your advertising ID from your device's settings (instructions in Section 03). Future ad interactions will not be linkable to prior ones.
Switch to non-personalized ads via the in-App Settings → "Ad privacy options" link, which re-opens the Google consent form.
Exercise your rights with Google directly for any data Google holds about you under their privacy policy at policies.google.com/privacy.

Managing Purchase Data

Purchase records live with the platform that billed you: manage or delete them through your Google Play or Apple account. The entitlement record held by RevenueCat (Section 04) can be deleted on request: contact us at the address below and we will initiate deletion with RevenueCat. Note that after the entitlement record is deleted you may need to use "Restore purchases" to re-activate Pro.

Deleting a Shared Hand

A hand you chose to share (Section 08) is kept for one year and then deleted automatically. To have it removed sooner, email its link to us at the address below, or use the Report this hand link at the bottom of the shared page, and we will delete the hand, its two pictures and its stored hash. You can also delete it yourself in the app under Settings, Data, Shared hands (for shares made on that phone), and copies already saved or forwarded by others cannot be recalled. A hand shared while signed in is deleted with your account; otherwise we can find a shared hand only by its link. Deleting the App or its data does not remove a hand you have already shared.

Bug Report Data

If you have sent a bug report (Section 05) and would like it deleted before its normal end-of-investigation deletion, email us with the approximate date and screen involved and we will remove it.

GDPR, CCPA, and Other Regulations

If you are a resident of the European Economic Area, the United Kingdom, California, or another jurisdiction with applicable data protection legislation, your rights under those frameworks apply to these categories of data separately:

Your training data remains on your device unless you sign in to a PokerSharp account, in which case a synced copy is held by us (Section 06). Signed out we hold none of it. If you are signed in, you can view and export it in the App and delete it by deleting your account, and you can email us to ask what we hold or to have it corrected or deleted.
Your account data (Google account id and email) is held to provide the sign-in and sync you asked for. You can delete it at any time as described above.
The advertising signals handled by Google AdMob are Google's data to manage under Google's privacy policy. Use the in-App "Ad privacy options" link to update your consent at any time, and contact Google directly for data-subject requests concerning data Google holds.
Pro entitlement data handled by RevenueCat can be deleted via a request to us, as described above.
Bug reports you have sent can be deleted via a request to us, as described above.
Shared hands can be deleted by emailing us the link, using Report this hand, or deleting them yourself in the app under Settings, Data, Shared hands (for shares made on that phone), as described above. Copies already saved or forwarded by others cannot be recalled.

If you have questions about how this App interacts with your rights under any applicable framework, please contact us at the address below.

Section 18

Security

Without an account we hold no user records. If you sign in, your account data is held in a database on Cloudflare, reachable only through our service with a per-device sign-in token (stored by us only as a one-way hash, and on your phone in the operating system's secure storage). Writes are rate-limited and capped per account to curb abuse. No system is perfectly secure, and a breach of that database would expose the account data described in Section 06. The hands you choose to share are stored on our endpoint in a private storage bucket and database, are reachable only through their random links, and are kept with a salted one-way hash of the install identifier rather than the identifier itself (Section 08).

Training data stored locally by the App is protected by the operating system's application sandbox: other apps cannot read it. On devices where full-disk encryption is enabled (the default on modern Android and iOS), the App's stored data is also encrypted at rest by the OS.

The App's network traffic travels over HTTPS / TLS in every case: the AdMob SDK's communication with Google (Section 03), the RevenueCat SDK's purchase validation (Section 04), any bug report you send (Section 05), your account's communication with our servers and the one-time Drive import (Section 06), the usage data (Section 07), and any hand you share, including the shared pages themselves (Section 08). Google and RevenueCat secure their data under their own security practices; bug reports and usage data are access-restricted (a bug report's screenshot is reachable only at its long, random, unlisted address, Section 05), uploads of shared hands are rate-limited and capped per install to curb abuse, and bug reports are deleted after the underlying issue is resolved.

Section 19

Do Not Track and Global Privacy Control

Some web browsers and mobile operating systems support a Do Not Track ("DNT") setting, and newer browsers support the Global Privacy Control ("GPC") signal, indicating that the user does not wish to be tracked across services. There is no universally adopted standard for how applications must respond to these signals.

The App sets no cookies and runs no cross-app tracking. Its only first-party analytics is the usage data described in Section 07, which is never used for advertising and which you can switch off in Settings → Privacy. Beyond that, the only monitoring is what the AdMob SDK does for ad-serving purposes. Mobile-app advertising does not rely on browser-level DNT or GPC signals; instead, the equivalent device-level control is the operating system's advertising-ID setting (Android) and the App Tracking Transparency framework (iOS). To exercise the equivalent of a "do not track" preference within the App, either:

Reset or delete your advertising ID from your device's system settings, or
Open the App's Settings → "Ad privacy options" link to switch to non-personalized ads via the Google consent form.

Either of these will stop personalized tracking by AdMob for this App. Steps for both are in Section 03.

Section 20

Links to Other Sites and This Website

This Privacy Policy page and the PokerSharp website may contain links to external websites or services that are not operated by us. If you click a third-party link, you will be directed to that third party's site, which is governed by its own privacy policy.

We have no control over, and assume no responsibility for, the content, privacy practices, or data-handling of any third-party sites or services. We strongly encourage you to review the privacy policy of any external site you visit.

The PokerSharp website (pokersharpgto.com) is hosted on Cloudflare, which receives your IP address and basic request details in order to deliver the pages and protect them from abuse. The website itself sets no cookies and runs no analytics. It stores a single value in your browser's local storage (your light/dark theme preference), which never leaves your browser. The site loads the "Outfit" typeface from Google Fonts, which means your browser requests the font files from Google's servers; that request necessarily includes your IP address and is handled by Google under its own privacy policy.

The pages that show a shared hand (Section 08) are served by our own endpoint rather than this website, and follow the same rules: they set no cookies, run no scripts and no third-party analytics, and store nothing in your browser. Our server keeps anonymous counts of how often each shared page is viewed and how often its buttons are tapped, with no cookie or identifier for the visitor. Unlike the rest of the site, their fonts load from our own server, not from Google Fonts.

Section 21

Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the effective date at the top of this document and, where the changes are material, provide notice through the App or the App Store listing.

Any future version of PokerSharp that introduces features requiring data collection beyond what is described here (such as multiplayer functionality) will be accompanied by a materially updated Privacy Policy presented to users before the new features become active. (The optional PokerSharp accounts described in Section 06, which replace the earlier Google Drive backup, are introduced under exactly this process in version 3.7 of this policy.)

We encourage you to review this policy periodically. Your continued use of the App following any changes constitutes acceptance of the updated policy.

Section 22

Contact

If you have questions, concerns, or requests regarding this Privacy Policy or PokerSharp's data practices, please contact us:

We will respond to all privacy-related inquiries within a reasonable timeframe. For questions about advertising data specifically, the fastest route is to manage your consent and advertising ID directly through the in-App "Ad privacy options" link and your device's system settings (see Section 03); for data Google itself holds, contact Google through their privacy support channels.