Privacy Policy
This policy covers wherecast.com and official Wherecast mobile apps that connect to the same service. Wherecast is operated by Burak Ozdemir, a self-employed trader (autónomo) established in Spain, at Calle Puerto 14, 5th floor, 29016 Málaga, Spain. The operator ("we") is the data controller for the information below and uses it to run the game, save progress and protect accounts. Contact us at support@wherecast.com about your information or this policy.
What we collect
- Guest play: a random guest identifier, session identifier, puzzle and guess records, outcomes and timestamps. Guest play is pseudonymous, not fully anonymous: these identifiers let us recognise the same browser or app installation without asking for a name or email.
- Accounts: your email, username, a password hash if you register with a password, verification status, and preferences you provide, such as country, timezone, language and game settings. We do not store your real name. Optional external sign-in provides a provider identifier and email; if the provider also sends your name, we do not keep it. We do not receive your Google or Apple password.
- Mobile sign-in: an account access token, the device label supplied by the app, token creation/usage information and expiry. The server stores a hash of the token. It is not an advertising identifier.
- Technical information: requests may include your IP address, browser or app information, and error or security details processed by our servers and delivery providers. We do not need your GPS location, contacts, photos or advertising identifier to play the game.
- Purchases and support: if you buy an offered premium feature, we keep the customer/order references and entitlement information needed to provide it. Payment providers handle payment details. Wherecast Pro can be bought in the app without an account: the app then gets a random purchase identifier and an access token, of which we store only a hash, together with the purchase status we confirm with RevenueCat and your archive replay progress. We do not ask for your name or email for this. Verified installations can share purchase access. Where Archive synchronization is enabled, restoring the same verified purchase also recovers its unclaimed guest Archive games, including unfinished games. Family Sharing or ownership we cannot verify does not expose another purchaser’s games. If you explicitly link an eligible production Apple purchase to a Wherecast account, we keep that association to provide website Pro; signing in alone does not link it. If you contact support, we receive what you send us.
Guest progress and account sync
Guesses are recorded on our servers as you play, including when you play without signing in. Creating a new account from that guest session saves its available game history to the account, including unfinished games. Signing in to an existing account does not automatically import a device's guest history. Where available in the native app, you can separately choose to keep your server-recorded free guest games and shared guest Archive games. Registration or an explicit import moves eligible games into the account and starts a new empty guest Archive history; signed-out Restore cannot reveal those account games. Existing account progress takes priority for the same puzzle and daily or replay mode, and guest-origin games never gain leaderboard eligibility through transfer. Account games can be retrieved by signing in to the same account on another device.
Personal streaks are calculated from saved games. Guest-started games, practice replays and older games whose origin cannot be verified do not enter leaderboards. Games started while signed in can qualify. We do not import results claimed by browser storage, offline clients or development installations.
Cookies and device storage
The website uses session and security cookies, and a random wc_guest cookie to recover guest progress. The guest cookie is set for up to 365 days and renewed during play; your browser may shorten that period. Signing in can also set a persistent sign-in cookie. Guest history transfer adds no new cookie. Browser storage holds preferences such as units and help settings; it is not the source of your streak.
Mobile clients use session cookies for guest play and account tokens for signed-in requests. Clearing browser or app data can remove access to guest progress; it does not by itself delete server records or an account. Keep access to your account to recover saved account history. We retain server-side hashes of transferred guest/session identifiers to prevent repeated transfers; those hashes do not sign anyone in. Optional transfers also retain a receiving account identifier and a receipt with transferred and skipped game counts so interrupted requests can be recovered without duplicating games.
Why we use information
We use account and gameplay information to provide the service you request, recover progress, calculate statistics, authenticate you and fulfil purchases. We use security and technical information for our legitimate interests in preventing abuse and keeping the service reliable. Where consent is required, we ask for it. Optional email reminders use your selected time and timezone; you can turn them off in your profile. Account verification, recovery and security messages are separate from reminders.
Mobile push reminders have been discontinued. Email reminders remain optional and are controlled in your profile. Older app versions may still contain notification software until they are updated.
Public results and service providers
Leaderboard responses may include your username, chosen country and eligible game statistics. Your email and password are not public leaderboard data. Sharing a result through your device's share controls sends it to the destination you choose.
We use service providers for hosting, storage, delivery, email and security. Cloudflare provides website delivery and image storage in our production setup. Configured email providers deliver account and reminder messages. An app store processes purchases made in a Wherecast app, and RevenueCat receives those purchase records with app and device information so we know which account or purchase identifier has Wherecast Pro. RevenueCat processes them under its privacy policy and identifies the buyer by a random billing ID, not by your email. External sign-in providers also apply their own privacy policies. These services may process information outside your country; applicable data-protection requirements apply to such transfers.
The production website uses Cloudflare Web Analytics to measure aggregate visits, page views and page performance. Cloudflare Web Analytics does not use analytics cookies or local storage and does not fingerprint visitors by IP address or browser information. These analytics apply to the website, not the native apps. Reminder unsubscribe pages are excluded. Website delivery and security may separately process the technical information described above. We do not sell player data or use it for targeted advertising.
Weather is fetched for the game's cities, not your device location. Player account information and guesses are not included in requests to the weather or poster-generation services.
Retention and deletion
We keep account history while the account remains available, unless you request deletion. Guest records have no scheduled deletion date. They stay on the server to support returning play and registration until they move to an account through registration or import, or until you delete them in the app or ask us to. Expiry or removal of a guest cookie is not an automatic deletion request. Technical records, transfer-protection hashes and backups have separate operational retention needs, including security, recovery and any applicable legal obligations.
Earlier versions used OneSignal for mobile push reminders. We have deleted the push registration and delivery records that we stored. Contact support@wherecast.com for requests relating to records held by the former provider.
You can delete your account from the website profile or in the Wherecast app (Profile › Account › Delete account). This deletes the account used across the website and mobile apps. Deletion removes the account, its game attempts, linked sign-in records and account tokens from the active database. A cached leaderboard entry may take a few minutes to disappear. Backup copies may remain until those backups are replaced, and payment providers may retain transaction records for their legal obligations. Signing out or uninstalling an app is not account deletion. In the app you can also delete, without an account, your purchase identifier with its archive progress and your free guest game history. For shared guest Archive history, the app asks you to confirm deletion across the associated installations. This removes the current unclaimed shared games and the requesting installation’s access credential. Other installations keep their verified purchase access and can start an empty guest history. An older app without this confirmation must update before deleting shared history. Installation-local histories are deleted only for that installation. Separately owned account games are not deleted by guest deletion, and Restore cannot recover games already transferred into an account or deleted. It is not a refund; Apple keeps the purchase for later Restore. We retain minimal transaction references, environment, verified ownership status and opaque RevenueCat billing identities needed to maintain purchased access and process restores or refunds. Empty provider customer records are queued for deletion. Account deletion removes its purchase link without canceling the Apple purchase. We keep a hash of the deleted access token or free-guest identifier for 30 days so a repeated deletion request gets the same answer, then remove that hash. Reports about a deleted account can keep its identifier and username until the report is resolved and redacted. The website has no guest deletion control, so contact us to request deletion of guest records or for help with an account request.
Your choices and rights
Depending on the law that applies, you can request access, correction, deletion, restriction, portability or object to processing, and withdraw consent without affecting earlier lawful processing. Contact support@wherecast.com; we may need to verify the requester's identity. You can also complain to your local data-protection authority, including Spain's AEPD. Accounts are not intended for children under 13 or a higher minimum age required where they live; contact us if such a child has provided account information.
Changes
We update this notice when our practices change. Material changes will be brought to your attention through the service where appropriate.
Username reports and blocking
The public-username reporting endpoint accepts reports without an account, cookies or access tokens and does not attach a reporting account. It stores the request identifier, report or block action, target player identifier, optional username snapshot and the reported leaderboard source, category and period. The endpoint accepts only these fields; do not submit passwords, payment data or other private information. Blocking preferences are stored locally by the app; the separate block report is retained for moderation even if you later unblock the player.
Authorized reviewers use moderation records, current account information, related reports, decision reasons and timestamps to investigate abuse and enforce the Terms. Our operations mailbox receives email notifications through our email provider for review by the authorized moderator; the persisted moderation inbox remains the source of truth if email delivery fails. We retain the accepted terms version and a server-generated acceptance time on your account. This processing supports service safety and our legitimate interest in preventing abuse.
Resolved or dismissed report details become eligible for redaction 90 days after the moderation action. Redaction waits while a notification is pending or being sent; it removes the report body, target identifiers, username snapshots and decision notes. Open reports remain available until reviewed and resolved. We retain request identifiers, a cryptographic digest of the submission, receipt identifiers and minimal receipt, notification and decision metadata, including decision types, moderator identifiers and timestamps, without a scheduled expiry, to prevent duplicate reports and maintain an audit trail. Active account suspension records retain the suspension reason, responsible moderator and time for enforcement and review requests. We do not store a reporting account, email, cookie, device identifier or IP address in the report. Trusted network addresses are used transiently for rate-limit counters for up to one hour; separate hosting and access logs follow the technical-record policy above.
Last updated: 2026-11-15