Privacy Policy

Information stored on your device

minclick stores its core app data locally on your device. Depending on the features you use, this can include:

• poker sessions, hands, actions, cards, notes, locations, stakes, buy-ins, cash-outs, tips, expenses, and results;
• bankrolls, transactions, settings, filters, and an active live-session draft;
• home-game ledgers, including player names, buy-ins, add-ons, cash-outs, and settlement calculations; and
• card-training images and metadata collected after your explicit opt-in, including predicted cards, detected regions, recognition timestamps and labels you enter.

Your complete records are not uploaded merely because you install the app or sign in. For community accounts, the friend-profile graph summaries described below are shared by default, unless you turn that setting off. You can export session files, backups, or a card-training dataset using the system share or file picker. You can also explicitly upload one private full-state backup to your signed-in account. That copy is replaced only when you upload again and can be downloaded, restored after confirmation, or deleted from Settings.

If you separately enable automatic multi-device sync, the app uploads an encrypted-in-transit private state copy to your signed-in Supabase account after local saves. Sync is off by default. A newer cloud version is applied automatically only while the local copy still matches the last accepted cloud copy; if both copies changed, sync pauses and asks which copy to keep. If you explicitly share a home-game ledger, its entries and member access records are stored in Supabase so invited members can collaborate. Card-training photos are never included in backup, sync, community posts, or collaborative ledgers.

The upcoming shared-home-game update uses one bank manager rather than simultaneous editing. The following applies to builds that support this new flow. When you explicitly share a game, Supabase stores its game details, player names, buy-ins, cash-outs, and any chip-set, chip-count, reconciliation, and settlement records included in that game. Member access, invitation, and handover records are also stored. People with a valid invitation can sign in and explicitly join to view the game’s records; joining members’ profiles are visible to the other members. Only the current bank manager can change the financial and chip records, and another member must accept a handover before that authority changes. Opening an invitation webpage does not join the game or display its financial records. If a game shared from your local records later becomes inaccessible, its last saved local copy may remain read-only on that device; it is not a current view of the shared game. Existing shared ledgers retain their earlier format and access rules.

Optional account and community information

If you create or use a community account, Supabase processes:

• your email address, authentication identifier, login session, username, display name, and any profile photo you choose to upload;
• friend requests and accepted friend relationships;
• session posts you explicitly choose to share, captions, up to four photos you attach, and whether each post is visible to accepted friends or only you;
• likes and comments;
• community notification events and the device-specific Expo push token you register after granting permission;
• mute and block relationships; and
• reports you submit about accounts, posts, or comments.

A shared post includes its date, duration, stakes, format, venue type, game type, limit type, buy-in, cash-out, expenses, net result, and any recorded location. It can also include a caption and up to four photos you select. Hole cards, hand histories, notes, and bankrolls are never included in a community post. Buy-ins, results, bankrolls, and ledger amounts can be included in a separate full-state backup or sync only when you enable that feature. Signing in does not automatically upload your complete local session or hand history. Full-state automatic sync requires its own explicit opt-in.

When you choose a new profile or post photo, its editor displays an OpenAI safety-check notice and a link to this policy. Choosing a photo only makes a local draft; canceling or removing it sends nothing. Tapping Save changes or Post with that photo is your affirmative permission to send only the selected new photo(s), through a minclick server function, to OpenAI's Moderation API for a safety decision before upload to community storage. If you do not want the check, remove the photo or cancel and continue without uploading it. The permission is remembered for that account on that device and can be withdrawn in Settings → Your Data. After withdrawal, a later selected-photo Save or Post can grant permission again under the same inline notice. Withdrawing permission does not remove photos already shared, which you can remove separately. A rejected photo is not posted. This screening does not receive live camera frames, card-training samples, session details, or session recordings. OpenAI states that API inputs are not used to train its models by default and lists no routine abuse-monitoring or application-state retention for the Moderations endpoint; legal and safety exceptions may still apply. See OpenAI's API data controls.

Friend-profile graphs

In versions supporting friend profiles, Share graphs with friends is on by default for community accounts. You can turn it off in Settings → Community. Supabase stores daily aggregate net results, playing hours, session counts, winning-session counts, dates, and the display currency so accepted friends can see your performance charts, including sessions you have not posted. These summaries do not include individual session IDs, locations, stakes, notes, hands, cards, bankrolls, or recordings. Posts keep their separate audience settings.

The app updates summaries from saved completed records on one source device. Another device does not silently replace them; you can explicitly choose Use this device’s records. Turning sharing off removes the server snapshot and prevents further uploads until you turn it on again. Removing a friend or blocking an account prevents new graph reads. An already open profile refreshes periodically and on return to the foreground, and copies someone already captured cannot be recalled. Deleting the account removes its graph snapshot.

Photo-safety permission controls are also in Settings → Community in these versions.

Optional subscriptions

If you view, purchase, restore, or manage minclick Pro, Apple or Google handles the store transaction and RevenueCat processes a pseudonymous Supabase account UUID, store and product identifiers, purchase history, subscription status, entitlement status, and related device, app, country, and store metadata made available by the platform. RevenueCat also uses purchase events for subscription analytics. In versions with the optional advertising measurement described below, RevenueCat can forward eligible subscription events to Meta.

minclick does not send RevenueCat your email address, poker records, card samples, friend content, or home-game ledger contents. RevenueCat returns entitlement information so the app can unlock paid features across your signed-in devices.

Optional app advertising measurement

In builds with advertising measurement enabled, you can choose whether to allow tracking in iOS Settings. Local logging and Pro remain usable without allowing tracking. With authorized App Tracking Transparency (ATT) permission, minclick sends app installation and activation events, the advertising identifier (IDFA), app identifier and version, operating-system version, and event time to Meta to measure and optimize minclick's own ads. It does not display third-party ads in the app.

For Pro conversion measurement, minclick supplies RevenueCat with the authorized IDFA and ATT status. RevenueCat may send trial starts, paid subscription conversions, initial purchases and renewals to Meta, together with subscription product identifiers, amount and currency, event and order identifiers, a pseudonymous account identifier, app/device context (including device/vendor identifiers if available to the provider), and an IP address when available to the provider. This measures which campaigns lead to Pro use and revenue. It does not send poker results, hands, notes, photos, recordings, email addresses or phone numbers to Meta. No separate client-side subscription events are sent, to avoid counting a purchase twice. Meta reporting is not a refund-adjusted accounting ledger.

The RevenueCat integration requires its last observed ATT status to be authorized. Returning to the app refreshes that status; if permission has been withdrawn, minclick requests removal of its advertising identifier from RevenueCat. A change made while the app is closed or offline cannot immediately reach RevenueCat, so later server-side renewals may still use the last synchronized permission until it is updated. Network failures or provider rejections can delay that update; a completed local sync call does not itself confirm removal. Withdrawing permission stops future eligible sharing once the updated state is accepted; it does not retract events already sent. Meta processes events under its own terms and privacy policy. Delivery does not guarantee attribution of every install or purchase to an ad.

Website analytics

The public minclick website uses Vercel Web Analytics to count visitors and page views and understand which pages are useful. This website measurement is separate from the app. Vercel processes page paths, safe referring pages, approximate location, browser, operating system, device type, and visit time for aggregated statistics. It uses no analytics cookies; a visitor hash derived from the request is discarded after 24 hours.

We remove query parameters and fragments from measured page URLs, exclude the email-confirmation page, and skip measurement when a referring URL may contain authentication details or query parameters. We send no account identifiers, email addresses, poker records, form contents, or custom events to website analytics. See Vercel's Web Analytics privacy information.

Former website waitlist

The website no longer collects new waitlist signups now that minclick is available on the App Store. If you joined before launch, minclick stores the email address you entered, the signup source, and the time you joined. An address must be confirmed through an expiring email link before it becomes part of the launch list. Unconfirmed signup records become eligible for removal after seven days and are removed during later signup activity.

To limit repeated automated submissions, minclick's waitlist tables briefly store a salted, one-way fingerprint derived from the request network address. Those tables do not store the raw network address. Supabase's network gateway may process and retain network addresses in infrastructure and security logs under Supabase's own terms; minclick does not write those raw addresses to its waitlist tables.

Supabase stores the waitlist record and runs the signup, confirmation, and delivery-retry functions. Resend processes the submitted email address to deliver the confirmation message. After confirmation, Resend sends minclick an operational notification that includes the confirmed address and may deliver the single launch message. Only confirmed addresses receive that launch message, unless you separately ask for other communications.

Confirmed waitlist records remain until the launch message is sent, the waitlist is retired, or you ask for removal. To remove your email before then, contact soungminlee@gmail.com from the address you submitted.

How information is used

Information is used to:

• save and analyze your poker records;
• create files or backups you request;
• authenticate accounts and maintain profiles;
• connect confirmed friends and show a private friend feed;
• provide sharing, likes, comments, optional push notifications, muting, blocking, reporting, and account deletion;
• provide optional private multi-device sync and collaborative home-game ledgers;
• validate, restore, and manage paid-feature access; and
• manage records from the former website waitlist and its promised single launch message; and
• secure, operate, troubleshoot, and improve the service.

The app does not display third-party advertisements. Optional, permission-gated measurement of minclick's own ads is described above. Supabase and app stores may process operational, security, or distribution data under their own privacy terms.

Who can see community information

Shared session posts are visible according to the audience you choose: either only you or you and accepted friends, subject to blocking and muting controls. The app remembers your most recent audience choice for the next post, and you can change it before posting. A pending friend request does not grant access to friend-visible posts. Optional profile and post photos are kept in private storage and delivered to authorized viewers through short-lived links. Changing the audience, removing a friend, blocking them, or unsharing prevents new links, but an already issued link may remain usable briefly. People cannot browse a public directory of minclick profiles; username lookup is used to find a specific account.

Accepted friends can see the session-summary fields, financial result, and any recorded location in a friend-visible post. Removing a shared post stops it from appearing through the community feed, but copies already saved or captured by another person cannot be recalled.

Service providers and disclosures

Supabase provides account authentication, the community database, private backup and sync storage, collaborative ledger storage, the website waitlist database, server functions, and network infrastructure. Row-level security limits access according to the signed-in account and feature membership. Resend delivers the waitlist confirmation, operational notification, and launch email. OpenAI processes only selected profile or post photos for the optional, consented safety check described above. Expo, Apple Push Notification service, and Firebase Cloud Messaging help deliver notifications after you opt in. Apple or Google processes subscription payments, and RevenueCat validates purchases and supplies entitlement status.

We limit information sent to each provider to the requested function. Each provider processes that information under its applicable privacy, security, and data-processing terms. Device, operating-system, app-store, file-sharing, and email providers also process information when you use their services, under their own terms and privacy policies.

minclick may disclose information when required by law, to protect users or the service, or in connection with a business transfer, subject to applicable law.

minclick does not sell personal information. If you allow optional advertising measurement, Meta receives the advertising and subscription-event information described above. Meta processes that information for advertising measurement, matching and optimization under its privacy policy. RevenueCat supplies eligible subscription events through its Meta integration.

Camera and files

Camera access is used for on-device hole-card recognition and, only when you start it, local session video recording. Recognition does not require you to save training samples. If you separately enable Training samples, the app can save one analyzed camera frame per stably recognized hand, together with predicted cards, detected regions, timestamps and model information, while you use recognition normally. The feature does not take photos on a periodic timer. Images can include people or surroundings; follow venue rules and obtain permission where necessary. Predictions are not verified labels, and enabling collection does not automatically train a model.

Samples remain in the app's document storage unless you explicitly export them. There is no automatic sample upload, and samples are excluded from app cloud backup, sync and community sharing. Collection is limited to 500 samples or 250 MB. You can turn collection off, export samples or delete them in Settings; turning collection off does not delete existing samples. Operating-system backups may retain local app files. minclick does not request microphone recording for this feature.

Photo-library access is used only when you explicitly choose a profile photo or attach photos to a community post. The app crops or reduces selected images before uploading them to private community storage; it does not upload the rest of your library. Profile photos and post photos are made available only to authorized community viewers through short-lived links. File and sharing access is used only when you choose to import, export, back up, restore, or share data.

Optional session video recording

You can explicitly start a local session video with microphone audio on by default, or turn audio off before recording. Microphone permission is requested when starting with audio enabled. Obtain necessary permission from people nearby and follow venue rules. A visible recording indicator and Stop control remain available. Locking or leaving the camera ends recording; it does not restart automatically.

The local index contains the session identifier, recording date, detected cards, approximate hand-marker timestamps, size and interruption status. Predictions and navigation windows are not guaranteed hand boundaries. Videos and indexes are excluded from cloud backup, sync, community sharing, training datasets and operating-system backup. Only your explicit export sends a copy to your selected destination. Export before uninstalling.

Deleting a recording in Session Recordings moves it to Trash and leaves its poker session, financial result and saved hands intact. Deleting a completed poker session, or discarding a live session, moves its local record or draft, saved hands and currently available associated recordings to Trash together. Deleting a community account alone does not delete local videos. Erase all local app data also removes recordings in the selected local library, including those in Trash.

Retention and deletion

Local records remain on the device until permanently deleted, erased with local app data, or removed with the app, subject to device backups and operating-system behavior. Deleted sessions and recordings can be restored from Settings → Trash for 30 days from deletion. Expired items are purged when the app next runs in the foreground; the app does not perform this deletion while closed. You can permanently delete an individual item or choose Empty Trash after confirmation. Videos in Trash remain on the device and continue to use storage. Deleting a shared session unshares its community post; restoring the session does not republish that post. Individual hand, bankroll, ledger and card-sample deletions do not use this Trash recovery period.

Exported JSON backups and optional cloud backup or sync can include Trash recovery records: deleted session and hand data, bookmark choices, deletion dates, and basic recording metadata such as identifiers, recording date, duration, size and whether audio was enabled. They do not include video/audio files or the native hand-marker indexes. Permanently deleting local Trash does not erase independently exported files or previously uploaded manual backups.

A manually uploaded cloud backup remains until you replace it, delete the cloud copy, or delete the associated account. An automatic-sync copy remains associated with the signed-in account until account deletion; disabling sync only unlinks the current device. You can export a JSON backup before erasing local data; this does not preserve recording files.

Earlier collaborative ledgers retain their owner-controlled deletion rules: the owner can delete the shared ledger, while another member can leave it.

In builds supporting the new single-manager shared games, the server keeps a game's records while at least one member remains. Leaving, being removed, or deleting an account removes that person's membership, but does not erase player names or financial and chip records already entered in the shared game. A manager must complete a handover before leaving. If the current manager deletes their account while other members remain, those members retain read-only access and cannot appoint a replacement manager. If the creator deletes their account after an accepted handover, the game and its new manager remain in place. There is no individual delete-for-everyone control for these games.

When the last membership is removed, including through account deletion or the last viewer leaving a managerless game, the server deletes the shared game and its associated invitation and handover history. This does not erase local read-only copies or files already exported by participants. Local copies remain until removed from the device as described above. These records are subject to legitimate security, legal, and disaster-recovery retention.

Registered push tokens remain until the device disables community notifications, signs out locally, the push service reports the token invalid, or the associated account is deleted. RevenueCat and the app stores retain transaction and subscription records according to their legal and operational requirements; deleting a minclick account does not cancel a store subscription or erase records the store must retain.

Unconfirmed website waitlist records become eligible for removal after seven days and are removed during later signup activity. Confirmed records remain until the launch message is sent, the waitlist is retired, or the submitted address asks for removal. Anti-abuse fingerprints are used only for a 24-hour throttling window and are removed during later signup activity.

You can change or remove your profile photo, unshare individual community posts and their attached photos, or delete your community account in the app. Account deletion removes uploaded profile and post photos, the authentication account, associated profile, and user-owned community rows under the current database rules. Limited safety, legal, backup, or operational records may be retained where permitted or required.

Deleting an account keeps its local sessions, hands, bankrolls, home-game ledgers, recordings and card samples available without signing in on this device. Existing guest libraries remain separate and can be selected in Settings → Local records. Signing into a different account does not automatically merge these records. To remove retained data, select that local library and use Erase all local app data, permanently delete session or recording items from Settings → Trash, or use the card-sample deletion control. Export anything you need before removing the app.

Security

minclick uses platform storage for local data and Supabase authentication and row-level security for community data. No system is completely secure. Protect your device, email account, and password, and export sensitive data only to destinations you trust.

Your choices

You can use local logging without an account; choose which sessions to post and whether each is visible to accepted friends or only you; unshare posts; remove friends; mute or block accounts; delete eligible comments; report content; enable or disable community push notifications; upload, restore, or delete a private cloud backup; enable or disable automatic sync; leave or delete eligible collaborative ledgers; restore or manage a subscription through the applicable store; request removal of a former website waitlist signup; delete your account; export your data; restore or permanently delete eligible items in Trash; and erase local app data.

You can also withdraw advertising tracking permission in iOS Settings. Local logging, purchased Pro access and community notification choices do not depend on allowing tracking.

International use and children

Data may be processed where Supabase and other providers operate. Do not use minclick if you are not legally permitted to use the service or agree to this policy. minclick is not directed to children under 13, and community accounts should not be created for them.

Contact and changes

For privacy or data requests, email soungminlee@gmail.com. Never send passwords or authentication links.

This policy may be updated as the app changes. The effective date above will be revised when material changes are published.