Last updated October 21, 2026
Privacy policy
This policy explains what Pic.Poker processes, why it is needed, and the choices you have when reviewing and sharing poker hands.
Information we process
We process the email address and player name or username you confirm (which may be suggested from your email address), poker photos you submit, detected cards and equity results, sharing choices, and basic technical data needed to operate and protect the service. Stripe processes website payments and Apple processes iPhone subscription payments. Pic.Poker stores subscription identifiers, expiration, and verification status to provide access; it does not receive or store full payment-card numbers.
Photos and poker analysis
A submitted photo is sent for card recognition. A metadata-free copy at the resolution received by the reader is retained in a private model-quality archive, along with card crops, model outputs, prompts and settings, timing, token usage, estimated costs, and the final cards you confirm. The archive is used to evaluate current and future card readers. It is not a public community post, and we are not training a model on these photos. Image metadata is removed during normalization and Pic.Poker does not use embedded GPS coordinates. After an upload is accepted, reading continues on the server while your phone is locked or the app is closed. A temporary account-protected read result is available for up to 24 hours so the app can resume card review; it is removed with account deletion. A random pending-review lookup ID and a temporary copy of the submitted photo may be stored on your device to recover interrupted uploads. The photo is eligible for recovery for up to 24 hours and is removed after the read is retrieved or account deletion; expired copies are cleaned up when the app next opens. Storage is limited to one pending photo per account and three on the device. These temporary records contain no sign-in credential. A small thumbnail can remain in your browser history. New photo reviews default to community sharing after you confirm the cards. You can select Keep this review private before confirming to prevent community publication. Shared thumbnails and hand results are stored for the selected audience and pass automated content and poker-photo checks before becoming visible. No community publication occurs just by uploading a photo. The research site uses a shared password. Archive entries use a non-readable account reference so account deletion can remove associated photos, crops, predictions, and annotations. We keep entries until account deletion or a request to support@howcan.io. Older photos may be available only at community-thumbnail resolution.
Earlier beta camera features
The current app reviews still photos and does not offer live detection or reader comparisons. Earlier beta builds offered experimental live detection and comparisons that sent sampled camera frames and card crops to TypeSafe to locate and identify the cards. Pic.Poker removes image metadata and does not log or save these live frames. Closing the camera or leaving the page stops the camera and scanning. Capture & review sends the photo to both TypeSafe and the existing card reader for comparison. Library photos are compared only when you enable that option. Comparison records contain card predictions, model identifiers, timing, a random capture ID, and the final cards you confirm; they contain no photo or account email.
Service providers
We use service providers to operate Pic.Poker, including Google for photo card recognition, OpenAI for community photo screening and earlier card readers, and Google, OpenAI and Anthropic for private card-reader evaluations. Earlier beta detection used TypeSafe. We also use Stripe and Apple for subscriptions, Resend for transactional email, and Render for hosting. Each provider processes information under its own terms and privacy commitments.
Review emails
Result emails include your confirmed cards, odds, and a copy of your poker photo with the reviewed boxes. Resend processes this content to deliver the email. Keeping a hand private prevents community publication but does not remove the photo from the result email sent to you.
Verified accounts
Sign-in and account deletion use one-time codes sent by Resend to the email you provide. Codes expire after 10 minutes and are stored only as keyed digests. Server sessions expire after 30 days, can be revoked, and are stored as digests. The website uses an HTTP-only secure cookie; the installed iPhone app keeps its session in the device Keychain. Account records are stored on our hosting service’s persistent storage.
Free reviews on an iPhone
The iPhone app stores a random, app-specific installation credential in the Keychain. We use a keyed hash of it and an allowance count to enforce five free photo reviews across sign-outs and email changes on that installation. It is not derived from hardware, location, advertising IDs, or browser settings, and is not used for advertising or tracking across other companies’ apps. The count is separate from account data and is retained when an account is deleted to prevent resetting the free allowance.
Community safety
OpenAI checks shared photos and their public labels for poker relevance and objectionable content before publication. Photos that pass appear automatically; failed or unavailable checks keep the photo out of public feeds. Flagging a photo hides it from your own feed while the moderator reviews the concern. Flagging your own photo holds it out of public view. Moderation records include submitted photos, posting status, reports and their reasons, and block-list relationships. Reports and blocking use your verified account. Your account email and block list are not included in public feed responses. Shared-photo access checks the selected audience, content-check status, reports, and blocking preferences.
Retention and sharing
Local account history remains on your device until browser data is cleared. Shared hands, account usage records, billing status, and moderation reports remain until removed or no longer needed to operate and protect the service. Deleting your account removes the associated application data and replaces the email in minimal subscription records with a non-readable account reference. Digests of deleted sessions remain until their original expiration, for up to 30 days, to tell other devices to clear local history. We do not sell personal information. We disclose it only to operate the service, comply with law, protect users, or complete a business transaction with appropriate safeguards.
Your choices
Before confirming the cards, select Keep this review private to opt out of the default community sharing. You can also choose to share a result by link later. Sample hands start private. You can delete your account in the account menu after confirming an emailed deletion code. You can also request access or correction, or find help, by following the data deletion instructions. Clearing browser storage removes device-only account history but does not cancel a Stripe or Apple subscription.
Contact
Privacy questions can be sent to support@howcan.io. This policy may be updated as the beta service and its storage architecture evolve.
