Privacy
1. Service and contact. Koreda! is an ad-supported hidden-object game provided by Dejuworks. It is a general-audience game for players aged 13 and over and is not directed to children under 13. Contact [email protected] about privacy or data requests. When you contact support, we process the contact details and message you supply to answer your request; no automatic retention period is defined for the support mailbox. Availability of ads, purchases and notifications depends on the app version, platform, service configuration and your permissions.
2. Game data. Your progress, found objects and preferences are stored on your device. Guest authentication and progress sync can run automatically when you connect to the internet; you do not need to create an account with a name or email. Linking an account is optional and is explained in section 3. The server stores completed levels, found objects, favourites, opened chapters, achievements, play times, supported settings and sync events with their timestamps and payload digests. These support continued play, synchronisation and duplicate prevention.
3. Identity and security. Firebase Authentication (Google) provides a random anonymous user identifier. The app also generates an installation UUID; this is not your phone serial number or advertising ID. If you choose to link your account with Apple, Google or email, Firebase Authentication processes your email address and, where available, your name; the server also stores them with your player account and uses them to recognise your account and restore your progress. When you link with email, your password does not reach our server and is handled by Firebase Authentication; a message is sent to verify your address. When you delete your account in the app, the Firebase account is deleted and the name and email fields on the server are cleared. The server stores the Firebase ID, player ID, installation ID, session tokens and session/device binding records, accepted terms version and acceptance time. Firebase App Check uses Play Integrity on Android and App Attest/DeviceCheck on iOS to help verify the app and device. Attestation tokens are processed; protected game endpoints require valid verification.
4. Technical data and website cookies. App requests may send language, time zone, platform, app version/build, content manifest version and a request ID. Device records store platform, version, locale, time zone, last-seen time, identity/binding revisions and permission preferences. The website uses essential cookies for session and CSRF security. The server and service providers see IP addresses and technical details such as user-agent during connections; the web session table can store IP and user-agent. Security and error logs may contain technical request details. These support service operation, abuse prevention and troubleshooting; we do not request precise location derived from your IP.
5. Game wallet. The wallet stores energy and hint grants, balances, allocations, temporary spending permissions (leases), receipts and a change ledger. Leases are linked to the installation ID. Ad rewards and purchase entitlements may be linked to verification records. These prevent duplicate spending and sync errors; the game wallet is not a bank account.
6. Google AdMob and advertising. Koreda shows two kinds of ads. Rewarded ads are optional; watching one gives +1 energy or a hint. Ads between scenes are never shown during play; they start after the first 3 completed scenes and appear at most once per 3 completions and at least 180 seconds apart. AdMob (Google) serves the ads. To serve and measure ads and prevent invalid activity, AdMob may process your IP address and the approximate location inferred from it, device and app information, diagnostic/performance data, ad impressions and interactions and, if you allow it, identifiers such as the Android advertising ID or iOS IDFA. To verify a rewarded ad, Google sends our server a signed reward callback; the ad request carries your Koreda customer ID (a randomly generated ID that contains no name or email) and a verification value tied to the reward request. Apart from that callback, AdMob sends us no personal data. Koreda requests non-personalised ads and limits ad content to the Teen (T) rating. Non-personalised does not mean data-free: data and device storage can still be used for measurement, frequency capping and fraud prevention.
7. Ad consent and your choices. In the European Economic Area (EEA), the United Kingdom (UK) and Switzerland (CH), and on iOS where App Tracking Transparency (ATT) applies, Google User Messaging Platform (UMP) shows the consent message. Ads are requested only when UMP allows it; if you decline or withdraw consent, ads and ad-based rewards may be unavailable, and you can keep playing. To change or withdraw consent, where required in your region you can reopen the UMP form in the app under Settings → Privacy and Data → Ad Preferences. This option appears only where UMP requires it; if you do not see it, write to [email protected]. On iOS you can manage the app’s tracking permission in Settings → Privacy & Security → Tracking; on Android you can reset or delete the advertising ID and turn off ad personalisation in system settings (options vary by version).
8. RevenueCat and in-app purchases. Hint and energy packs (consumables) and the one-time Play Ad-Free purchase are made through the App Store or Google Play; the store processes payment and Koreda does not receive card details. RevenueCat manages purchases. RevenueCat receives your Koreda customer ID (a randomly generated ID that contains no name or email) and the purchase receipts from the store; product ID, store, transaction ID and purchase/refund status are processed to verify what you bought and to prevent the same entitlement being granted twice. Play Ad-Free removes only the ads between scenes; rewarded ads stay optional. You can restore store purchases with Restore purchases in the Shop; this brings back only the permanent item (Play Ad-Free), not hint or energy packs. Deleting game data does not automatically delete store purchase history or transaction records a provider must retain; payment and refund requests follow the relevant store’s processes.
9. OneSignal and optional notifications. Notifications are enabled with your explicit choice and operating system permission. OneSignal may process a push token/subscription ID and technical device information to deliver notifications; Koreda may store notification permission status, preferences and subscription ID. You can turn notifications off in app settings or your operating system’s notification settings. Turning them off in the app opts the OneSignal subscription out and withdraws local consent. Refusing notification permission does not prevent you from playing.
10. Content, updates and providers. Scenes and images are downloaded through our CDN (files.getkoreda.app). Cloudflare provides content delivery, network security and storage; Hetzner hosts the API/site. Expo EAS Update may check for app updates on launch and process technical data such as an EAS client/installation ID, platform, runtime/version and update identifiers. When configured, Sentry may provide technical error and performance reporting; server code strips request bodies, cookies and user fields from those reports. Game usage analytics is described in section 12.
11. Sharing and international processing. Data may be transferred to the relevant providers for the game, verification, advertising, purchase, notification, support and infrastructure purposes above. Providers may process data in their own infrastructure and countries; their logs and backups are managed separately from our game database. Google/Firebase: https://policies.google.com/privacy ; AdMob: https://support.google.com/admob/answer/6128543 ; RevenueCat: https://www.revenuecat.com/privacy ; OneSignal: https://onesignal.com/privacy_policy ; Expo: https://expo.dev/privacy ; Cloudflare: https://www.cloudflare.com/privacypolicy/ ; Hetzner: https://www.hetzner.com/legal/privacy-policy/ ; Sentry: https://sentry.io/privacy/ . You can also review the providers and purposes listed in the ad consent form.
12. Retention. Progress, device records and the game wallet are kept until deletion is requested so that play can continue and records remain consistent; the code does not define an automatic maximum retention period for them. Session access tokens normally last 30 days and expired tokens are pruned daily. Web sessions default to a 120-minute idle lifetime; expiry does not mean immediate physical deletion. Game usage analytics: unless you turn it off in Settings → Privacy and Data → Share usage data, the app sends game usage events to Koreda’s own servers to improve the game: app session starts, levels started, completed or failed, hints used, content download results (size in bytes and duration), shop and purchase outcomes, rewarded and full-screen ad displays, and first-run and energy-screen events. Events carry public content keys (level and chapter), the app version, platform and language, and are linked to your Koreda account (anonymous for guests, or the account you linked with Apple, Google or email) and app installation ID. They never contain your name, email, store receipts, prices or advertising ID, are not used for advertising or tracking, and are not shared with ad networks. Turning the setting off stops collection and clears events not yet sent; events already received are deleted after 30 days. Completed deletion requests are pruned after 30 days; the installation identifier is removed from the request on completion. Pending or review-required identifiers are kept only to resolve the request. This app code does not establish a verified retention period for infrastructure logs/backups; contact us for those details.
13. Children under 13. Koreda is not offered for use by children under 13, and we do not intend to knowingly collect their personal data. If we learn that a player is under 13, we will review the situation and take steps to stop the relevant use and delete associated personal data, subject to necessary legal retention and ownership verification. A parent or guardian can contact [email protected] privately and use the Data deletion page. Do not include a child’s name, date of birth or other unnecessary personal details in support messages. Being 13 or older does not mean you can independently consent to ad personalisation or data processing in every country; applicable age and consent rules also apply.
14. Security and your rights. Data is transferred over HTTPS; protected API endpoints require session and app verification. The deletion form uses session security and request limits. No internet service can guarantee absolute security. Where applicable, you can request access, correction, deletion, restriction/objection or portability at [email protected]; we may need to verify that the request concerns your installation.
15. Data deletion. You can delete guest data in the app with Delete my data on the Privacy and Data screen. If you cannot access the app, use the form on the Data deletion page. Share your installation ID only privately: someone who knows it can submit a deletion request. Deletion through the form does not remove offline data on your device, and playing online again afterwards can create new server data. If you cannot access the ID or have a shared/linked account, contact [email protected]. When you delete guest data in the app, your player record on the server is removed completely. For guests with a store transaction or rewarded ad record, and when you delete a linked account in the app, we keep a minimal deletion marker containing Firebase/player IDs and legal acceptance dates to prevent identity reuse, as well as detached wallet evidence (including lease installation IDs); no automatic pruning period is defined for these records. The guest deletion form’s scope and exceptions are explained on the Data deletion page.
16. Policy changes. We update this page and its revision date as the service changes. A policy update alone does not grant advertising or notification consent. Contact [email protected] with questions or data requests.
Home