At a glance
- House Duck (Junhee Choi, Germany) is the controller. Contact: support@houseduck.in.
- We process what we need to run and protect the games, accounts, purchases and rankings (sections 2 and 3).
- Usage analytics, personalised ads and customer match lists for ads are used only with your consent, which you can withdraw at any time.
- Aggregated and anonymised statistics that do not identify you are used to improve our games and for business purposes (section 3, “How we use data”).
- Data is mainly stored on servers in the EU (Ireland); some providers process it outside the EU (section 5).
- Your rights to access, correct, delete and object are in section 9.
- The details for 10key Survival are in section 13; tap an item to expand it.
1. Scope and Controller
This Policy applies to the website houseduck.in and to the games and apps that Junhee Choi operates in Germany under the name House Duck (together, “our games”). The titles currently covered are the mobile game Quirky Ball (Android, iOS) and the arcade game 10key Survival. Future House Duck titles are covered by this Policy as well. Before a title processes data in a materially different way, we will add that processing here or publish a short title-specific supplement, which then applies together with this Policy for that title.
Sections 2 to 12 describe Quirky Ball 2.0.0 and later and the website, unless stated otherwise. Section 13 describes 10key Survival and states which parts of sections 2 to 12 also apply to it. Section 14 describes support requests and House Duck’s internal operations tools; it applies to all our games and the website.
Controller: Junhee Choi, House Duck (하우스덕)
Address: Ringstr. 23, 61476 Kronberg im Taunus (Hessen), Germany
Email: support@houseduck.in
Phone: +82 10 7620 3959
This policy is a notice about personal-data processing. Acknowledging it or playing a game does not replace consent to optional analytics, advertising, or tracking. Consent for personal-data processing and consent for device storage/access are assessed separately under applicable law.
2. Information We Process
| Information | When and why it is processed |
|---|---|
| Account identifiers (guest identifier (UID) and identity-provider identifier) | A guest account is created when Quirky Ball is first used. If you optionally link a Google account (Android and iOS) or an Apple account (iOS), the provider identifier is stored for sign-in, account linking, and loading the same account on another device. If you sign in with an account that is already linked to another game account, that account’s saved progress is loaded and the current guest progress on the device is replaced. |
| Email address and profile name | Processed only to the extent you choose Google Sign-In or Sign in with Apple and the provider discloses them. Apple may provide a private relay address. To prevent invitation abuse, the server may check whether two linked accounts share the same sign-in email. Only with your separate consent is it also used for personalised ads as described in section 3, “How we use data”. |
| Game and account data | Nickname, display code, user-selected country/faction, profile icon, nameplate and other owned/equipped customization, progress and saved game state (for Quirky Ball, for example lab progress and run results), virtual currencies and items (such as gems, reagent and tickets), rankings, friends and gifts, invitation codes and invitation status, mailbox items, attendance and missions. Stored on the device and in Supabase. |
| Fair-play and reward records | Server-issued run tickets, play and reward records, and plausibility checks of time, score and currency changes, used to grant rewards correctly and to prevent cheating, duplicate rewards and abuse. |
| Purchase data | Product ID, store transaction ID or purchase token, purchase status, platform, the game account the purchase is linked to, restoration/refund status, and entitlement. House Duck does not receive full card or bank-account details. |
| In-app reports and support requests | If you send a Quick Report in the app settings, the text you enter (up to 2,000 characters) is stored with your account ID, app version, build number, platform and language so that we can investigate the problem; we see your current nickname next to the report. Support emails and the contact details needed to reply are processed to answer the request (see section 14). Please do not include passwords or payment details. |
| Advertising and device data | The Google Mobile Ads SDK (AdMob) may process IP-derived approximate location, app/ad interactions, diagnostics, advertising ID, App Set ID, and similar identifiers for ad delivery, measurement, error handling, and fraud prevention. |
| First-party usage analytics stored in Supabase (optional) | Only with the optional usage-analytics consent: app start/session, screen and button interactions, game start/end, ad request/impression/reward, purchase flow events, app version, platform, time-zone offset and distribution channel. This includes basic stability diagnostics: the code location (file and line) of client errors, and a flag when the app ended unexpectedly while it was open on screen (a crash or forced close), not when you closed it from the app switcher. Random installation/session identifiers are used and kept separate from the account UID; these events do not include the advertising ID. |
| Optional Firebase Analytics | Only with the same optional consent: Firebase Analytics may process automatically collected events, app-use information such as tutorial completion, and app/device information including an app instance ID. Declining does not restrict the game, and the choice can be changed or withdrawn at any time in the app settings. |
| Notification data | If you allow notifications: the push token and installation identifier, account link, platform, app version, language and delivery/open status. Google (Firebase Cloud Messaging, FCM, on Android), Apple (Apple Push Notification service, APNs, on iOS) and Supabase may process them for delivery, device registration and troubleshooting. Notification permission is optional, can be managed in device settings and is separate from the optional usage-analytics consent. Turning notifications off does not by itself mean that earlier tokens or history are erased immediately. |
| Device settings | Language, sound, vibration, graphics settings, your consent choices and the calculated age band are stored locally on the device. |
| Website network and storage information | The website is delivered through GitHub Pages. A browser makes requests to GitHub for page resources and delivery/security logs, may request YouTube thumbnails from Google at i.ytimg.com, and may request Supabase public endpoints: one returns public version information, and another returns aggregate homepage game score/play-count totals only, not individual record data. On the support page, after a visitor picks 10key Survival, the browser asks a third Supabase public endpoint once for the game’s public settings, to show the current link for public questions on YouTube; the request carries no account, player identifier or anything the visitor typed, and selecting that link opens YouTube, where comments are public. On Korean-language pages only, the browser loads the Kakao JavaScript SDK from t1.kakaocdn.net when a visitor hovers over, touches or focuses the KakaoTalk share button, or opens the share sheet; it is never loaded when a page opens. When a visitor shares through KakaoTalk, Kakao Corp. (South Korea) receives the shared link, picture and text and processes them under its own Kakao Privacy Policy. BGM files in the music panel are served by this website and load only when a visitor manually starts playback. A separate external YouTube playlist link opens that service when selected. Recipients of those requests may process IP address and HTTP request metadata. When a visitor selects a language, the house_duck_site_language key may be stored in browser localStorage. The email button opens the visitor’s email application; the website does not send the message to a website backend before the visitor sends it from that application. |
Our games are not designed to collect precise location, contacts, photos, camera, microphone, or other information unnecessary for the game. Sharing a result card uses your device’s share sheet; we do not receive what you share.
3. Purposes and Legal Bases
- Providing the games, accounts, account linking and loading, rankings, Friend features, mailbox, invitations, purchases, restoration, in-app reports and support: contract performance or pre-contractual steps (GDPR Art. 6(1)(b)).
- Payment, refund, fraud checks, and legally required records: legal obligation (Art. 6(1)(c)) and legitimate interests (Art. 6(1)(f)).
- Security, fair play, stability, and error investigation necessary to operate and protect the service: legitimate interests (Art. 6(1)(f)).
- House Duck first-party usage analytics stored in Supabase (including the stability diagnostics above), Firebase Analytics, and the use of the tutorial-completion event for ad-campaign measurement: separate optional consent (Art. 6(1)(a)), withdrawable at any time.
- Personalized advertising and processing that requires tracking consent: consent (Art. 6(1)(a)), which may be withdrawn at any time.
- Limited/non-personalised advertising and fraud prevention: consent or legitimate interests where permitted by applicable law.
The legitimate interests are protecting accounts and transactions, preventing fraudulent scores or duplicate rewards, investigating errors, handling reports efficiently, and maintaining service stability. Random installation/session identifiers do not by themselves make data anonymous. Behavioural analysis such as screen navigation or button interactions is not treated as essential security processing, and accepting the terms alone does not satisfy any required consent.
How we use data
This applies to all our games and the website.
- Aggregated and anonymised data: House Duck may use data that has been aggregated or anonymised so that it no longer identifies anyone (for example play counts, level distribution, usage by country, ad performance) for any purpose, including improving our games, planning new games, business analysis, marketing material and published statistics, and discussions with publishers and partners. Anonymised data is not personal data.
- Use across House Duck games: Account and usage information processed for one game may also be used to run, improve and develop other House Duck games and services (legitimate interests, Art. 6(1)(f) GDPR). Information for which this Policy sets a narrower purpose (for example the technical signals in section 13 or support email in section 14) stays within that purpose. Your right to object is described in section 9.
- Personalised ads using a linked account: If you link your game account to a Google or Apple account and separately agree to this in the game, House Duck may pass the email address of that account, as a SHA-256 hash, to the customer match list of an ad platform such as Google Ads, to show you ads for House Duck games and to find other people with similar interests. Where a platform requires a separate permission for this (for example Apple’s App Tracking Transparency on iOS), House Duck uses the data for this only after that permission. The legal basis is your consent (Art. 6(1)(a) GDPR). Consent is optional, declining does not affect the game, and you can withdraw it at any time in the app settings or at support@houseduck.in; the address then leaves the list at the next sync. Accounts linked before this consent are not used for this purpose, and neither is information about users under 18. Apple relay addresses may not match.
- News about House Duck games: If you agree, we may email you about new House Duck games and updates. You can stop these emails at any time with the unsubscribe link in each email.
- Business transfers: If House Duck’s business or a game passes to another operator through a merger, acquisition or transfer of business, user information may be transferred to the new operator so that the game can continue, and the new operator processes it within the scope of this Policy. Where the law requires, we will tell you in advance.
4. Service Providers and Recipients
House Duck does not sell personal information to data brokers for money. However, disclosures for personalised advertising or ad measurement may fall within broader statutory definitions of sale or sharing in some jurisdictions; applicable choices and statutory rights remain unaffected. The following providers may process information as independent controllers or processors as applicable.
For customer data hosted in Supabase, House Duck remains the controller and Supabase processes that data as a processor acting on House Duck's instructions. Supabase's published Data Processing Addendum provides information about these roles.
| Service | Purpose |
|---|---|
| Supabase | Authentication, account linking/synchronisation, game state, rankings/social features, mailbox, invitations, purchase entitlements/reward state, in-app reports, notification registration, first-party analytics storage, the public-version check, and aggregate homepage game score/play-count totals |
| Firebase Analytics and Google Ads (Google affiliates) | Optional app-usage analytics after you consent; with that consent, the tutorial-completion event may be used by Google Ads to measure our app-install campaigns (conversion measurement). On the 10key Survival web pages, the Google tag of Google Ads measures in consent mode whether a visit from our ads leads to a pre-registration, and customer match lists of SHA-256-hashed email addresses given with consent are used to show House Duck ads (sections 3 and 13) |
| Google AdMob and User Messaging Platform (UMP) (Google affiliates) | Rewarded, interstitial, banner and native ads, and advertising-consent management |
| Google Sign-In, Google Play Billing, Firebase Cloud Messaging (Google affiliates) | Optional sign-in, Android in-app purchase, restoration and refund processing, Android notifications |
| Google Workspace (Gmail) and Google Identity Services (Google affiliates) | Receiving, storing and answering email sent to support@houseduck.in and business@houseduck.in; staff sign-in with Google to the House Duck operations console (section 14) |
Google YouTube thumbnail service (i.ytimg.com) | Delivery of YouTube thumbnail images requested by the browser |
| Sign in with Apple, App Store/StoreKit, APNs (Apple affiliates) | On iOS, optional sign-in, in-app purchase, restoration and refund processing, and notifications |
| GitHub Pages | Static hosting, website-served BGM files, and security/delivery logs for houseduck.in |
| Resend (Plus Five Five, Inc.) | Sending the 10key Survival pre-registration emails (the receipt and the launch email) as House Duck’s processor (section 13) |
| Kakao (Kakao Corp.) | KakaoTalk share on Korean-language website pages: the Kakao JavaScript SDK (t1.kakaocdn.net), loaded only when a visitor hovers over, touches or focuses the KakaoTalk share button or opens the share sheet, and the delivery of the link, picture and text the visitor shares |
Quirky Ball uses Google AdMob as its only ad network; no other ad network or mediation SDK is active. If we add one to any of our games, we will update this Policy and the in-app notice before it is used.
- Google Privacy Policy
- Firebase Privacy and Security information
- Apple Privacy Policy
- Supabase Privacy Policy
- GitHub Privacy Statement
- Kakao Privacy Policy
- Resend Privacy Policy
5. Processing Countries and International Transfers
House Duck operates and processes personal data in Germany. The primary Supabase database for our games is in Ireland (AWS eu-west-1). That is where the database is, not a promise that all support, delivery or log processing stays in Ireland; a primary database location or a company’s address is not a full list of a provider’s processing countries. The table separates the confirmed primary location from each provider’s published processing scope, and the linked official pages give each recipient’s contact route.
| Recipient/service and contact route | Countries and scope | Data, purpose, and timing |
|---|---|---|
| Supabase (Supabase DPA; privacy@supabase.io) | Primary database: Ireland. The published DPA names Supabase Pte. Ltd. (Singapore); Supabase, Inc. is listed as a support subprocessor. Global support and subprocessor processing are separate. | Guest/account identifiers, game state, purchase entitlements, in-app reports, and first-party analytics. Encrypted network transmission/storage when the app runs, authenticates, synchronizes, or records gameplay. |
| Google services (Google, Firebase) | United States and Google’s published global facilities. Google LLC, Google Ireland Limited, or other applicable affiliates process data depending on the service and user’s residence; storage is not Germany-only. | Information for optional analytics and ad measurement, ads/consent, optional sign-in, Android purchases, support email (Google Workspace), staff sign-in to the operations console, website thumbnails, the Google tag on the 10key Survival web pages, and customer match lists of hashed email addresses given with consent. Sent when the relevant feature is used, subject to any required separate consent. Notification installation identifiers/tokens and delivery/open status may also be processed during notification device registration, delivery, and confirmation. |
| Apple services (Apple) | Apple states that data is generally stored in the United States. Apple Distribution International Limited in Ireland controls personal data relating to EEA, UK, and Swiss users; service-specific entities may differ. | Information for optional Apple sign-in, iOS purchases, restoration, and refunds, sent when you use those features. Notification installation identifiers/tokens and delivery/open status may also be processed during notification device registration, delivery, and confirmation. |
| GitHub Pages (GitHub) | United States and other countries disclosed by GitHub. GitHub, Inc., GitHub B.V., or the applicable entity processes the information. | IP addresses and request metadata when pages, images, or music are requested, for website delivery and security/delivery logs. |
| Resend (Resend Privacy Policy) | United States. Plus Five Five, Inc. processes the information as House Duck’s processor; transfers rely on Resend’s EU-U.S. Data Privacy Framework certification and the Standard Contractual Clauses. | Email address and email content of the 10key Survival pre-registration emails (the receipt and the launch email), when they are sent. |
| Kakao (Kakao Privacy Policy) | South Korea. Kakao Corp. processes the information under its own privacy policy. | IP address and request metadata when a Korean-language website page loads the Kakao JavaScript SDK (only when a visitor hovers over, touches or focuses the KakaoTalk share button, or opens the share sheet), and the link, picture and text the visitor shares through KakaoTalk. |
Supabase lists its subprocessors under Supabase subprocessors; retention is described in section 6.
Direct collection by House Duck as an overseas operator is distinct from subsequent disclosure, processing outsourcing, or storage with another overseas provider. Transfers subject to the Korean Personal Information Protection Act require a valid basis for the particular processing, such as separate consent or the statutory disclosures for outsourcing/storage necessary to perform a contract. Reading this notice or playing a game is not separate consent to international transfers.
Transfers outside the EU/EEA require an applicable adequacy decision, Standard Contractual Clauses (SCCs), or another valid safeguard. Supabase’s published DPA contains SCCs; Google, Apple, and GitHub describe their transfer mechanisms in their official policies. Kakao Corp. is in South Korea, for which the European Commission has adopted an adequacy decision. Contact support@houseduck.in for the countries, recipients, basis, and a copy of safeguards applicable to particular processing.
Optional analytics can be declined or withdrawn in the settings, advertising choices are managed in Ad Privacy Settings, and optional sign-in can be skipped. The server-based game services cannot readily be provided without the required Supabase account and synchronisation processing. To object or to request deletion, contact support; we will explain which features are affected in your case and what you can do. Making a rights request is not in itself a reason for adverse treatment.
6. Retention
- Detailed play, season and weekly records and account-separated first-party analytics events: normally 28 days from the record-specific time explained below.
- Account, current synchronised state, best records, progress and fair-play/reward records: until account deletion.
- In-app reports: while needed to handle the report, and no longer than until account deletion.
- Mailbox items: deleted 90 days after they are claimed or expire.
- Entitlements, transaction references, refund and fraud records: as needed to support the purchase or for the applicable statutory retention period.
- Support emails: as needed to resolve the request and handle disputes.
- Local settings: until the app or device data is deleted.
- Information independently held by store, sign-in, advertising, analytics, and hosting providers: under each provider's retention policy and settings.
How the periods are calculated
Daily cleanup removes data older than 28 days based on the play time for detailed gameplay, the update/achievement time for season/weekly records, and server receipt time for first-party analytics. Because the cleanup runs once a day, deletion can normally happen up to one day after that threshold. The 28-day window does not apply uniformly to Firebase analytics, push tokens, or providers’ independent logs.
Events waiting in the app to be sent (the app-managed unsent first-party analytics queue and the pending Firebase custom-event queue) expire 24 hours after they were created. Expired entries are discarded at the next queue check or before sending, so deletion does not happen at exactly 24 hours while the app is closed. Both queues are also discarded when you withdraw consent or switch accounts. The 24-hour rule does not limit the Firebase SDK’s internal storage or providers’ own retention, and it does not guarantee that information already sent is deleted immediately.
7. Account Deletion
You can delete your game account in the app under Settings → Delete Account or follow the external deletion instructions.
- Deleted and not recoverable: the account profile, synchronised state, progress, friends and social connections, mailbox, invitations, in-app reports and fair-play records linked to the account. A Sign in with Apple link is also revoked with Apple.
- Some detailed play records may remain until the 28-day threshold described in section 6 and the next daily cleanup, and are then deleted automatically.
- Minimal records strictly required for legal obligations, payment/refund handling, fraud prevention, or legal claims may remain until those purposes end.
- Store transaction records managed independently by Apple or Google are not deleted with the game account; restorable purchases can later be restored to a new game account as described in the Terms.
8. Advertising and Analytics Consent Choices
- Optional usage analytics: one optional choice jointly controls House Duck first-party usage analytics stored in Supabase (including the stability diagnostics in section 2) and Firebase Analytics (including automatically collected events and tutorial completion). Users aged 18 or over make an explicit choice that is not preselected, separate from required terms acceptance and advertising consent. Declining does not restrict the game. Essential account, currency, transaction, and security processing is separate.
- The choice can be changed or withdrawn at any time in the app settings (“Optional usage analytics”). Withdrawal stops future collection and transmission for both optional analytics systems, discards the app-managed unsent queues, and resets the Firebase Analytics data on the device. It does not affect processing lawfully completed before withdrawal; deletion of information already transmitted follows sections 6 and 9.
- Ad-campaign measurement: we promote Quirky Ball with Google Ads app campaigns. Only if you gave the optional usage-analytics consent, the Firebase tutorial-completion event may be used by Google to count how many installs from those campaigns finished the tutorial (conversion measurement). Google may link this to its own advertising data under Google’s policies. Without that consent, no such event is sent.
- Older app versions: the Firebase-only notice and setting in older Quirky Ball 1.x versions such as 1.1.2 (build 53) control Firebase Analytics only, not first-party analytics stored in Supabase. A previous Firebase-only ON choice does not retroactively extend to the combined scope; a fresh explicit choice on the new notice is required.
- Ads: Quirky Ball shows Google AdMob rewarded, interstitial, banner, and native ads. A Google UMP message may be shown in regions that require consent, including the EEA, UK, and Switzerland. On iOS, Apple’s App Tracking Transparency (ATT) prompt is shown separately when cross-app tracking permission is requested.
- Where required, you can reopen Ad Privacy Settings in the app settings and can also manage advertising identifiers and tracking in device settings. Declining advertising consent does not prevent gameplay, but rewards conditional on completing an ad view may be unavailable.
- Whether advertising is personalised, limited, or non-personalised does not by itself settle whether consent is required. The requirement depends on applicable law and the particular storage or access to a device. In Germany, TDDDG Section 25 may require consent for applicable storage or access.
9. Your Rights
Subject to applicable law, you may request access, rectification, erasure, restriction, portability, objection, or withdrawal of consent by contacting support@houseduck.in. For requests to which the GDPR applies, we normally respond within one month. Where necessary because a request is complex or numerous, we may extend that period by up to two further months and will tell you within the first month, including the reasons. The right to lodge a complaint with a supervisory authority is unaffected. The competent authority in Hesse is Der Hessische Beauftragte für Datenschutz und Informationsfreiheit.
You may object to processing based on legitimate interests on grounds relating to your particular situation, and at any time to processing for direct marketing. Withdrawing analytics consent or resetting the device SDK does not mean that all previously stored server data is immediately erased; contact support separately about historical deletion. Korean users may also seek help through the personal-information complaint service (118) or the Personal Information Dispute Mediation Committee.
10. Children's Privacy
Our games are not directed to children under 14, or a higher minimum age required by local law. In Quirky Ball:
- you cannot enter the game before confirming your age (unknown age: 0) or if you are under 14;
- users aged 14–17 can play, but ad SDK/Google UMP requests and optional usage analytics are disabled for them;
- users aged 18 or over can proceed to the standard advertising-consent flow after accepting the required terms; ads are not requested without the required consent.
You select your birth year and month on the age-confirmation screen, and the age band is calculated only on the device. The day of birth is not requested, and the selected year/month is not saved or transmitted. Because the day is unknown, the age-14 and age-18 thresholds are conservatively treated as met only from the month after the relevant birth month. Only the calculated band is stored locally (0: unknown, 14: ages 14–17, 18: age 18 or over). This does not replace identity/age verification or any required parental authorization. If we learn that information from an underage user was processed, we will verify and delete it.
The game’s age-14 requirement is separate from the age for data-processing consent. Where local law requires parental or guardian authorization for consent-based processing, that authorization is required. In Germany, online consent-based processing covered by GDPR Article 8 generally requires parental authorization below 16; this is not a blanket prohibition on all gameplay. Contact support about children’s data.
11. Security
House Duck uses reasonable safeguards including TLS, access controls, Supabase Row Level Security, least privilege, server-side purchase verification with Apple and Google, and duplicate-transaction controls. No transmission or storage method can be guaranteed completely secure.
12. Required Information and Automated Decisions
A guest UID, basic game state, and the Supabase-backed operations that store and synchronize them are required to provide Quirky Ball. Supabase-backed usage analytics and Firebase Analytics are optional: they can be declined or withdrawn together, and declining does not restrict the game (section 8). Without optional sign-in or advertising consent, some features (for example friends, invitations or loading your account on another device) or personalised advertising may be unavailable. Automated fair-play checks may withhold a reward or a ranking entry that fails a plausibility check; you can ask support for a human review. House Duck does not make solely automated decisions producing legal or similarly significant effects.
13. 10key Survival
10key Survival is a single-player arcade game in which you steer a 3D numeric keypad over a board of keyboard keys. It is offered through platforms and stores; “the platform” below means the platform or store through which you play or obtained 10key Survival (for example itch.io, Nekoland, GamePix, Google Play or the Apple App Store). Use of the game is governed by the 10key Survival Terms of Service.
This section describes what House Duck processes for 10key Survival:
- on every platform: play, saves and the online rankings;
- in the web versions (itch.io, Nekoland and GamePix), also the guest account for the online ranking (on itch.io, and in newer versions on Nekoland, it can also send a 1:1 inquiry) and, on itch.io and in newer versions on Nekoland, the technical signals described under “Crash reports, daily usage counts and run records”;
- in the Android and iOS apps, also the full House Duck guest account, the game progress and balances kept with it, daily and weekly quests, social features such as the friends list, gifts and mailbox, problem reports and in-app purchases.
Sections 1, 9 and 14, the statements about Supabase in sections 4, 5 and 11 and, for in-app purchases, the statements about Google Play Billing and the App Store in sections 4 and 5 also apply to 10key Survival. The rest of sections 2 to 12 describes Quirky Ball and the website and applies to 10key Survival only where this section refers to it.
Play and saves
In the web versions (itch.io, Nekoland and GamePix) and for players under 14 in the Android and iOS apps, your progress (levels, upgrades and the in-game parts called “scrap”), your gems and other in-game items, any modules and your settings are saved only on your device or in your browser’s storage. House Duck does not receive this save; on Nekoland, Nekoland’s own platform also keeps a copy of it (see “Web version on Nekoland”). The guest account of the web versions (see below) is used only for the online ranking and, on itch.io and in newer versions on Nekoland, the 1:1 inquiry, and holds none of it. In the Android and iOS apps without an account, the game can be played offline.
With a House Duck guest account in the Android and iOS apps (see below), our server keeps your game progress and balances with the account and decides every purchase or spend inside the game, so that they cannot be duplicated or changed on the device. Starting a run needs an internet connection: the app first asks our server for a ticket for the run, and the scrap and gems the run earns are booked once against that ticket (a run that ends offline is sent later, up to 7 days after it started). The app keeps a copy of the account’s progress in its save to show it; your settings stay only on the device. What our server keeps for the guest account and for purchases is described below.
Online rankings
10key Survival has online rankings stored on House Duck’s server at Supabase, in the same House Duck project as our other games but in a separate part (schema) of the database. The game shows the board of the current season and the board of the last season (newer versions also the board of the season before last). A season is one calendar quarter and starts on January 1, April 1, July 1 and October 1 at 09:00 UTC (the current season runs from October 1 to December 31, 2026). For each player the server also keeps the player’s all-time best, which is used for the player’s profile.
- Viewing the boards: the game requests the public board entries (rank, nickname, score and level) without sending an account or player identifier. Like any web request, these requests carry your IP address and HTTP request metadata, which are processed to deliver the response and to protect the server. When the game starts, it also reads a small settings file from this website (
houseduck.in/10key/config.json, delivered by GitHub Pages, section 5) in the same way, without any identifier. - Sending records in the web versions (itch.io, Nekoland and GamePix): when a run is finished, the game sends its result to our server under the nickname of your guest account (see “House Duck guest account” below) and reads the boards from our server. Besides the ranking records and the requests of the guest account, the itch.io version (and, in newer versions, the Nekoland version) sends only the technical signals described under “Crash reports, daily usage counts and run records” and the 1:1 inquiries you send yourself (see “House Duck guest account”); the GamePix version and older Nekoland versions send nothing else.
- Sending records in the Android and iOS apps: results are sent with your House Duck guest account (see below) and shown under its nickname.
- Before 10key Survival offers ranking sign-in on another platform or processes other data, we will update this section.
| Information (players whose results are sent) | Details |
|---|---|
| Player identifier | The login ID of your guest account. |
| Nickname | The nickname of your guest account. It is shown publicly on the boards. |
| Player record | When your record was created and when you were last seen (in the apps also when the app checked your account at start while online). |
| Best scores | Your best result in each season and your all-time best: score, level, play time and when it was achieved. |
| Ranking run records | Records of submitted runs (one play from start to end), used against cheating: score, level, play time, depth, scrap, combo, number of skills, how the run ended, game build, platform name and an anti-cheat flag. |
| Input-rhythm summary (newer versions) | Sent with each ranking run by newer versions of the game (for example the Android and iOS apps) to detect macros and other automation, in numbers only (counts and shares), such as the number of key presses, the share of the gaps between presses that falls into the single most common timing band, the number of screen touches and the share of touches on the single most repeated exact screen point. It contains no information about which keys were pressed, no text and no touch paths. It is kept with the ranking run record; when a run is tagged, its numbers can also be kept in a review note (see “Security and automated checks” and “Retention”). |
| Review notes | When a run is tagged as likely automated, or an account shows anomalies in its currencies or data, a short note for the review by a person, for example the tag, the counts behind it and the result of the review. |
10key Survival has no chat and no user content other than the nickname shown on the boards, and it is not designed to collect precise location, contacts, photos, camera or microphone data.
App and device integrity checks (for example Play Integrity on Android): the app can ask the platform’s integrity service for a signed token that states whether the app and the device are genuine and have not been tampered with, and send that token with a request, for example when the game sends a finished run to the rankings or when our server verifies an in-app purchase. On Android this is currently Google’s Play Integrity service. House Duck uses the result to protect the rankings, purchases and players, for example to detect tampering, cheating and fraud; the platform provider (for example Google) receives the integrity request and processes it under its own terms and privacy policy (sections 4 and 5). The iOS apps and the web versions currently do not send such a token.
House Duck guest account
The Android and iOS apps use a House Duck guest account that holds your nickname, game progress, balances and purchases. The web versions (itch.io, Nekoland and GamePix) use a guest account only for the online ranking and, on itch.io and in newer versions on Nekoland, the 1:1 inquiry (see “1:1 inquiries” below): when you choose a nickname, the game signs in anonymously at Supabase Auth (no email address, no password, no phone number) and keeps your nickname with that login, so that your finished runs can be shown on the boards under it. That account holds only your nickname and your ranking results (on itch.io and in newer Nekoland versions, our server also notes the account next to the technical signals sent while you are signed in; see “Signals linked to a web guest account” under “Crash reports, daily usage counts and run records”); your progress, gems, other in-game items, modules and upgrades stay in your browser’s storage and are not sent to House Duck. Its sign-in tokens are kept in your browser’s storage and are sent only to House Duck’s server.
From here on, this part describes the apps. At the first start the app asks you to agree to the Terms of Service and this Policy and to choose a nickname. It asks for your birth year and month once, at your first visit to the SHOP (and before any purchase), and works out your age band on the device (under 14, 14 to 17, or 18 and over; your birthday month counts as not yet reached, because the day is not asked). The year and month themselves are not saved and not sent.
- Creating the account: after you choose a nickname, the app signs in anonymously at Supabase Auth (no email address, no password, no phone number) and creates your 10key Survival account on our server. If you are offline, the app keeps the guest account on the device and creates it on the server the next time it can.
- 14 and over: the account stays, and your age band is added to it.
- Under 14: no account is kept. The app deletes the online account on our server in the same way as an account deletion (see “Deletion and your rights”) and forgets the login; you play on without an account, your progress stays only on the device, and no records about you are sent. The game may still load the public boards and its settings file as described above, without any identifier, and, like every player, may send the anonymous basic crash report and app issue reports described under “Crash reports, daily usage counts and run records”.
| Information (guest account) | Details |
|---|---|
| Login ID | A random identifier that Supabase Auth creates for the anonymous login. It identifies your account on our server and the purchases bound to it. |
| Sign-in tokens | An access token and a refresh token that keep you signed in. They are stored only in the app’s save on your device and are sent only to House Duck’s server. Supabase Auth keeps the records it needs to run the login, for example when it was created and last used and, for active sessions, the IP address and the app’s user agent. |
| One-device session | Information that lets our server keep one device at a time signed in to your account, such as a random session code that the app makes at each sign-in and a label for the kind of device (for example “iPhone” or “Android”). When you sign in on another device, the earlier device is signed out at its next check. The session code is not your login ID. |
| Account record | Your nickname (at least 2 letters or digits, at most 12 Korean, Chinese or Japanese characters or 18 other ones; unique, shown on the boards), your age band (14 or 18, once you have answered the age question), the version of the Terms you accepted and when you agreed, when the account was created, and when and how often you changed the nickname. |
| Rankings | The player record, best scores and run records described above, under your nickname. |
| Game progress | The levels of your upgrades, part unlocks and robot parts, the number of runs and the best score that our server booked, gameplay statistics such as how many times each of the ten number keys has been pressed in total, whether a run of yours has reached the robot, and when the account moved to progress kept by the server; from app versions before October 30, 2026 also the progress they synchronised (highest levels and unlocked items). |
| Balances | Records of the scrap, gems (see “In-app purchases”) and Rare Parts your account received and spent: event ID, amount, reason, reference, time and, for events sent by the app, the time on the device. Your balance is the sum of these entries. Our server books the scrap and gems earned in runs, the free daily gems, the one-time welcome gifts and the spends it allows (upgrades, Rare Parts, revives and the ROBOT PACK). |
| Modules | The fragments you hold of each module and the grade they give; and the answer to each module draw (which fragments it gave), stored under the draw’s random request ID so that a repeated request is never charged twice. |
| Run tickets | One entry per run started: a random run ID, the start time and, once the run is booked, when and what was booked (scrap, gems, play time and whether a limit was applied). |
| ROBOT PACK offer | After a run reaches the robot, the 72-hour window of the lower ROBOT PACK price for your account: when it opened, when it ends and the run that opened it. |
| Quest rewards | If you claim the reward of a daily or weekly quest in the app: your login ID, the quest ID, the UTC day or week of the quest and the reward (in-game parts, gems or module draw tickets), so that each reward is granted only once. How far you have come in a quest is counted on your device only and is not sent. |
| 1:1 inquiries (problem reports) | If you send a 1:1 inquiry (SETTINGS → INFORMATION → CONTACT → 1:1 INQUIRY) in the Android or iOS app with your guest account, or in the web version on itch.io (and in newer versions on Nekoland) while you are signed in with its ranking guest account (the GamePix version and older Nekoland versions cannot send one, and without a guest account no inquiry can be sent): your text (up to 500 characters), the email address you give for the reply, the app version and build, the platform, the device model, the game language, your login ID and the time. Newer versions also add, at most 2 KB in all, the situation the inquiry was written from: the session code, the state of the run and the save summary described under “Situation at the time of a report (newer versions)” (in “Crash reports, daily usage counts and run records”) and the last 10 entries of the short trail of steps with the game action codes. With the session code, staff can find the crash reports and app issue reports of the same session, as described under “Crash reports, daily usage counts and run records”. These items are deleted together with the inquiry. At most one an hour and five a day. Only House Duck staff can read them, and the email address is used only to answer that inquiry. The answer is sent by email from support@houseduck.in; from then on it is handled as a support email (section 14). TALK PUBLICLY ON YOUTUBE in the same window only opens YouTube; what you post there is governed by Google's policies. |
Nicknames are checked automatically against a list of offensive and misleading words; a refused name must be changed. You can change your nickname in the app while online (your profile at the top left of the home screen, then Account → Change name).
Linking Google or Apple (optional): in your profile (Account) you can link the guest account to a Google account (Android and iOS) or an Apple account (iOS), so that you can load the same account on another device or after logging out. The sign-in runs on Google’s or Apple’s own sign-in page. Supabase Auth then stores the identifier that Google or Apple gives for your account and, where the provider shares them, your email address and name (Apple may share a relay address instead of your email address). House Duck uses them for signing in to this account and, only if you separately agree in the game, for personalised ads (customer match) as described in section 3, “How we use data”.
Logging out (Account → Log out) ends the session, and the device forgets the guest account and your age answer; the next start asks again. A guest account that is not linked to Google or Apple cannot be signed back into, because it has no password and no recovery code. Logging out does not delete the account’s data on our server: your nickname and records stay on the boards until the cleanup described under “Retention”, unless you delete the account first or ask us to delete it. Logging out or deleting the account also resets the game on this device to a first start (the progress, balances and records in its save; your settings stay), so that one account’s progress never passes to the next account on the device.
Friends, gifts and mailbox
Like our other House Duck games, the Android and iOS apps of 10key Survival offer optional social features for players who have a House Duck guest account, such as a friends list, friend gifts and a mailbox. You use them only if you choose to, for example by adding a friend; a player under 14 (who keeps no account) cannot use them.
- Friend code and friend requests: each guest account has a friend code. To become friends, one player enters the other's friend code and the other accepts; either can cancel a request or remove a friend later. Your friend code is shown to you in the game so that you can share it.
- Friends list: when you are friends, each of you can see the other's profile in the game, for example the nickname, the friend code, the level, the best score, the profile picture (avatar) and, where it is set, the country.
- Friend gifts: you can send friends in-game gifts and claim the gifts friends send you (currently a fixed amount of the in-game part “scrap” once a day, with no message attached). Our server records information such as who sent which gift to whom, when, and whether it was claimed, so that each gift is given once.
- Mailbox: the game has a mailbox in which House Duck can place items and notices for players, for example rewards, gifts, announcements and system messages. Our server keeps the messages addressed to your account and their state, for example whether you have opened or claimed them. There is currently no free-text messaging between players in 10key Survival.
- Reporting a player: you can report another player, for example for an offensive nickname. A report stores information such as your account, the reported player's nickname and friend code, the reason and the time, and House Duck staff review it in the operations console (section 14). To prevent misuse, the number of reports is limited (currently at most one report about a given player in 24 hours and ten a day).
- Blocking a player: you can block another player. A block stores the pair — who blocked whom — and removes any friendship, pending friend request and unclaimed gift between the two of you, so that a blocked player can no longer be your friend or send you requests or gifts.
These features run on House Duck's server at Supabase (section 4), as part of your guest account. Friend connections, gifts and mailbox items are kept with your guest account and deleted when the account is deleted or on request (see “Deletion and your rights”). A report is kept as long as needed to review and handle it and to protect players (normally about 7 days), and longer where needed for a dispute or a legal claim. A block is kept until you unblock the player or either account is deleted. Purposes and legal basis: providing the features you choose to use (GDPR Art. 6(1)(b)), and our legitimate interests (Art. 6(1)(f)) in running, improving and developing these and similar features across House Duck games, in keeping players safe and in preventing and handling abuse and fraud.
In-app purchases (Android and iOS)
The apps sell gem keycaps in three packs and the ROBOT PACK (a permanent one-time purchase; for 72 hours after a run reaches the robot it is offered at a lower price as a separate store product). Gems are spent in the game on the one revive per run after the battery runs out, on Rare Parts (called Premium Modules in the game; they open module boxes: a basic box takes 1, a rare box 3; see the odds) and on the ROBOT PACK. Payment is handled by Google Play Billing on Android and by the App Store (StoreKit) on iOS under their own terms and privacy policies. House Duck receives no payment card data and no name or email address of your store account. A purchase needs your guest account: our server verifies each purchase with Google or Apple and binds it to your account before the game grants it.
| Information (purchases) | Details |
|---|---|
| Purchase record | Product, platform (Android or iOS), a one-way hash (SHA-256) of the store’s purchase token or transaction ID, the store order ID (Google) or transaction ID (Apple), the state (granted, test purchase or refunded), the time of purchase and, after a refund, when it was refunded and the refund category. The record is bound to your login ID. |
| Store verification | To verify a purchase, our server asks Google or Apple about it and reads the answer (for example the product, the purchase state and whether it was refunded); only the items in this table are stored from it. On Google Play the app passes Google a one-way hash (SHA-256) of your login ID with each purchase, so that the receipt can be matched to your account; on iOS the app passes no account identifier to Apple. For Restore purchases on iOS the app may send the device’s App Store receipt, which our server uses only to find your transactions and does not store. |
| ROBOT PACK | A record that your account owns the ROBOT PACK (bought in the store or with gems), so that it stays with the account and a store purchase can be restored on a new device or after reinstalling. |
| Gem records | A ledger of gem grants and spends (event ID, amount, reason, reference and time), so that a purchase is never counted twice and support can check a lost balance. Our server writes the grants of verified purchases and every other grant and spend it allows (see “Balances” above); app versions before October 30, 2026 also sent their own gem events. If a gem pack is refunded, our server books a spend of that pack’s gems, and the balance can go below zero. |
Crash reports, daily usage counts and run records
So that we can find and fix crashes and other faults, see how many people play and check that the game’s difficulty is right, 10key Survival sends these technical signals to House Duck’s server: crash reports, app issue reports, daily usage counts, performance reports (test period only), run records, and run timelines and first-time steps. They are sent by the game’s own code, not by an analytics or advertising SDK, and only by released versions (the store apps, the web version on itch.io and newer web versions on Nekoland; the GamePix version and older Nekoland versions send none of them), never by development or test builds. They have no field for your nickname, your login ID or an advertising identifier. In the apps, House Duck does not link them to your guest account; in the web versions on itch.io and Nekoland, newer versions send them with the sign-in of your ranking guest account while you are signed in, and our server notes that account next to them (see the row “Signals linked to a web guest account” below). Apart from that, only a 1:1 inquiry that you send yourself can, in newer versions, carry the same session code as the reports of that session (see “Situation at the time of a report (newer versions)” below). Only House Duck staff can put these records together, only inside the operations console (section 14) and only to find the cause of a crash or problem: from the session code of an inquiry or a report to the crash reports and app issue reports of the same session, from the run ID of a report to the run timeline of that run, and from a report that carries the install ID to the records of the same installation from up to 2 hours before to 2 hours after it (other crash reports and app issue reports, the run timelines of runs played in that time and performance reports); and from the nickname of a web guest account to the signals linked to that account.
| Information | Details |
|---|---|
| Basic crash report | Sent when the previous session ended while the app was open on screen (a crash), when the app stopped responding for 5 seconds or more, and for the first error of a session. It contains information such as the kind of event, the platform (Android, iOS or web), the app version (version name, Android version code and iOS build number), the device model, the operating-system version, the name of the graphics chip (GPU), the device’s language setting, whether the report came from an internal test or diagnostic build, and technical details: how long the app had been running or how long it stopped responding, where in the program the error happened together with its error text, and a short trail of the last 30 steps before it (start, change of screen, going to the background or foreground, errors). The server adds the time it received the report and how often the same report was repeated. Going to the home screen or closing the app in the app switcher is not treated as a crash. |
| Extended crash report (Android and iOS apps, with a guest account) | If the previous session ended while the app was open on screen, the app adds the following on its next start, and the server attaches it to the basic report of the same event: the random install ID (see below), the build number, the line that names the crash (the engine’s crash message or the last error line, up to 200 characters) and an excerpt of the app’s own technical log, at most the last 8 KB. The log is a record of what the game and its engine printed (messages, warnings and errors); it is not meant to contain personal data. A report that cannot be sent stays on the device and is tried again for up to 3 days. |
| App issue reports (Android and iOS apps, itch.io, newer versions on Nekoland) | Sent when something goes wrong that is not a crash: an error answer from our server, a save that could not be read or written, a built-in part of the app that is missing on the device, a frame that took longer than 250 ms or, on the web, a longer stall, a low-memory warning from the system, a further program error after the first one of a session, and values that cannot be right (for example a negative balance, or an end of the app without a clean close); in newer versions also a failure message the game showed you that no such report explains (for example that gems could not be received or that a reward could not be claimed). It contains the kind of event, the platform, the app version and build number, the device model, the operating-system version and the device’s language setting, where in the program it happened and a short message about it, the screen and game step at the time and the short trail of the last 30 steps; for an error answer, also the server function called, its answer code and its error words (identifiers and tokens masked, never what the app had sent). For a failure message, also the fixed code of the message (not the text on your screen), the order of the game’s last requests to our server with their answers (see “Situation at the time of a report (newer versions)”) and how many milliseconds after the last request the message appeared; at most 6 such reports a session. The server adds the time it received the report and how often the same report was repeated. In the Android and iOS apps the install ID (see below) is added only for players with a guest account who have accepted the Terms and have not answered the age question as under 14; all other reports, and all reports from the web version, carry no identifier (for the session code that newer versions add, see “Situation at the time of a report (newer versions)”; for the guest account that our server notes next to the reports of newer web versions, see “Signals linked to a web guest account”). At most 16 reports a session; on Android and iOS a report that cannot be sent stays on the device and is sent at the next start. |
| Situation at the time of a report (newer versions: Android and iOS apps, itch.io and Nekoland) | So that a crash or problem can be replayed and fixed, newer versions add the following to crash reports and app issue reports; older versions send them without it. While a run is under way, the state of the run at that moment: the world seed (the random number from which the run’s board is made), the game mode (normal or hard), the level, the seconds into the run, the level the run started at, the form of the keypad (for example DRIFT or the robot) and whether it is the demo. A summary of the save in counts only: the number of runs, the best level, the sum of all upgrade levels, the number of modules and the save format version. In the short trail of the last 30 steps, also short fixed codes of the last game actions: a level-up card picked, a level reached, a revive, a special threat appearing, being caged, a popup opened or closed, and, in the newest versions, a request to our server that a button press started and its answer: the name of the server function, the answer code and its short answer word, how long it took and, when the same request had been sent shortly before (within 10 seconds), the milliseconds in between (this is how a double tap shows). For players with a guest account who have accepted the Terms and have not answered the age question as under 14, the reports also carry a random session code that the app makes new at every start (on itch.io and Nekoland, every time the page is opened) and the random run ID of the run timeline under way (see below), so that the reports of one session and its run can be put together. None of this contains your nickname, your login ID or anything you typed. |
| Install ID | A random identifier (UUID) that the app creates by itself and keeps in its own file on your device, separate from your save. It is not your login ID and is not derived from your device, your account or your name. Logging out or deleting the guest account does not change it; deleting the app or its data removes it, and a new installation creates a new ID that has no relation to the old one. |
| Daily usage counts | Once a day, shortly after the app starts: the install ID, the platform (Android or iOS), the app version and build number, the game language and the total number of runs played so far (a counter). When you leave the app after playing more runs (at most once every 20 seconds): the same details with the new total, so that the number of runs per day can be worked out. The server keeps one record per installation (first and last day seen, number of days seen, latest platform, version, build, language and run total) and one record per day on which it was seen (the counters at the first and last count of that day and the times). The device model and the operating-system version are not included. |
| Performance reports (Android and iOS apps, test period only) | While 10key Survival is in its test period, the Android and iOS apps send one short technical summary per session so that we can find slow loading, stutter and connection problems on real devices. It contains: how long each loading step took and its longest frame, frames that took longer than 100 ms (with the screen and the game step where they happened), pauses of 2 seconds or more, per server address the number of calls and how they ended (success, offline, timeout, error code), the steps of a purchase and their result codes (never a payment token, receipt or order number), memory use and the system’s low-memory warnings, and the device facts already listed for crash reports plus the number of processor cores, memory size, screen refresh rate and graphics driver. A random session ID ties the parts of one session together. It is sent only by players who have accepted the Terms of Service and this Policy and have not answered the age question as under 14 (until the age question is answered, a player is not treated as under 14); players who answered it as under 14 send no performance reports. The install ID (see above) is added only for players with a guest account. The summaries are kept for 30 days and are switched off when the test period ends. |
| Run records | Collected on the device each time a run (one play from start to end) ends and sent a few runs at a time while the app is open: the install ID, the platform, the app version and build number, a random run ID made for each run, when the run ended, the game mode, the level reached, the play time, the depth, how the run ended, whether it was completed, the form at the end (keyboard, DRIFT or robot) and the levels at which DRIFT and the robot were reached, the level-up cards chosen and the level at which each was chosen (at most 24 per run), the enemies met and beaten, the best combo, the scrap collected, whether the revive offer appeared and was used, whether Transform mode is owned, and the balance settings number. A record that cannot be sent stays on the device and is tried again for up to 7 days. The server keeps one record per run. The device model and the operating-system version are not included. |
| Run timelines and first-time steps (Android and iOS apps with a guest account, itch.io, newer versions on Nekoland) | Run timeline: sent once per run when it ends, in fixed words and whole numbers only (no free text): a random run ID, the game mode, how and why the run ended, the level reached and the run’s length, the seconds at which each level was reached, the level-up cards offered and the ones chosen, when each special threat first appeared, when the keypad’s durability fell low, the revive offer and your answer, the special cards (GOLDEN FEVER, DRIFT and TRANSFORM) and whether they were won, idle stretches of 8 seconds or more without a dig or a pick, and balance counters (for example keys broken and damage taken per band of levels, in newer versions the durability lost to each cause (battery drain, hits, being grabbed and being caged), time spent in each form and the skill levels at the end). Newer versions also add, in whole numbers only, how far your progress was when the run started: the upgrade level of each part, the number of modules, the level the run started at and the number of revives already paid with gems. First-time steps: once per step, the first time a step of a fixed list is reached (first start, title screen, first run, first level-up, first death, first result screen closed, second run, first opening of each of the five tabs, end of the demo), with the seconds since the game started, the number of runs played so far and the game language. Both carry the platform and the app version and build number and, in the apps, the install ID (see above); on itch.io and Nekoland they carry the page-load number described in the next row instead. In the apps, the timeline of a run that was still open when the app closed is sent at the next start if it is less than 3 days old. |
| Web versions on itch.io and Nekoland: usage signal, run records, run timelines and first-time steps | The web version on itch.io sends only after you agree to the Terms of Service and this Policy on its first screen; the date and the terms version of that agreement stay in the game's save data so it does not ask again. Newer versions on Nekoland send the same in the same way, with Nekoland web as the platform; the GamePix version and older Nekoland versions send none of this. Each time the game page is opened, the game makes a new random number (UUID) in memory and does not store it in your browser (no cookie, no local storage). Once when the page opens: this number, the platform (itch.io web or Nekoland web), the game version and build number. Each time a run ends: the same items as the "Run records" above and the run timeline described in the row above, sent at once (not collected on the device; a record that could not be sent is gone when the page is closed); and the first-time steps described in the row above, the first time each is reached on this page. The game language, the total play counter, the device model, the operating system version and your nickname are not sent with the usage signal and the run records, and your guest account only as described in the next row (the first-time steps carry the game language and the number of runs, and the ranking record described under “Online rankings” is separate). The server keeps them the same way as for the apps (one entry per number, one per day, one per run, one per step). Because the number changes every time the page is opened, we cannot tell from it whether the same person came back; only the records linked to a web guest account (next row) show which of them came from the same account. |
| Signals linked to a web guest account (newer web versions on itch.io and Nekoland) | While you are signed in with the ranking guest account (Terms accepted, nickname chosen and not answered as under 14), newer web versions send the crash reports, app issue reports, usage signal, run records, run timelines and first-time steps described above with the sign-in token of that account. The records themselves stay the same: they have no field for your nickname, your login ID or anything you typed. Our server reads the account from the sign-in and stores the account’s player ID next to each record, so that House Duck staff can go from the account to its records in the operations console (section 14). Before you choose a nickname, after you log out, or when the server does not accept the sign-in, the records are sent without it, as before. A report that only adds to the count of an earlier identical report of the same day adds no link. The Android and iOS apps, the GamePix version and older Nekoland versions never link these signals to an account. |
- Which versions send: The basic crash report is sent by the released Android and iOS apps, also before you have a guest account and by players under 14, because it contains no identifier (for the session code that newer versions add, see “Situation at the time of a report (newer versions)”); the released web version on itch.io, and newer web versions on Nekoland, send it only for the first error of a session. App issue reports are sent by the same versions in the same way, with the install ID only as described in their row. In the Android and iOS apps, the extended crash report, the daily usage counts, the run records and the run timelines and first-time steps are sent only by released versions and only while you have a House Duck guest account (Terms accepted, nickname chosen and not answered as under 14): not before the account exists and not after you log out. Of these, the web version on itch.io (and newer web versions on Nekoland) sends only its own usage signal, run records, run timelines and first-time steps, described in the web rows of the table above, linked to your guest account only as described in the row “Signals linked to a web guest account”. The GamePix version and older Nekoland versions send none of these signals: House Duck’s server accepts from them only the requests of the online ranking and its guest account. Desktop versions and test builds send none of them. Like any web request, each signal carries your IP address and HTTP request metadata, which are processed to deliver the response and to protect the server.
- Purposes: Crash reports: to find, group and fix crashes and freezes and to see which app versions and devices are affected. Daily usage counts: to count how many installations are used per day and how many runs are played, to see how many come back and which versions are in use, and to check that an update runs stably and the service works. Run records: to count at which level and why runs end, how far players get to DRIFT and the robot and how often each card is chosen, so that the game’s difficulty and balance can be tuned. App issue reports: to find and fix server errors, save problems, stutter and other faults, also before they lead to a crash. Situation at the time of a report (newer versions): to replay a crash or problem as it happened, so that it can be fixed. Run timelines and first-time steps: to see where runs become too hard, too easy or dull, and at which first step new players stop, so that the game’s pace, balance and first steps can be improved. Signals linked to a web guest account: so that, when a problem is reported or seen, House Duck staff can find the crash reports, app issue reports, runs and first steps of the same account and fix its cause. We use them for nothing else.
- Legal basis: legitimate interests (GDPR Art. 6(1)(f)) in the stability and operation of the game, in fixing errors, in knowing how many people use it and in balancing the game. A random install ID does not by itself make data anonymous. Your right to object is described in section 9.
- Recipients and countries: The server that receives these signals is run by Supabase as House Duck’s processor (section 4); the primary database is in Ireland (AWS eu-west-1), and section 5 describes support and subprocessor processing outside the EU. The records can be read only by House Duck staff in the operations console (section 14). House Duck does not pass them to advertising or analytics providers.
- No advertising, no profiling: House Duck does not use these signals for advertising, does not share them with advertising partners, does not use them, or their link to a web guest account, to build a profile of you, and makes no decision about you based on them. They are used for error analysis and for counts and trends.
- Retention: Run records: deleted after 60 days. Run timelines and first-time steps: deleted after 60 days. Daily usage counts: the records per day are deleted after 120 days; the record of an installation, with any day records left, is deleted when the installation has not been seen for 183 days (6 months). Crash reports: the log excerpt is deleted after 7 days and the rest of the report after 30 days. App issue reports: deleted after 30 days. These deletions are made by a regular automatic cleanup.
- Deletion: In the apps these signals are not linked to your guest account, so deleting the account in the app does not delete them; the cleanup removes them after the periods above. Signals linked to a web guest account are deleted together with that account’s 10key Survival data (on request, see “Deletion and your rights”, or when the cleanup removes the player record), at the latest after the periods above. Deleting the app or its data removes the install ID from your device. The page-load number of the web versions on itch.io and Nekoland is never stored, so nothing of it stays on your device once the page is closed. Because they contain no name, nickname or login ID, we generally cannot tell which records belong to which person (except the records linked to a web guest account); if you write to support@houseduck.in (section 9), we will explain what is possible.
Web version on Nekoland
On Nekoland, the free web demo of the game (up to level 8) is available; there is no purchase. As on itch.io, your progress, gems, Rare Parts and modules stay in your browser’s storage, and the results of finished runs are sent to House Duck’s server for the online ranking and the ranking is read from it (see “Online rankings” and “House Duck guest account”). Apart from these requests and those of its guest account, older Nekoland versions send House Duck nothing. Newer versions also send, like the itch.io version, the technical signals described under “Crash reports, daily usage counts and run records” (only after you agree to the Terms of Service and this Policy on the first screen; the usage signal, run records, run timelines and first-time steps name Nekoland web as the platform, while crash reports and app issue reports say web, as on itch.io; linked to your guest account only as described there), and while you are signed in they let you send a 1:1 inquiry (see “House Duck guest account”). Nekoland’s own platform keeps a cloud save of the game and receives four game events from it (start, completion and failure of a level, and the end of the tutorial), under Nekoland’s own terms and privacy policy.
Web version on GamePix
On GamePix, the full game is free on the web, with ads shown by GamePix; there is no purchase. Your progress, gems, Rare Parts and modules stay only in your browser’s storage (module boxes are opened inside the game). As on itch.io, the results of finished runs are sent to House Duck’s server for the online ranking and the ranking is read from it (see “Online rankings” and “House Duck guest account”). Apart from these requests and those of its guest account, the GamePix version sends House Duck nothing: no usage signal, no run records, no run timelines or first-time steps, no crash reports and no app issue reports. The game contains no analytics SDK and no advertising SDK of its own; the only third-party SDK in it is the GamePix SDK, which GamePix (GamePix S.r.l., Italy) provides as an independent controller in GamePix’s page. It shows the ads (an ad may play when a run ends; rewarded ads play only when you choose to watch one, for example for a revive or for gems), and the game passes it your score, your level and highlight moments of a run. GamePix’s own terms and privacy policy (GamePix Privacy and Cookie Policy) and those of the website on which you play govern the SDK, the ads and any consent for them.
Daily reminder and store review prompt (Android and iOS)
Daily reminder: the apps can remind you to play with a notification at 20:00 on your device’s clock. The reminder is a local notification that the app schedules on your device itself: no push service is used, and nothing about it is sent to House Duck or to anyone else. The app asks for the system’s permission to show notifications. You can turn the reminder off in the app’s SETTINGS or in your device’s settings.
Store review prompt: the apps may open the store’s own review sheet (Apple’s or Google’s) once, so that you can rate the game if you wish. The sheet is shown and run by the store under its own terms and privacy policy; House Duck receives nothing from it.
Launch pre-registration (website)
If you leave your email address on the 10key Survival page (houseduck.in/10key/), we send you one launch email with the download link (houseduck.in/10key/get/) once the game is available on iOS and Android. Pre-registering is free and is not a purchase. It signs you up for no other marketing email; news about House Duck games is emailed only if you agree to it separately (section 3, “How we use data”).
| Information (pre-registration) | Details |
|---|---|
| Sign-up record | Email address, email language (the language of the House Duck page you signed up on: Korean, English, German or Japanese), the version of the consent text you agreed to, a random token for the cancel link, the status (pre-registered, unsubscribed; sign-ups from before October 30, 2026 can also be awaiting confirmation) and its times (sign-up, receipt email sent, unsubscribe, launch email sent). We do not store your IP address and do not link the record to a game account. |
- Done on sign-up: since October 30, 2026 the pre-registration is complete the moment you send your address. support@houseduck.in sends you one receipt email, and its cancel link cancels the pre-registration at any time. Signing up again with the same address sends no further email. Addresses that signed up earlier under double opt-in and never confirmed do not get the launch email.
- Legal basis for the pre-registration: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time with the unsubscribe link in our email or by writing to support@houseduck.in; this does not affect processing before the withdrawal.
- Ad measurement: the 10key Survival page loads the Google tag of Google Ads (Google Ireland Limited and Google LLC, USA) in Google’s consent mode. While you have not answered the notice at the bottom of the page, it stores and reads no cookie and only tells Google, through cookieless signals, whether the visit came from one of our ads and whether a pre-registration was made (conversion measurement). These signals contain the ad-click information (the ad click ID in the page address), the page address, the time and device and browser data such as the IP address. Legal basis: House Duck’s legitimate interest in measuring how its ads perform (Art. 6(1)(f) GDPR). If you press Allow, an ad-measurement cookie is stored as well, which makes the measurement more accurate; the legal basis for that is consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). If you press Decline (an objection under Art. 21 GDPR), no further signal is sent, and from your next visit no code from Google is loaded at all. You can change your choice at any time with “Ad measurement settings” at the bottom of the page; the choice is stored only in your browser. Declining does not affect the pre-registration. Google’s policies govern the data Google receives and the cookie (sections 4 and 5); Google Ads cookies usually last up to 90 days.
- Google Ads customer match: The email address you leave on the pre-registration form is also passed to Google Ads (Google Ireland Limited and Google LLC, USA) as a customer match list. The address leaves our server as a SHA-256 hash, and Google uses the list only to show you House Duck ads and to find other Google users with similar interests (similar segments) for those same ads. We do not allow its use for other advertisers, do not sell it, and do not use it for any purpose other than our own ad targeting. Legal basis: your consent (Art. 6(1)(a) GDPR), which you give with the consent box on the pre-registration form. You can withdraw it with the unsubscribe link in our email or by writing to support@houseduck.in; House Duck then removes the address from the Google Ads list, and your pre-registration is cancelled. Withdrawal does not affect processing before the withdrawal. Google's policies govern the data Google receives and the retention of the list (sections 4 and 5).
- Recipients and countries: the sign-up record is kept on the House Duck server at Supabase (section 4) in Ireland (AWS eu-west-1). Emails are sent by Resend (Plus Five Five, Inc., USA) as House Duck's processor, which receives your email address and the email content for this. Transfers to the USA rely on Resend's EU-U.S. Data Privacy Framework certification and the Standard Contractual Clauses.
- Retention: we keep the sign-up record on the pre-registration list after the launch email as well, and use it for the Google Ads customer match list described above for the same purpose. Unsubscribed sign-ups and deletion requests are removed by automatic clean-up within 30 days, and we delete earlier on request. Unconfirmed sign-ups from before October 30, 2026 are still deleted after 30 days.
Purposes and legal bases
- Showing the boards and your rank, and accepting and storing your records for them: contract performance (GDPR Art. 6(1)(b)), because the ranking is a service you choose to use.
- Creating and running the guest account (login ID, sign-in tokens, nickname, an optional Google or Apple link), keeping the account’s game progress, balances, modules, run tickets, quest-reward records and ROBOT PACK offer, verifying, delivering and restoring purchases, and keeping the ROBOT PACK and gem records: contract performance (Art. 6(1)(b)).
- Problem reports, to answer them and fix what they describe: contract performance (Art. 6(1)(b)) and legitimate interests (Art. 6(1)(f)) in fixing errors.
- The social features (such as the friend code, friend requests and connections, friend gifts and the mailbox): providing the features you choose to use (Art. 6(1)(b)) and legitimate interests (Art. 6(1)(f)) in running, improving and developing them and similar features across House Duck games, for example granting each gift once. Keeping players safe and preventing abuse and fraud (for example blocking, reviewing reports and integrity checks): legitimate interests (Art. 6(1)(f)).
- The age band, the Terms version and the time of your agreement, to apply the age rule (no account under 14) and to show what was agreed: legitimate interests (Art. 6(1)(f)) and, where a law requires such a check or record, legal obligation (Art. 6(1)(c)).
- Preventing cheating and abuse (verifying the sign-in, plausibility checks, rate limits, booking each run once against its ticket, prices and balances checked on our server, the nickname check, checking the game version against the minimum version for the boards, the input-rhythm summary and review notes used to tag likely automation and currency or data anomalies for a review by a person, holding accounts from the boards until that review, excluding players from the rankings and the other measures in the Terms, for example removing records or items or suspending or terminating an account) and purchase fraud (binding a receipt to one account, refusing a receipt used twice, recording refunds, keeping purchase records after an account is deleted): legitimate interests (Art. 6(1)(f)) in fair rankings, in protecting purchases and in protecting the service.
- Keeping purchase records where tax, commercial or consumer law requires it: legal obligation (Art. 6(1)(c)).
- IP address and request metadata for delivering responses and protecting the server: legitimate interests (Art. 6(1)(f)).
Recipients and countries
- Supabase runs the 10key Survival server, including the sign-in of guest accounts (Supabase Auth), as House Duck’s processor (section 4). The primary database is in Ireland (AWS eu-west-1); support and subprocessor processing outside the EU follows the safeguards described for Supabase in section 5.
- Other players and anyone who views the boards see the public board entries: rank, nickname, score and level.
- Google and Apple process in-app purchases, their restoration and refunds in the Android and iOS apps (Google Play Billing, App Store) as independent controllers under their own terms and privacy policies; sections 4 and 5 describe them and the countries involved. Our server contacts them, for example, to verify purchases and integrity tokens. The app may also ask a platform’s integrity service to confirm that the app and the device are genuine, for example Google’s Play Integrity on Android when a run is submitted or a purchase is verified (see “Online rankings”). If you link a Google or Apple account, Google or Apple run that sign-in on their own pages under their own terms and privacy policies.
- The platform runs or delivers the game and provides your platform account, its own services and, where applicable, payment processing under its own terms and privacy policy, as an independent controller.
- GamePix provides the GamePix SDK and its ads in the GamePix version as an independent controller (see “Web version on GamePix”). House Duck sends GamePix no data; the game passes the SDK only the score, the level and highlight moments.
- GitHub Pages delivers this website, including the game’s settings file (section 5).
Retention
- Season board entries: the boards of the current and the last season are kept in full; of the season before last, the entries below the top 100 places of each board are deleted (the entries of players excluded from the rankings stay until that season is deleted, so that an exclusion can be lifted), and all entries of older seasons are deleted.
- Run records sent for the rankings, including their input-rhythm summary: deleted after 35 days; those flagged by our checks or tagged as likely automated after 90 days.
- Review notes (a run tagged as likely automated, or an account with anomalies in its currencies or data): kept with the account, at most until the account is deleted or its data is removed for inactivity (see the player record below).
- Player record, all-time best and all other ranking data of a player, and in the apps the account record (nickname, age band, Terms version): deleted together once the player has not been seen for 6 months (183 days), or earlier on request or when you delete the account.
- Game progress, scrap and Rare Part records, modules and run tickets of a guest account: deleted together with the player record once the player has not been seen for 6 months (183 days), or earlier on request or when you delete the account. Before that, run tickets are deleted 2 days after the run started once it is booked (7 days after the start if it was never booked), the answers of module draws after 30 days, and entries of the scrap, gem and Rare Part records older than 30 days are folded into one total per kind and source (your balances stay the same; purchases and one-time grants are kept as they are).
- Guest login (with any Google or Apple link), the ROBOT PACK record and offer window, and gem records: kept until you delete the account in the app or ask us to delete it, because they are needed to restore the ROBOT PACK and to handle refunds and support requests (older gem entries are folded as described above). Sign-in sessions end when you log out or delete the account.
- Problem reports: deleted 7 days after they were sent, or earlier when you delete the account.
- Quest reward records: deleted 35 days after the reward was claimed.
- Friends, gifts and mailbox: friend connections, gifts and mailbox items are kept with your guest account and deleted when the account is deleted or on request. A block is kept until it is removed or either account is deleted. A report is kept as long as needed to review and handle it and to protect players (normally about 7 days), and longer where needed for a dispute or a legal claim.
- Purchase records: while the account exists, as part of it. When the account is deleted, the link to the account is removed and the rest of the record (product, platform, the hash of the purchase token or transaction ID, the store order or transaction ID, state and times) is kept, so that the same receipt can never be granted again to another account and refunds and disputes can be matched, for as long as these purposes and any statutory retention period require.
- Technical signals (crash reports, app issue reports, daily usage counts, performance reports, run records, run timelines and first-time steps), as described under “Crash reports, daily usage counts and run records”: day records of usage counts 120 days; an installation’s record until it has not been seen for 183 days; crash log excerpts 7 days; crash reports 30 days; app issue reports 30 days; run records 60 days; run timelines and first-time steps 60 days; performance reports (test period only) 30 days. Records linked to a web guest account follow the same periods and are deleted earlier together with the account’s data.
- Saves, settings and sign-in tokens on your device or in your browser: under your control; House Duck holds no copy of the save (for a guest account, our server keeps only the progress and balances described above). Deleting the app or its data removes them, and logging out or deleting the guest account resets the save to a first start (your settings stay).
- Information independently held by the platform or store, and request logs kept by hosting providers: under each provider’s retention policy and settings.
These deletions are made by a regular automatic cleanup once the periods have passed.
Deletion and your rights
In the Android and iOS apps you can delete your guest account at any time: tap your profile at the top left of the home screen, press and hold Hold to delete account under Account, and confirm with Delete (an internet connection is needed). Our server then deletes your account record, player record, best scores, run records, review notes, game progress, scrap, gem and Rare Part records, modules, run tickets, your friend connections, the gifts and mailbox items of your account, your blocks and the reports you sent, the ROBOT PACK record and offer window and your problem reports and, unless another House Duck game uses the same login, the login itself (with any Google or Apple link). If an Apple account is linked and the login itself is deleted, the app may ask you to confirm with your Apple account once more, so that our server can withdraw the app’s access to it. Purchase records are kept without the link to your account, as described under “Retention”. The app then forgets the account and resets the game on this device to a first start (your settings stay). A ROBOT PACK bought in the store can later be restored to a new guest account with Restore purchases and the same store account; gems, Rare Parts, modules and progress cannot be restored.
You can also ask at any time for your 10key Survival data to be deleted, for example if you have logged out, no longer have the app or play a web version: email support@houseduck.in and give your nickname. House Duck then deletes your 10key Survival data on its server (your player record, best scores, run records and review notes and, for a guest account, also the account record, game progress, balances and their records, modules, run tickets, your friend connections, gifts and mailbox items, your blocks and the reports you sent, the ROBOT PACK record, problem reports and, unless another House Duck game uses it, the login, with purchase records kept as described above; for a web guest account also the technical signals linked to it). Because nicknames are public, we may ask for the minimum additional information needed to confirm that the request comes from you (for example the order ID on a store receipt); do not send passwords. If you later send records again while signed in, or create a new guest account, a new player record is created. Your other rights, response times and the right to complain to a supervisory authority are described in section 9. Your platform or store account and the data the platform holds are managed by the platform; contact the platform about them.
Ads and analytics
- 10key Survival itself contains no analytics SDK and no advertising SDK of its own, and House Duck receives no advertising identifiers. The crash reports and daily usage counts that House Duck’s own code sends are described under “Crash reports, daily usage counts and run records”. The Nekoland version contains Nekoland’s SDK for its cloud save and game events (see “Web version on Nekoland”), and the GamePix version GamePix’s SDK (see “Web version on GamePix”). The Android and iOS apps show no ads.
- Where 10key Survival is free on a platform, ads may be shown by that platform (for example on GamePix) under its own terms and privacy policy; ad consent and ad choices are managed by the platform.
- Where 10key Survival is sold through a store, the store processes the purchase of the game and of in-app purchases under its own terms and privacy policy; what our server keeps about in-app purchases is described above. House Duck receives no payment card data.
Children
Like our other games, 10key Survival is not directed to children under 14, or a higher minimum age required by local law. In the Android and iOS apps, players under 14 keep no account once they have answered the age question, which is asked at the first visit to the SHOP and before any purchase (see “House Duck guest account”). They can still play the game without an account. From then on they send no ranking records and none of the signals that need a guest account; only the basic crash report and the app issue reports described under “Crash reports, daily usage counts and run records” are still sent, without any identifier. The age question is not identity or age verification. Players below the age at which local law lets them consent to data processing on their own (in Germany generally 16) should play 10key Survival only with the permission of a parent or guardian, and the platform’s own age rules also apply. Purchases by minors may need the approval of a parent or guardian (see the Terms). If we learn that we processed a child’s data without a required authorization, we delete it; a parent or guardian can ask for deletion at support@houseduck.in.
Security and automated checks
Our server accepts records only after verifying the guest account’s sign-in, and it checks submitted runs automatically (plausibility checks and rate limits). A run that fails these checks is flagged and may not count for the boards, and players who cheat may be excluded from the rankings or face the other measures in the Terms (for example removal of records or items, or suspension or termination of the account). Only runs played with a game version at or above the minimum version House Duck sets count for the boards (a run started before the minimum was raised still counts). Accounts whose currencies or data show anomalies are held from the boards until a person has reviewed them, and runs that the input-rhythm summary suggests are likely automated are tagged for such a review; a tag alone never removes a record or a player from the boards; a person decides after the review. To check the game, House Duck can switch on a test mode for single accounts: staff test accounts can play invincible, and app store reviewers can switch on a review mode with a code from House Duck. Players cannot switch these modes on, and runs played in them are not shown on the boards. Newer versions keep a short summary of each invincible run (the level and time reached and the test settings it was played with) apart from the players’ run records, for 60 days. Nicknames are checked automatically against a word list, and purchases are granted only after Google or Apple confirm them. Prices and balances are checked on our server, and the earnings of each run are booked once against its ticket. The game sends data only encrypted (HTTPS); the account and purchase tables can be read only by House Duck’s server (Row Level Security), and purchase tokens are stored only as a hash. You can ask support for a human review. House Duck does not make solely automated decisions producing legal or similarly significant effects.
14. Support Requests and House Duck’s Operations Tools
This section applies to all House Duck games and to the website. It describes how we handle support requests and the internal tools that House Duck staff use to answer them and to run our games.
Support email
Email sent to support@houseduck.in or business@houseduck.in is received, stored and answered in Google Workspace (Gmail), which Google provides to House Duck as a service provider (section 4). We process what you send: your email address, the name shown with it, the subject, the message, attachments and anything else you include (for example a game display code or a platform username). We use it to answer and resolve your request, which may include looking up the game account you ask about. Legal basis: contract performance or pre-contractual steps (GDPR Art. 6(1)(b)) where the request concerns a game, an account or a purchase; legal obligation (Art. 6(1)(c)) for rights requests; otherwise legitimate interests (Art. 6(1)(f)) in answering inquiries. Support emails are kept as long as needed to resolve the request and handle disputes (section 6). Please do not send passwords or payment details.
House Duck operations console
The House Duck operations console at houseduck.in/console/ is an internal tool used only by House Duck staff. Players do not sign in to it and cannot create an account there. Staff sign in with Google: the console receives a Google ID token that contains the staff member’s Google account email address, Google account ID and, where Google includes them, name and profile picture. House Duck’s server (Supabase) verifies this token with Google, checks the email address against the staff allow list, asks a second security question and then issues its own session ticket, valid for 72 hours. The ID token and the session ticket are kept in that browser’s local storage until they expire or the staff member signs out. Failed sign-in attempts are counted under a hashed identifier so that repeated failures lock the sign-in, and changes that staff make to game data are recorded in an audit log with the staff member’s email address. We process this sign-in data to keep the console limited to authorised staff and to keep operations traceable (legitimate interests, Art. 6(1)(f)).
In the console, staff may look up the game account data described in sections 2 and 13 (for example, the account that matches the display code given in a support email) only to answer that player’s support request, to handle purchases and refunds, or to keep the games running and fair. Changes to game data are made through House Duck’s server, not directly from the browser, and are recorded in the audit log.
Gmail access (Google user data)
With the staff member’s consent on Google’s consent screen, the console requests the Gmail scope https://www.googleapis.com/auth/gmail.modify and uses it only for the House Duck support mailbox (support@houseduck.in), to:
- list and read the messages and attachments sent to support@houseduck.in;
- add and remove House Duck support labels (for example “House Duck/CS/Needs Reply” or “House Duck/CS/Done”) and move answered conversations out of the inbox;
- write and send replies to those messages from the support mailbox.
The console calls the Gmail API directly from the staff member’s browser. The access token stays only in the browser’s memory for that session and is revoked when the staff member disconnects Gmail or signs out. Mail, attachments and access tokens are not copied to House Duck’s servers (Supabase) or to any code repository. The short summary and category that staff see for each message are made by the console inside the browser; mail text is not sent to any AI service. People at House Duck read mail only to answer and resolve the request. House Duck does not sell Gmail data, does not use it for advertising, does not share it with anyone other than the providers named in this section that process it for House Duck, and does not use it to train AI models. A staff member can remove the console’s access at any time in their Google Account under third-party connections.
House Duck’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
15. Changes
- November 22, 2026 notice revision — 10key Survival (section 13): the social features of the Android and iOS apps are now described, such as the friends list, friend gifts and the mailbox (for example the friend code and friend requests, and what a friend sees), together with reporting and blocking another player, their purposes and retention, and that they are deleted with the account. The basic crash report is noted to also carry, for example, the graphics chip (GPU) and whether it came from an internal test or diagnostic build; the one-device session and app and device integrity checks (on Android currently Google’s Play Integrity) are now described; and the game-progress record is noted to include gameplay statistics such as per-number-key press counts. Some lists are now worded as examples. Section 3 now states that where a platform requires a separate permission for personalised ads using a linked account (for example Apple’s App Tracking Transparency), House Duck uses the data for this only after that permission. Later the same day, 10key Survival (section 13): which runs count for the boards (a minimum game version), that accounts with currency or data anomalies are held from the boards until a person has reviewed them, and the input-rhythm summary in numbers only (counts and shares; no key identities, no text, no touch paths) that newer versions send with ranking runs to detect macros and other automation are now described, with their purpose (preventing cheating and fraud, legitimate interests) and retention (with the ranking run record; a review note with the account, at most until the account is deleted or removed for inactivity). Nothing else changed.
- November 19, 2026 notice revision — 10key Survival (section 13): Steam is no longer named as a platform, because the game is not offered there. Rare Parts are called Premium Modules in the game and open module boxes (a basic box takes 1, a rare box 3). The nickname rule now matches the game (at least 2 letters or digits, at most 12 Korean, Chinese or Japanese characters or 18 other ones). Players under 14 can still play without an account. A test mode that House Duck switches on for single accounts (invincibility for staff test accounts, a review mode for app store reviewers) keeps their runs off the boards, and newer versions keep a short summary of each invincible run apart from the players’ run records for 60 days. Editorial changes: the page header now links to the 10key Survival Terms, the wording on the daily cleanup (section 6) and on the pre-registration consent is clearer, and the page uses one spelling throughout. Nothing else changed.
- November 18, 2026 notice revision — 10key Survival (section 13): newer web versions on Nekoland send the same technical signals as the itch.io version (crash reports for the first error of a session and app issue reports, which say web as on itch.io, and the usage signal, run records, run timelines and first-time steps, which name Nekoland web as the platform) and, while you are signed in, offer the 1:1 inquiry. In newer web versions on itch.io and Nekoland, while you are signed in with the ranking guest account, these signals are sent with its sign-in and our server notes the account next to them, so that House Duck staff can find one account’s records when a problem is reported; they still carry no nickname or login ID, the apps and the GamePix version never link them, and they are deleted with the account’s data. Versions released before this revision send none of this. The GamePix version is released; the note that it was still in review was removed.
- November 18, 2026 notice revision — Website (section 2): on the support page, after a visitor picks 10key Survival, the browser asks once for the game’s public settings (a Supabase public endpoint) to show the current link for public questions on YouTube. The request carries no account, player identifier or anything the visitor typed.
- November 18, 2026 notice revision — 10key Survival (section 13): newer versions also send an app issue report when the game shows you a failure message that no other report explains (for example, after a double tap, that gems could not be received): it carries the fixed code of the message, the order of the game’s last requests to our server with their answers and how long after the request the message appeared, at most 6 such reports a session. The short trail of the last 30 steps also names the requests to our server that a button press started and their answers. None of this contains your nickname, your login ID or anything you typed. Versions released before this revision send none of these new items.
- November 17, 2026 notice revision — 10key Survival (section 13): the technical run records are now kept for 60 days instead of 90. In newer versions, the balance counters of the run timeline also name the durability lost to each cause (battery drain, hits, being grabbed and being caged). The new row “Situation at the time of a report (newer versions)” and the 1:1 inquiry row list what newer versions add so that a crash or problem can be replayed: the state of the run, a save summary in counts only, short codes of the last game actions and, for players with a guest account who have accepted the Terms and have not answered the age question as under 14, a random session code and the run ID (a 1:1 inquiry carries them without the run ID, at most 2 KB in all, deleted with it). Newer versions also add your progress at the start of a run (upgrade levels, modules, starting level, revives paid with gems) to the run timeline. Versions released before this revision send none of these new items. Also in this revision: the 1:1 inquiry row names the web version on itch.io, from which a player signed in with its ranking guest account can send an inquiry; section 13 says how House Duck staff can put records together in the operations console to find the cause of a problem (by session code, by run ID, and by install ID from up to 2 hours before to 2 hours after a report); the performance report row says that players who have answered the age question as under 14 send none (until it is answered, a player is not treated as under 14); and season board entries are no longer deleted 12 weeks after the season: the current and the last season are kept in full, the season before last keeps only its top 100 places per board (newer versions also show that board), and older seasons are deleted.
Show earlier revisions
- November 9, 2026 notice revision — 10key Survival (section 13): in-app problem reports moved to SETTINGS → INFORMATION → CONTACT → 1:1 INQUIRY and now ask for an email address for the reply, so that address and its only use (answering the inquiry) are listed, and the same window's YouTube button is described as only opening YouTube.
- November 8, 2026 notice correction — the text now matches what our games and website do: the Google Gemini API row (section 4) and “redacted support summaries” (section 5) were removed, because support messages and reports are not summarised by any AI service (section 14); Resend and the Google Ads uses on the 10key Survival pages (the Google tag and customer match lists) were added to the tables in sections 4 and 5; section 13 now says which signals players under 14 still send, that pre-registering signs you up for no other marketing email, that deletion by email keeps the login if another House Duck game uses it, and how long performance reports are kept. Section 13 now also describes the app issue reports and the run timelines and first-time steps (what they contain, which versions send them, and that they are kept for 30 and 60 days), names the Nekoland web version, and says that the GamePix version is still in review and that both send House Duck only the requests of the online ranking and its guest account. The Korean and German versions now link the account-deletion instructions in their own language.
- November 8, 2026 notice revision — website: on Korean-language pages, the KakaoTalk share button and the Kakao JavaScript SDK it loads from
t1.kakaocdn.netwere added to section 2 (when the SDK loads and what Kakao Corp. receives when a visitor shares), and Kakao Corp. (South Korea) to the provider table in section 4 and the country table in section 5. The whole Policy was also edited for readability (repeated statements merged, long sentences shortened, some passages turned into lists), with no change in substance. The games and their consent are unchanged. - November 4, 2026 notice revision — added “How we use data” to section 3: use of aggregated and anonymised data, use across House Duck games, personalised ads (customer match) with the hashed email address of a linked Google or Apple account where you separately agree, news emails where you agree, and transfers in a business transfer. The account-linking text in sections 2 and 13 was aligned. Accounts linked before are not used for this without consent. The document was also made easier to read (summary added, section 13 details and the revision history folded).
- November 4, 2026 notice revision — 10key Survival launch pre-registration (section 13): the email address you leave on the pre-registration form is now also passed to Google Ads as a customer match list, as a SHA-256 hash, so that House Duck ads can reach you and other Google users with similar interests. The earlier sentence that the address is never sent to Google was replaced, and the purpose, its limits, the legal basis (consent) and how to withdraw were added. In the same revision the retention of the sign-up record changed: it stays on the pre-registration list after the launch email and is deleted within 30 days after an unsubscribe or a deletion request (section 13).
- November 4, 2026 notice revision — 10key Survival (section 13): during the test period, the Android and iOS apps now send one short technical performance summary per session (loading times, long frames and pauses, how server calls ended, purchase step results without any payment token, receipt or order number, memory use and device facts). It is sent only after you agree to the Terms of Service and this policy, players under 14 send none, and the summaries are kept for 30 days and switched off when the test period ends.
- November 1, 2026 notice revision — 10key Survival (section 13): the online rankings now show the board of the current season and of the last season (a season is one calendar quarter) and keep each player’s all-time best, instead of a weekly board. The web versions on itch.io and GamePix now use a guest account (anonymous sign-in and your nickname) only for the online ranking and send the results of finished runs to House Duck’s server, while progress, gems and upgrades stay in your browser; they also send House Duck’s own technical signals, and the description of the GamePix version was updated accordingly. Described: daily and weekly quests in the apps (each claimed reward is recorded on our server for 35 days so that it is granted once), the daily reminder notification (a local notification, nothing sent) and the store review prompt (nothing received). The text on sign-in with a platform account, the CrazyGames SDK and platform avatars was removed, because 10key Survival is not offered on CrazyGames.
- October 31, 2026 notice revision — 10key Survival launch pre-registration (section 13): the Google Ads ad measurement now uses Google’s consent mode. Before you answer the notice it sends only cookieless signals about the ad click and the pre-registration (legitimate interest); Allow adds the ad-measurement cookie (consent); Decline stops the signals and, from your next visit, no code from Google is loaded.
- October 31, 2026 notice revision — 10key Survival (section 13) brought up to date with the game: with a House Duck guest account, our server keeps the account’s game progress, balances (scrap, gems, Rare Parts), modules and run tickets and decides every spend, and starting a run needs an internet connection; logging out or deleting the account resets the game on the device; the age question comes at the first visit to the SHOP; the optional Google or Apple link; problem reports (kept 7 days); the ROBOT PACK replaced the Revive Pass, gems are also spent on Rare Parts and the ROBOT PACK, and the gems of a refunded gem pack are taken back; the web version on GamePix (ads by GamePix, no data sent to House Duck); retention and deletion updated to match.
- October 30, 2026 notice revision — 10key Survival web version on itch.io (section 13): after you agree to the Terms of Service and this policy on its first screen, it sends a random number made anew, and never stored, each time the page is opened, plus a record of each run, to count how much it is played and to balance the game. There is no account and no nickname.
- October 30, 2026 notice revision — 10key Survival launch pre-registration (section 13): it is now complete the moment you sign up, with a receipt email that has a cancel link instead of a confirmation button, and the emails now also come in German and Japanese. Added the optional Google Ads ad measurement (conversion measurement) that only runs if you allow it, its legal basis and how to decline.
- October 25, 2026 notice revision — added run records to section 13: the short record of every finished run that the store apps send with the random install ID (what it contains, which versions send it, why, the legal basis, retention 90 days).
- October 24, 2026 notice revision — added the launch pre-registration on the 10key Survival web page to section 13: what we store (email address, language, consent text version, status and times), double opt-in, processing based on consent and how to withdraw it, Resend (USA) as the email processor and the transfer basis, and retention (30 days).
- Notice update October 23, 2026 — Added to section 13 the crash reports and daily usage counts that the Android and iOS apps of 10key Survival send (and, for the first error of a session, the web version): what they contain, which versions send them, why, the legal basis (legitimate interests), recipients, retention (120 and 183 days for usage counts, 7 and 30 days for crash reports) and why deleting the guest account does not delete them. Cross-references were added to the under-14, CrazyGames, retention and “Ads and analytics” text.
- Effective October 20, 2026 (v4.3) — 10key Survival in the Android and iOS apps (section 13): the House Duck guest account (the age question, of which only the age band is used; the nickname; the anonymous sign-in at Supabase Auth; sign-in tokens kept on the device; logging out), in-app purchases of gem keycaps and the Revive Pass through Google Play Billing and the App Store with verification on our server (purchase records with a hash of the purchase token, the Revive Pass record, gem records; a hashed login ID passed to Google Play), the legal bases for this processing, Google and Apple as recipients, retention, what is kept after an account is deleted and why, and account deletion in the app or by email. Nothing changes for players on CrazyGames or the web.
- Name update October 20, 2026 — The game formerly called 10KEY is now called 10key Survival (딸깍 서바이벌 in Korean); section 13 and the other mentions use the new name. Nothing else changed: the same data is processed for the same purposes, and your rights are the same.
- Effective October 20, 2026 (v4.2) — Added section 14 on support requests and House Duck’s operations tools: support email handled in Google Workspace (Gmail), the staff-only operations console with Google sign-in, the console’s access to the support mailbox through the Gmail API (
gmail.modify), and the Limited Use statement for information received from Google APIs. Added Google Workspace and Google Identity Services to the providers in section 4. “Changes” is now section 15. - Effective October 19, 2026 (v4.1) — Added 10key Survival (section 13): offline play with saves only on the device, optional online rankings for players signed in to their platform account, the data stored for them, retention, deletion on request, and ads and purchases handled by the platform or store. The separate 10key Survival privacy notice of October 18, 2026 was folded into this Policy. Clarified that sections 2 to 12 describe Quirky Ball and the website unless stated otherwise; “Changes” is now section 14.
- Effective October 5, 2026 (v4.0) — Made this the shared policy for all House Duck games, with Quirky Ball as the current title; updated it for Quirky Ball 2.0.0: Google sign-in on iOS, account loading on another device, in-app Quick Report, fair-play records, invitations, stability diagnostics inside the optional usage analytics, Google Ads conversion measurement under that consent, redacted support summaries with the Google Gemini API, mailbox retention, and purchase restoration. Removed the AppLovin MAX preparation notice: AppLovin will not be used, and Google AdMob remains the only ad network.
- Notice update September 9, 2026 — Clarified age bands, the combined optional analytics choice and 24-hour unsent queues, no retroactive expansion of Firebase-only choices, and ad-reward conditions.
- Notice update September 8, 2026 — Clarified processing countries, recipients/transfers, notice versus consent, minors, and rights requests.
- Analytics notice update September 5, 2026 — Distinguished Supabase-backed operations and first-party analytics from optional Firebase Analytics, and documented consent, refusal, and withdrawal in settings.
- Clarity update September 5, 2026 — Clarified website requests and local preferences, deletion-request verification, and the rights-request process.
- Effective August 24, 2026 (v3.0) — Converted to a shared House Duck policy and added Android/Google Play, iOS with Sign in with Apple, advertising consent, and one-time purchase processing.