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 to keep your training data on your device. Your hand history and settings are never transmitted to us: we operate no accounts and no server that stores them. The exceptions are anonymous 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). If you enable the optional Cloud Backup, your history is saved to your own Google Drive, not to us (Section 06). The App’s training features work fully offline.

Six 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 (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 is the only service we ourselves operate. It receives a bug report only when you press send, and the anonymous usage data described in Section 07 only while that switch is on. Coach questions (below) pass through it too.
Optional cloud backup: if you connect a Google account, your hand history and settings are backed up to your own Google Drive. That data flows between your device and your Google account only, never through us (Section 06).
Anonymous 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 reporting endpoint to Anthropic, which writes the reply. This happens only when you send a question (Section 07).

This Privacy Policy explains precisely what data the App stores locally, what data each of those six 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). None of this data is ever transmitted to us. It leaves your device only if you enable the optional Cloud Backup, which stores it in your own Google Drive (Section 06). For the separate, narrower categories of data that can be transmitted, see Sections 03–07.

The data listed above contains no personally identifiable information (PII). No name, email address, phone number, location, or any other information that could identify you as an individual is collected, inferred, or stored.

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). 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 anonymous ID 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. A bug report is sent only when you review it and explicitly tap send. The one automatic exception is the small background error report described in Section 07. It is part of the anonymous 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, the game mode, app version, device model, and operating system version.

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 are not linked to any identity (there are no accounts); and they are not shared with any third party. Reports are retained only as long as needed to investigate and resolve the issue, then deleted.

Section 06

Cloud Backup and Google Drive

The App includes an optional Cloud Backup feature that keeps your hand history and settings safe, and keeps them the same on every device you play on. It is off by default and activates only if you explicitly connect a Google account under Settings → Data.

Where Your Data Goes

Backups are stored in a hidden, app-private folder of your own Google Drive (Google’s “application data folder”), under your own Google account and counting against your own Drive storage quota. Your device communicates directly with Google Drive over an encrypted connection (HTTPS). No PokerSharp server is involved, and we never receive, hold, or have any means of accessing your backup. Google processes this data as your storage provider under Google’s own privacy policy, not as a processor acting for us.

What the App Can and Cannot Touch in Your Drive

The App requests a single, narrow Google Drive permission (drive.appdata) that grants access only to the hidden folder it creates for itself. It cannot see, list, read, modify, or delete any other file in your Drive (no documents, no photos, nothing), and other apps cannot read PokerSharp’s folder.

What Is Backed Up

Hand history records: the same records described in Section 02;
Gameplay, display, and sound settings: so a second device feels the same as the first.
Chip balance, daily-bonus state, and your Pro entitlement are not backed up (Pro already follows your Google Play or Apple account).

Google Account Information

When you connect, the App receives your Google account’s email address, display name, and profile photo from Google’s sign-in service, solely to show on the Settings screen which account is connected. This information stays on your device and is never transmitted to us. Connecting a Google account creates no PokerSharp account; see Section 14.

Your Controls

Sync Now: run a backup manually at any time;
Delete Backup (Settings → Data): removes every PokerSharp file from your Drive, leaving the data on your device untouched;
Disconnect: stops all syncing;
Revoke access at Google: from myaccount.google.com/permissions, or via Google Drive’s “Manage apps” settings, which can also delete the hidden app data itself.

Section 07

Usage Data (First-Party, Anonymous)

While PokerSharp is in development, the App records anonymous 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 08).

You can turn this off at any time in the App under Settings → Privacy → Share anonymous play stats. The App shows a one-time notice explaining this the first time you open it. Turning the switch off stops all recording immediately, clears anything not yet sent, and stops the App from contacting the endpoint at all. The setting is per device and is deliberately not included in Cloud Backup, so switching it off on one device never silently switches it on somewhere else.

What is in it

Each event carries an anonymous 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, and settings changes.

None of it identifies 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 account, because the App has no accounts (Section 14). 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. 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 Anthropic, a third-party processor, so that its model can write the reply. Anthropic does not use this content to train its models by default. We do not send your name, email address or any account detail, because the App has none; please do not type any into a question.

Unless you have turned off Share anonymous play stats, we keep each question and answer for 90 days, stored against a one-way hash of your anonymous install identifier (and, for Pro, a hash of the anonymous 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, 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 on an answer that would otherwise not be kept, that one question and answer are kept for 30 days so that we can review the report. To have coach data deleted sooner, contact us with your install identifier (Section 16).

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 16).

Section 08

Data We Do Not Collect

The six 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 Cloud Backup to your own Google Drive (Section 06), anonymous usage data you can switch off (Section 07), and the questions you choose to ask the in-app coach (Section 07). Setting those aside, the following categories of data are not collected, stored, transmitted, or processed by PokerSharp under any circumstances:

Personal & Identity Information

The App does not collect names, email addresses, phone numbers, usernames, profile photos, dates of birth, or any other personal identifiers. No account registration of any kind is required or available. If you connect a Google account for Cloud Backup, the App shows that account’s email address on your device’s Settings screen only: it is never sent to us (Section 06).

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 anonymous random ID generated for the Pro entitlement (used only by the RevenueCat SDK, Section 04). We do not receive either identifier. 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 anonymous 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 anonymized purchase status: that an installation holds an active Pro entitlement for a given product, never who you are or how you paid. See Section 04.

Network Communications

The App’s outbound network traffic is limited to exactly six 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), the Cloud Backup’s direct communication with your own Google Drive if you have connected a Google account (Section 06), and the anonymous 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 Anthropic’s model API (Section 07). 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 09

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), or the App’s own optional Cloud Backup to your Google Drive (Section 06), and in either case, the data is controlled by you, not by us.

We have no access to any data stored locally on your device, regardless of how it is backed up. If you restore a device from a backup that includes PokerSharp’s data, that data will reappear on your device, but it was never transmitted to us and we remain unable to access it.

Section 10

Third-Party Service Providers

We engage three 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 anonymous installation identifier 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 account detail. 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.

A note on Google Drive: the optional Cloud Backup (Section 06) is not a service provider relationship of ours. Your device communicates directly with Google Drive under your own Google account; Google acts as your storage provider under your agreement with Google, and we never touch, route, or access that data.

Beyond these three providers (and the bug-report 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, does not provide social-sharing features that transmit data to external services, and does not embed any other third-party SDK that independently collects or transmits data. 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 us, to RevenueCat, or to Google’s advertising systems. Apart from the summary of one hand that goes to the coach when you ask about it (Section 07), it leaves your device only if you enable Cloud Backup, in which case it is stored in your own Google Drive under your own account (Section 06), held by Google as your storage provider, and still beyond our reach.

Section 11

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 enable Cloud Backup, in your own Google Drive, see Section 06) and is never in our hands to sell.

Section 12

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.

We operate no user database and no system that stores user-attributable information. Your training history, settings, and session data exist only on your device (and, if you enabled Cloud Backup, in your own Google Drive) and are beyond our reach. A subpoena, court order, or government demand directed at us could therefore yield, at most, transient bug reports (which contain no identity information and are deleted after resolution) and the anonymous usage events described in Section 07, which are keyed to a random install identifier rather than to a person. With respect to your identity, there is nothing 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. The same applies to any Cloud Backup: it lives in your own Google Drive, held by Google under your account (Section 06). 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 13

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.

Because we do not hold user data, no personal information would be transferred as part of such a transaction. A successor entity would acquire the App and its codebase, but not a database of user records, because no such database exists. The privacy commitments in this document would be represented to any acquirer as binding obligations carried forward with the App.

Section 14

No Accounts or Authentication

PokerSharp does not require you to create an account, log in, or authenticate with any service to use any feature of the App. There is no registration flow, no email verification, and no password. The one optional sign-in is connecting a Google account for Cloud Backup (Section 06): that connection is between your device and Google, creates no PokerSharp account, and shares nothing with us.

Because there are no accounts, there is no profile data associated with you. Your training history, preferences, and progress are stored anonymously on your device and are associated with the App installation, not with any named identity. Even PokerSharp Pro works this way: entitlement is tracked against an anonymous random identifier (Section 04), and can be restored on a new device through your Google Play or App Store account using the “Restore purchases” option; the store, not us, knows who made the purchase.

If you uninstall and reinstall the App, your local training data will be cleared, and unless you had enabled Cloud Backup there is no mechanism to recover it: it was never stored outside your device. If Cloud Backup was enabled, reconnecting the same Google account restores your hands from your own Drive (Section 06).

Section 15

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 16

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. We have no copy of this data on our side that could be exported to you in any other form.

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 enabled Cloud Backup, there is no remote copy to request deletion of, because none was ever created.

Deleting Your Cloud Backup

If you enabled Cloud Backup (Section 06), one remote copy exists (in your own Google Drive), and you can delete it yourself at any time: in the App via Settings → Data → Delete Backup, or from your Google account by removing PokerSharp’s hidden app data (Drive settings → Manage apps, or myaccount.google.com/permissions). We could not delete it for you even on request: we have no access to your Drive.

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 anonymous 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.

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 (or, if you enabled Cloud Backup, in your own Google Drive) and is not collected, processed, or stored by us. We hold none of it, so requests for access, portability, correction, or deletion directed at us return nothing: the data is already in your possession and you can delete it yourself at any time, including the Drive copy (Section 06).
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.

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

Section 17

Security

Because we operate no user database and no infrastructure that holds user-attributable data, the most common category of data-security risk (a breach of a centralized server of user records) does not exist with respect to PokerSharp on our side. There is no remote dataset of users to compromise.

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), the optional Cloud Backup’s communication with your Google Drive (Section 06), and the anonymous usage data (Section 07). Google and RevenueCat secure their data under their own security practices; bug reports and usage data on our reporting endpoint are access-restricted, and bug reports are deleted after the underlying issue is resolved.

Section 18

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 anonymous 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 19

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 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.

Section 20

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 user accounts or multiplayer functionality) will be accompanied by a materially updated Privacy Policy presented to users before the new features become active. (The optional Cloud Backup described in Section 06 was added under exactly this process, in the August 2026 revision 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 21

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.