Privacy

Accounts and game progress

Signing up asks for a username, a public display name, and a password. Player accounts do not require an email address and may optionally add and verify one when email delivery is enabled. Passwords and one-time recovery codes are stored as hashed values, not as readable passwords or codes. Recovery codes are shown once for you to save. You can replace the entire set from My account after confirming your current password. Replacement immediately invalidates the old codes, signs out other sessions and invalidates outstanding email links, while preserving your password, verified email and scores.

For daily rounds, the server stores the card and its date, your guesses, results, points, and completion state, linked to your account or a random guest-session identifier. This supports scoring, resuming a round, history, and rankings. Session and rate-limit records include timestamps; browser-local progress can also include update timestamps.

Completed ranked rounds can appear on the public leaderboard with your display name, score, rank, and daily date. Choose a display name you are comfortable making public. Display names are checked for profanity and slurs before they are saved, and you can change yours later. In the iOS app that edit is under Account. Your sign-in username, password, and recovery codes are not leaderboard fields.

You can report a leaderboard name. We store the report with your account, the account you reported, a short reason, and the time, so we can review it. You can also hide a player from your own view of the board; that hide is private to you and does not remove them for anyone else. We can hide a display name from the public leaderboard. Hiding a name does not delete the account.

Pro subscriptions and account email

Six Hunches Pro can be bought on this website and in the iOS app. Wherever you buy it, the payment is taken by that platform’s payment processor, and this site never sees or stores your card number.

On this website, checkout is handled by Stripe, on Stripe’s own pages. We create a Stripe customer record that carries your Six Hunches account number and your username, so that a payment can be matched to the right account. Stripe collects an email address from you for its own receipts; that address belongs to your Stripe records and is not added to your Six Hunches account or used to sign you in. Cancellation, payment-method changes and invoices happen on Stripe’s billing portal, which we open for you from the Pro page. We ask Stripe what your subscription is currently worth rather than relying on what any single message from Stripe says.

In the iOS app, Apple takes the payment and holds the payment details. The app sends one transaction identifier. We ask Apple’s App Store Server API what that identifier is worth and store the result on your account: whether Pro is active, the plan (monthly or yearly), the status, when the current period ends, and whether it will renew.

Sign in with Apple sends an identity token. We check it with Apple and store Apple’s subject identifier, which is how the same Apple ID is recognized next time. We do not ask Apple for your name. A new Apple account gets a generated public display name, such as “Player 4F2A”, rather than your Apple ID name, and you can change it. The identity token may include an email address, including a Hide My Email relay. We do not save the email from that token. An email address is stored only if you add one yourself.

Sign in with Google sends an identity token. We check its signature against Google’s published keys and store Google’s subject identifier, which is how the same Google account is recognized next time. We do not use the name or email in that token. A new Google account gets a generated public display name, the same way an Apple account does, and you can change it.

My account shows whether email delivery is available. When enabled, you may add an optional email address, confirm your current password, and verify the address using an emailed link. We store verified and pending addresses privately, not on the leaderboard. Your previous verified email address stays active until a replacement is verified; unverified addresses cannot reset passwords. Existing accounts are not assigned an email automatically.

Verification and reset links use random, expiring, single-use tokens. Only their hashes are stored by the application. The email provider necessarily handles the recipient address and message, including the link. Reset and password changes invalidate existing sign-in sessions; recovery codes remain available. When delivery is unavailable, the interface says so rather than claiming a message was sent.

Cookies and this browser

Session cookies connect requests to a guest session or signed-in account and help protect account actions. Sample rounds, archive replays, and older local progress use browser storage. That local information is not automatically imported into ranked scores or synchronized between devices.

Guest daily rounds are server-scored and tied to the current browser session, not a portable account. Clearing cookies, session expiry, or switching browsers can make a guest round inaccessible. Clearing site storage can erase local progress.

The game does not request GPS access or device-location permission. A map pin is a game guess, not a measurement of where you are.

The iOS app does not send a hardware identifier, an advertising identifier, or Identifier for Vendor, and it does not use UserDefaults for this. It stores a random device token that this server issues, in the iOS Keychain, and sends that token with requests so a guest device can be told apart from a signed-in account. The token is not your Apple ID and not a device serial number. Guess, score, and account requests are the same information described above.

Hosting, security, and other websites

Our hosting provider hosts the website and its server-stored data. Requests necessarily reach the hosting service with connection information such as an IP address. Hosting access and error logs may contain requested URLs, request times, and browser details. The application also uses IP-derived rate-limit records to reduce account abuse.

Game scripts, styles, map data, and the bundled D3 library are served from this website. The interface uses your device’s system fonts. Source and map-attribution links can take you to other websites when opened; those sites handle requests under their own policies.

If you email support, your email address, message, and any attachments are handled by the email services used to deliver and manage that conversation. Please include only what is needed to help with your request.

Your choices, retention, and deletion

You can play without creating an account, sign out, or clear this site’s cookies and local storage in your browser. Clearing browser data does not delete server-stored account records or rounds.

You can delete your account yourself. On the website, open My account → Delete account and confirm with your current password, or use Delete your account without installing the app. In the iOS app, open Account → Delete account. An account created with Sign in with Apple confirms by signing in with Apple again. An account created with Sign in with Google confirms by signing in with Google again on the deletion page. Any other account confirms with its password. Deletion removes your username, display name, password, and recovery codes, signs out every device, removes your completed rounds from the leaderboard and ranked history, removes leaderboard reports and hides tied to the account, and removes your verified and pending email addresses. Official daily results are kept unchanged, so your past rounds remain in our records without a name or sign-in details attached. Deleting the account does not cancel an Apple subscription; cancel it in Settings on your device.

There is currently no automatic deletion schedule for accounts or saved rounds. Rate and storage limits apply to guest play. Guest rounds dated more than 30 calendar days ago, including their answers, may be removed through reviewed maintenance. That cleanup is not automatic and does not remove account-linked ranked results. If you cannot sign in, or for any other privacy request, email support@sixhunches.com. Those requests are reviewed manually, and we may need to verify account ownership before acting. Never email your password or recovery codes.

Server data supports game operation, history, security, and recovery from failures. Backups and hosting logs are separate from live account records, so removal from the live service does not necessarily remove every copy immediately. We can explain the available options and any limits when reviewing your request.

Questions and updates

Contact support@sixhunches.com about this policy. Changes will be reflected on this page with an updated effective date. See also our Terms and Support page.