Privacy Policy

Effective Date: October 20, 2026

SolvePoker (formerly SolvePLO; "we," "us," "our") respects your privacy. This Privacy Policy explains what data we collect, how we use it, and your rights regarding your information when you use solvepoker.app, solveplo.app, solvenlhe.app, or logbook.solvepoker.app (together, "the Service"). The sites share one account system, and this policy covers all of them.

1. What Data We Collect

Account Information

When you create an account, we collect your email address. This is the only personally identifiable information we require for registration.

Payment Information

If you subscribe to a paid plan, payment is processed by Stripe. We do not store your full credit card number, CVV, or bank account details on our servers. Stripe handles all payment data in compliance with PCI DSS standards. We receive and store only a transaction reference, the last four digits of your card, and billing status information from Stripe.

Files, Notebooks and Support

If you upload hand histories, we store the files and parsed hands to provide the tracker. If you save a notebook, we store its title and contents; anyone with a public notebook link can open it. Contact forms and support chat send us the name, email address and message you provide. These features are optional.

Usage Analytics

We collect usage analytics to understand how the Service is used and to improve it. This includes pages visited, features used, session duration, and general device/browser information. We use Google Analytics 4 (cookies _ga and _ga_<id>) to distinguish visitors and measure engagement. We also log calculator-usage events (which tool, which action) server-side; if you are logged in these are stored against your account email so we can debug issues, detect abuse, understand which features are used, and decide which emails are relevant to you. Microsoft Clarity records sessions: how pages render and where you click, scroll and move the mouse (see Section 3).

The Android app creates a random installation ID to measure first opens and whether installed users open tools, practice or return. We link it to the browser's random ID and, when you sign in, your account ID. Google Play may provide campaign labels and whether an ad click led to the install. We retain those labels and a click-presence flag, rather than the raw click ID. Usage events also include the country inferred from the request and a broad error category when a runtime or asset-loading problem occurs. We use this information to find first-use problems and compare advertising campaigns with recorded product use. The app does not request the Android advertising ID.

Technical Data

Our main-site servers automatically log standard technical data when you access the site, including IP address, browser type, operating system, and request timestamps. This data is used for security monitoring and debugging and is not linked to your account for profiling purposes.

SolvePoker Logbook

Logbook addendum: October 24, 2026

Guest records stay in your browser. Signing in does not upload them. An explicitly confirmed copy to your account includes saved records and their history: financial records, original imported data and private notes, including replaced, hidden or removed note history. Changes you save in the account workspace are then sent to the account service. Unsubmitted form drafts and private hand photos stay in that browser and are excluded from account backup.

Cloudflare hosts the Logbook app and stores account records, temporary upload and download data, account and browser identifiers, your chosen browser label, access and acknowledgement timestamps, and save and deletion receipts. Logbook checks your existing SolvePoker sign-in and does not create a separate password.

Publishing a hand link is a separate action. It uploads only the reviewed snapshot, with Hero and numbered seat labels. This can include cards, action, chip amounts and your optional public question exactly as entered. Private notes, Player notes, photos, places, dates and linked financial records are excluded. Check the preview for identifying details. Anyone with the link can read it until expiry, revocation or account-data deletion. Recipients may keep copies.

Logbook does not load advertising trackers, third-party analytics or session recording. The main site's sign-in, registration and solver pages use the services described elsewhere in this policy. Checking Core access reads your existing membership. Opening a related solver spot sends the selected board and solver context in the link, plus hero cards and a generic referral tag only if you select them. The parent site's ordinary privacy policy applies there.

If optional product analytics is available, it starts off each visit and requires a separate Allow action in your account workspace. Reloading starts off again. Guest recording and the sample send no analytics. Allowing analytics is separate from cloud backup or support access and is not required to record, export or request study.

Optional analytics counts fixed actions by UTC day: starting a session, ending play, completing an import or hand review, seeing an optional study suggestion, opening study, and requesting a download. It also counts session starts in a later week. Ending play does not mean a cash-out was confirmed, and requesting a download does not prove a file was saved. The service groups counts by new or existing account, Core entitlement when consent began, observed import use and a randomly assigned study-suggestion group. The test can hide optional study suggestions; manual study remains available in both groups.

These counters use an internal account-derived pseudonym, a consent revision and account-generation safeguards. They are linked to your account, not anonymous. The analytics payload contains no amounts, private notes, cards, record IDs, email, raw page addresses or IP addresses. Cloudflare still processes ordinary connection information when receiving a request. Separately approved analytics staff can view fixed aggregate reports, with each cell requiring at least five distinct consenting accounts. Event counts and account counts do not establish unique people or paid conversions.

If hosted support access is available, you can select one saved session or hand note, preview the exact immutable copy and explicitly authorize approved staff to read it for one hour. A session copy can include its game and stakes, venue, start and end times, currency, money and wallet entries, and recorded settlement. A note copy contains only its text and recording time. Other sessions, linked notes, drafts, photos, Player notes and the rest of your record history are excluded. Staff access requires an approved staff identity, a recent sign-in and confirmation of the specific support purpose. Accepted access is recorded in your audit history. A support grant does not authorize business analytics access.

You can revoke a hosted support copy. Revocation, expiry, Logbook cloud-data erase and whole-account retirement remove the active hosted copy. Deleting browser data alone does not revoke it. Copies already delivered to a staff browser, downloaded or otherwise retained cannot be recalled. Support-copy and analytics retention are described below.

Downloaded backups and recovery files can contain private records, processed photos, draft recovery and account working recovery. Password encryption protects the chosen file, not browser storage or separate plain files. Local erase affects only the selected browser copy. Remote deletion cannot erase offline browser copies, downloaded files or recipients' copies. Support email and diagnostic downloads require your action; Logbook does not automatically send records to support.

2. How We Use Your Data

  • Account management: To create and maintain your account, authenticate your access, and manage your subscription.
  • Service improvement: Aggregated usage data and session recordings help us understand which features are used, identify bugs, and prioritize development.
  • Email communications: We send account and billing emails (verification, sign-in codes, password resets, renewal notices, cancellation confirmations), a short series of emails in your first weeks, and a product update about once a month. Which of these you receive depends on how you have used the Service, for example whether you have imported hands or reached a free-tier limit. You can turn off everything except account and billing emails from the unsubscribe link in any of the others, or under Account > Email.
  • Security: Technical logs help us detect and prevent abuse, unauthorized access, and other security threats.

3. Third-Party Services

We use the following third-party services, each with their own privacy policies:

  • Cloudflare - Hosting and delivery of Logbook, including account records and published hand snapshots. Where enabled and explicitly chosen, Cloudflare also stores selected support copies and optional account-linked analytics counters, and processes requests to those services.
  • Stripe - Payment processing. Stripe collects and processes payment information under their own privacy policy. See stripe.com/privacy.
  • Google Analytics 4 - Web analytics. Sets cookies to measure traffic and engagement. See policies.google.com/privacy.
  • Google Ads - Conversion tracking for our marketing campaigns. Sets cookies on conversion events. See policies.google.com/privacy.
  • Microsoft Clarity - Session recordings and heatmaps, on the site and in the solver. Clarity records how pages render and how you interact with them (clicks, scrolling, mouse movement) so we can find bugs and confusing screens. Each recording is tagged with your account ID if you are signed in, or with the random device ID stored in your browser (prefixed anon:) if you are not, and with whether you are signed out, on the free plan or on Core. The ID is never your email address, and Clarity hashes it in your browser before it is sent. Clarity sets the cookies _clck (its visitor ID) and _clsk (which joins the pages of one visit into one recording). See microsoft.com/privacy/privacystatement.
  • Mailgun - Email delivery: account and billing emails, and product updates (account verification, password reset, billing receipts, contact-form notifications, the monthly product update). Mailgun receives the recipient email address and message body. See mailgun.com/privacy-policy.
  • Chatwoot - Customer support chat. If you open the chat as a logged-in user, your account identifier, email, and a display name derived from your email are passed to Chatwoot, along with the contents of your conversation. See chatwoot.com/privacy-policy.

We do not sell or rent your personal data. The services above receive the data described in this policy. Microsoft processes Clarity data under its own Privacy Statement.

4. Cookies

SolvePoker sets the following first-party cookies:

  • __session - Keeps you logged in for up to 30 days. Essential.
  • gclid_aw - Set for 90 days if you arrived from a Google Ads click; used to attribute paid signups back to the ad that drove them.

Google Analytics, Google Ads, Microsoft Clarity, and Chatwoot set their own cookies (see Section 3).

5. Data Retention

  • Account data: Retained for as long as your account is active. If you delete your account, your personal data is removed within 30 days.
  • Payment records: Transaction records are retained as required by tax and financial regulations (typically 7 years).
  • Analytics data: Google Analytics retains event-level data for up to 14 months by default (configurable in our GA4 admin). Aggregated reports are retained indefinitely.
  • Session recordings: Microsoft Clarity keeps recordings for 30 days. Recordings we mark as favorites, a random sample Clarity keeps, and heatmaps are kept for up to 9 months. Clarity offers no way to delete one person's recordings early, so they expire on that schedule.
  • Main-site server logs: Automatically purged after 90 days. This period does not describe Cloudflare's own transport or security records for Logbook; no retention period for those records is specified here.

For Logbook, correcting, hiding or removing a record preserves its earlier history. Delete Logbook account data removes the account record history and makes its old hand links unavailable. Revoked browser-grant records, including browser labels and access timestamps, and deletion and retired-generation receipts remain to reject old requests and prevent deleted records from returning. Sanitized snapshots from those links remain stored until expiry or explicit revocation.

Deleting your whole SolvePoker account also removes Logbook browser grants and redacts its published hand snapshots. Owner and generation identifiers, deletion timestamps and receipts, and share-link receipt metadata remain to prevent deleted accounts or publications from returning. These retained safeguards are exceptions to the general account-data removal period above and have no scheduled automatic deletion.

Optional Logbook analytics counters and server consent expire no later than 30 days after consent, using scheduled cleanup. Turning off analytics stops future hooks for this visit and requests deletion of the saved counters. The app reports when server deletion is not confirmed so you can retry. Logbook cloud-data erase and whole-account retirement require confirmation that analytics counters for the retired generation were purged before reporting completion. Minimal pseudonymous off-consent revisions and retired-generation safeguards remain indefinitely to reject delayed old requests. Abuse-rate counters last at most one UTC day. These safety records are exceptions to the general account-data removal period above.

A hosted support copy is readable for one hour unless revoked sooner. Revocation, expiry, Logbook cloud-data erase and whole-account retirement remove its payload. Minimal case receipts, original-copy fingerprints and access audit metadata, including the actor, action, purpose and time, remain for at most 30 days under scheduled cleanup. They do not retain the copied note, cards or money. These periods do not promise deletion of external copies or specify Cloudflare's independent transport, security or provider-backup retention.

6. Your Rights

You have the following rights regarding your data:

  • Access: You can request a copy of the personal data we hold about you.
  • Correction: You can update your email address and account information from your account settings.
  • Deletion: You can request deletion of your account and associated personal data. Contact us at [email protected] or use the account deletion option in your settings.
  • Export: You can request an export of your personal data in a machine-readable format.
  • Objection: You can object to the processing of your data for specific purposes. Contact us to discuss.

To exercise any of these rights, email [email protected]. We will respond within 30 days.

7. Children's Privacy

SolvePoker is intended for adults 18 and over. We do not knowingly collect personal data from minors; if you believe we have, contact [email protected] and we will delete it.

8. Data Security

We implement reasonable technical and organizational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction. This includes encrypted connections (HTTPS), secure password hashing, and access controls on our infrastructure. However, no method of transmission over the internet or electronic storage is 100% secure, and we cannot guarantee absolute security.

9. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Effective Date" at the top of this page and notify registered users by email. Your continued use of the Service after changes take effect constitutes acceptance of the revised policy.

10. Contact

If you have questions or concerns about this Privacy Policy or your personal data, contact us at:

[email protected]