minclick does not host games, accept wagers, transfer gambling funds, process payments between players, or sell personal information. Apple or Google processes optional app-subscription payments.
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.
These records are not uploaded merely because you install the app or sign in. 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, pauses on a version conflict, and asks before replacing either copy. 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.
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. Signing in does not automatically upload your complete local session or hand history. Full-state automatic sync requires its own explicit opt-in.
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.
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.
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
- secure, operate, troubleshoot, and improve the service.
The app does not contain third-party advertising or behavioral analytics code. 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, and server functions. Row-level security limits access according to the signed-in account and feature membership. 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.
Device, operating-system, app-store, file-sharing, and email providers process information when you use their services. These providers process information 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.
Camera and files
Camera access is used for on-device hole-card recognition. 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. Delete recordings in Session recordings or through Erase All Local Data; deleting a poker session or community account alone does not delete its video.
Retention and deletion
Local records remain on the device until you delete them, erase local app data, or remove the app, subject to device backups and operating-system behavior. 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. A shared collaborative ledger remains until its owner deletes it, while a member can leave it. 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.
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 a community account does not erase local sessions, hands, bankrolls, home-game ledgers, or card samples from your device. Use Erase all local app data and the card-sample deletion control for those items.
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; delete your account; export your data; and erase local app data.
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.