Cluck Force Privacy Policy

Effective date: October 21, 2026

Developer: TheReki

This Privacy Policy applies to the mobile game Cluck Force: Chicken Idle RPG (Korean title: 치킨특공대 : 방치형 RPG 닭 키우기; package name com.shyos.chicken), developed and published by TheReki.

Cluck Force (the "App") is an idle game in which a squad of chickens chops its way forward on its own. The App has no sign-up and no account system of its own. Your game progress is stored on your device. If you are signed in to Google Play Games on Android, or to Game Center on iOS, a copy is kept encrypted in your own account (your Google account on Android, your iCloud on iOS) so that you can continue on another device (sections 1.1 and 1.2). The developer's server stores only the minimum information needed for the leaderboard.

This policy explains what information the App processes, for what purposes, and which third-party services it uses.

1. Information stored on your device

The following is stored on your device and is not sent to the developer's servers. The only case in which it leaves your device is the account save described in 1.1 and 1.2.

Game progress: stages and records, currencies, weapons, wardrobe, ranch, pets, relics, and mission, season pass and achievement progress
Settings: sound, handedness, notifications on or off
A record of purchases the App has already delivered (so the same purchase is never delivered twice)
A purchase-management identifier that the App generates at random when it is installed (section 4.1)

In the released App this save file is encrypted with a key protected by the device's secure key store. It is excluded from operating-system backups and device-to-device transfer, and it is deleted when you uninstall the App.

1.1 Account save — Google Play Games "Saved Games" (Android)

If the device is signed in to Google Play Games, the App uploads a copy of the save above to Google Play Games Saved Games so that you can continue after changing devices or reinstalling the App.

What is uploaded: game progress, currencies and the record of their changes, the record of purchases the App has already delivered, the purchase-management identifier (section 4.1), and the time you last played
Where it is kept: your own Google account (an app-specific area of Google Drive that is not shown in the Drive interface). It is not stored on any server operated by the developer, and the developer does not read this copy.
The copy is encrypted before it is uploaded and can be opened only with that account.
When it is uploaded: when the App leaves the screen, right after a purchase or a rebirth, and otherwise about once every five minutes when something has changed
Another device signed in to the same account (or a reinstalled App) receives this copy and continues from it. If that device already has progress, the App first asks which one you want to continue with.
Nothing is uploaded if you are not signed in to Play Games (progress stays on that device only). The account save on iOS is described in 1.2.
See section 6 for how to delete it.

1.2 Account save — Game Center "Saved Games" and iCloud (iOS)

If the device is signed in to Game Center and iCloud Drive is turned on, the App uploads a copy of the save above to Game Center Saved Games so that you can continue after changing devices or reinstalling the App.

What is uploaded, and when: the same as in 1.1.
Where it is kept: your own iCloud (this App's iCloud storage area). It is not stored on any server operated by the developer, and the developer does not read this copy.
The copy is encrypted before it is uploaded and can be opened only with that Game Center account.
Another device signed in to the same account (or a reinstalled App) receives this copy and continues from it. If that device already has progress, the App first asks which one you want to continue with.
Nothing is uploaded if you are not signed in to Game Center or iCloud Drive is turned off (progress stays on that device only).
The account save on Android and the account save on iOS do not carry over to each other.
See section 6 for how to delete it.

2. Leaderboard — information stored on the developer's server

For your record to appear on the App's leaderboard, the following is stored on a server operated by the developer (Google Firebase, Seoul region, Republic of Korea).

Identifier: A unique value that tells players apart. If the device is signed in to Google Play Games (Android) or Game Center (iOS), a unique value linked to that account is used; otherwise an anonymous value tied to the device. It is never shown on screen or to other players. The App does not receive your email address, real name or contacts.
Nickname: The name shown on the leaderboard. If you do not set one, an automatically assigned name (for example "Chick123") is used.
Records: Record stage, stages gained this season, the number of achievement tiers claimed and the counts they are based on (rebirths, cleared rounds, collections and so on)
Cosmetics: The title you wear, the outfit of the chicken you control, the number of medals
Country: Your device's region setting (a two-letter country code), used for the flag in front of your nickname. The App does not measure your location.
Timestamps and flags: When records were first and last submitted, and a flag used to hide illegitimate records

Visible to other players: nickname, flag, title, outfit, medal count, record and rank
Purpose: providing the leaderboard and preventing illegitimate records. It is not used for advertising. Usage statistics receive only an irreversibly transformed form of the identifier (section 4.3).
Device attestation (Firebase App Check — Google Play Integrity on Android, Apple's App Attest on iOS) is used to confirm that requests come from the genuine App.
Nicknames may not contain language that is offensive to others (profanity, sexual language, hate or discrimination, staff impersonation and the like). The operator may reset such a name to an automatic name or hide the entry from the leaderboard (Nickname Rules).
Reports: when you report another player's name on the leaderboard, the reported name and your identifier are stored on the server and reviewed by the operator. The reported name is hidden on your leaderboard, and the list of names you have hidden is stored with your leaderboard information.
This information is kept until you ask for it to be deleted (section 6).

3. Permissions the App requests

The App asks you directly about notifications and, depending on your region and device, two things related to advertising.

Notifications: To tell you when your away-time rewards are full and when your eggs are full. Notifications are scheduled on the device, not sent from a server. Required? Optional — every feature works without it, and you can turn it off in settings at any time.
Consent for advertising and analytics (European Economic Area, United Kingdom, Switzerland): Through Google's consent window, the App asks for your consent to store and read information on your device for advertising and usage statistics, and to use it for personalised ads. Required? Optional — every feature works without it (ads are shown without personalisation), and you can change your answer at any time under "Ad Privacy Settings" in settings.
Permission to track (iOS): Through the operating system's prompt, the App asks whether it may use your device's advertising identifier so that the ads you choose to watch are more relevant to you. Required? Optional — every feature works without it (ads are shown without the identifier), and you can change it at any time in the device settings.

If you are in one of the US states that give this right, you can opt out of the sale or sharing of your personal information under "Ad Privacy Settings" in settings.

Internet and network-state access, billing and advertising-ID access (Android) are used for time checks, showing ads, verifying purchases and the leaderboard; they are normal permissions granted by the operating system without a separate prompt. The Wi-Fi state access, vibration, Google Play licence check and (on Amazon devices) privacy attestation permissions that the ad companies' SDKs (4.2) use to show ads are normal permissions of the same kind (Android). The App does not request access to location, camera, contacts, photos or files.

4. Third-party services

4.1 RevenueCat (purchase management)

RevenueCat, Inc. is an external platform that verifies and manages in-app purchases made through the app store.

Information processed: purchase history (product, time of purchase, refund status), the transaction identifier issued by the store, and basic device and app information (platform, app version, country and the like)
Because the App has no account system, an identifier that the App generates at random when it is installed is used (it is not derived from any device or account information). The App does not pass your name, email or other identity information to RevenueCat. A device that continues from an account save (sections 1.1 and 1.2) keeps using the identifier in that save so that your purchase history is not broken.
The App does not use the feature that passes the advertising identifier to RevenueCat.
To link purchase events recorded by RevenueCat's servers to the same analytics record, the App passes the randomly generated Firebase app-instance identifier described in 4.3. It identifies an installation, not a person, device or Google account.
Payment itself is handled by the store (Google Play on Android, the App Store on iOS). Neither the App nor RevenueCat receives card numbers or other payment-method details.
To take back what was delivered for a refunded purchase, installations that have made a purchase send the identifier above to a server operated by the developer (Google Firebase) to check for refunds.
RevenueCat privacy policy: https://www.revenuecat.com/privacy

4.2 Google AdMob (advertising)

Ads in the App are rewarded ads that you choose to watch in exchange for a reward.

Information processed: advertising identifier (Android advertising ID; on iOS, the advertising identifier only if you allowed tracking), IP address, ad and app interaction records, diagnostics
Purpose: serving and measuring ads, analytics, fraud prevention
Whether ads are personalised follows your answer in the consent window in the European Economic Area, the United Kingdom and Switzerland, and whether you opted out of the sale or sharing of your personal information in certain US states. Where an answer is required first, the App does not request ads until you have answered.
On iOS, ad performance may be measured through Apple's SKAdNetwork even if you did not allow tracking. No information that identifies you or your device is passed along in that case.
If you have purchased ad removal, no ads are shown (you receive the reward without an ad).
Google's advertising policies: https://policies.google.com/technologies/partner-sites
Ads from other ad companies: through AdMob mediation, an ad may also be served by one of the companies below. The SDK of the company serving the ad processes the information above for the same purposes, and whether ads are personalised follows the same consent or opt-out described above.
AppLovin privacy policy: https://legal.applovin.com/privacy/
Unity Ads privacy policy: https://unity.com/legal/game-player-and-app-user-privacy-policy
Liftoff Monetize privacy policy: https://liftoff.ai/privacy-policy/
Pangle privacy policy: https://www.pangleglobal.com/privacy/enduser-en

4.3 Firebase Analytics and Crashlytics (usage statistics and diagnostics)

Firebase is Google's app analytics and crash-diagnostics platform.

Purposes: diagnosing and fixing crashes and other faults; improving the App using basic usage figures such as how far players progress at each stage of the game; measuring purchase and advertising performance
Records the App sends: session summaries (counts such as time played and stages gained), which windows were opened, tutorial and rebirth progress, rewarded-ad rewards, completed purchases, tier markers such as whether ad removal is owned, and shares (section 4.8)
Text you write, such as your nickname, is never included in these records.
To count a player who uses the same account on several devices as one person, an irreversibly transformed form (a hash) of the leaderboard identifier (section 2) is sent as the user ID. The identifier itself is not sent.
Information the SDK processes automatically: a randomly generated installation identifier, the advertising identifier (on iOS only if you allowed tracking — plus a vendor identifier that is the same only across this developer's apps), app version, device model, OS version, language and country settings, the install source reported by the store (such as an ad or a share link), and an IP address that may be used to estimate approximate region. Crashlytics additionally processes crash diagnostics (stack traces, app state at the time of the fault, an installation identifier).
The four consent signals — analytics storage, ad storage, ad user data and ad personalization — follow your region and your answer. In the European Economic Area, the United Kingdom and Switzerland they follow your answer in the consent window (all four are off if you decline); in certain US states, ad user data and ad personalization are off if you opt out of the sale or sharing of your personal information; elsewhere they are granted.
Crash diagnostics are collected only in the released version of the App.
Firebase privacy information: https://firebase.google.com/support/privacy
Google privacy policy: https://policies.google.com/privacy

4.4 Firebase Authentication, App Check, Cloud Functions and Firestore (leaderboard)

The leaderboard information in section 2 is processed and stored on Google Firebase. Google acts as a service provider processing it on the developer's behalf.

Firebase Authentication creates and verifies the identifier in section 2. If the device is signed in to Google Play Games, the Play Games profile identifier and the profile information Play Games passes along with it (gamer name, profile picture address) may be kept in Firebase Authentication as part of sign-in verification. If the device is signed in to Game Center (iOS), the Game Center player identifier and Game Center nickname may be kept in the same way. The App does not display this profile information or send it anywhere else.
The leaderboard store cannot be read or written directly by the App; only the developer's server functions access it.

4.5 Google Play Games Services and Apple Game Center (sign-in and Saved Games)

If automatic sign-in to Google Play Games is enabled on the device, the App uses that sign-in for two things: creating the leaderboard identifier (section 2) and the account save (section 1.1). Play Games sign-in, profiles and the storage of Saved Games are handled by Google. The App does not use Play Games leaderboards or achievements. You can play and use the leaderboard without signing in (an anonymous value tied to the device is used instead, and progress stays on that device only). You can disconnect in the Play Games app's settings.

On iOS, if the device is signed in to Game Center, the App uses that sign-in for the same two things: the leaderboard identifier (section 2) and the account save (section 1.2). Game Center sign-in and profiles, and the storage of Saved Games in iCloud, are handled by Apple. The App does not use Game Center leaderboards or achievements. You can play and use the leaderboard without signing in (an anonymous value tied to the device is used instead, and progress stays on that device only). You can sign out of Game Center in the device settings. Apple privacy policy: https://www.apple.com/legal/privacy/

4.6 Google Play and the App Store (in-app review and new-version check)

The App may show the review dialog provided by the store (Google Play on Android, the App Store on iOS). That dialog and any rating or comment you leave are handled entirely by that store; the App is not told whether you wrote a review or what it said.

To let you know when a new version is out, the App may ask the store for its latest version. On Android, Google Play on the device answers; on iOS, the App asks Apple’s public lookup address (itunes.apple.com), sending only the App’s identifier and the device’s region code. These requests carry none of your information; those servers may keep ordinary web access logs (IP address, time of access). You get the new version from the store yourself — the App does not download or install it on its own.

4.7 Time checks

To obtain a trustworthy current time, the App sends content-free requests to a few public web servers (microsoft.com, apple.com, cloudflare.com). These requests carry none of your information; those servers may keep ordinary web access logs (IP address, time of access).

4.8 Sharing

When you tap share in the game, the operating system's share sheet opens with the game's share link (https://chickensquad.web.app/play/…). You choose what to send and to whom. The App uses the kind of app you picked to decide a reward, and sends where you shared from and the kind of app you picked (the app's name if it is on the list of messengers and social networks, otherwise "other") as part of the analytics records in section 4.3. It does not send the shared text or the recipients.

If the person who receives the link does not have the App, they are taken to their device's store, and the store address carries a marker saying they came from a share link. After installation this marker is processed as the install source in section 4.3; it does not say who sent the link.

When it sends them to the store, the share page adds one to a count kept on the developer's server for that day, page language and device kind (Android, iOS or other), to see how often share links are opened. This request carries none of your information; that server may keep ordinary web access logs (IP address, time of access).

5. Retention and deletion

On-device data: deleted when you uninstall the App. You can also reset your progress with "Start over" in settings.
Account save (sections 1.1 and 1.2): kept in your account (your Google account on Android, your iCloud on iOS) until you delete it. It remains after you uninstall the App, and you can continue from it if you reinstall with the same account.
Leaderboard information: kept until you ask for it to be deleted.
Purchase records: kept by RevenueCat and the store for as long as needed to provide the service and meet legal obligations (retention of transaction records).
Advertising, analytics and crash-diagnostics information: subject to Google's retention policies and settings.

6. Your rights and choices

Changing your nickname: once a day, on the leaderboard screen.
Requesting deletion of leaderboard information: to have the leaderboard information stored on the server (section 2) deleted, write to the contact in section 9 with your nickname and record stage. We will delete it after confirming. If you keep using the App afterwards, a new leaderboard entry is created.
Advertising identifier: you can reset or delete the advertising ID in your device settings. On iOS, you can change the permission to track in the device settings (Privacy & Security → Tracking).
Ad privacy settings: in the European Economic Area, the United Kingdom, Switzerland and certain US states, the App's settings window shows "Ad Privacy Settings". There you can change your consent for advertising and analytics, or opt out of the sale or sharing of your personal information.
Notifications: you can turn them off at any time in the App's settings or the device settings.
Disconnecting Play Games (Android): you can sign this game out in the Play Games app's settings.
Signing out of Game Center (iOS): you can sign out under Settings → Game Center on the device.
Deleting the account save (Android): you can delete this game's data in the Google Play Store app under Settings → General → Play Games profile → Privacy & settings (Google may rename these menus — see Google's help page). If you keep using the App while signed in to Play Games afterwards, a new copy is uploaded.
Deleting the account save (iOS): you can delete this game's data on the device under Settings → your name (Apple Account) → iCloud → Storage (Apple may rename these menus). If you keep using the App afterwards while signed in to Game Center with iCloud Drive turned on, a new copy is uploaded.
Requesting deletion of purchase or analytics records: contact us to have purchase-related records, or analytics records linked to your installation, deleted. Tapping the version line at the bottom of the App's settings window copies support information; sending it along speeds things up. Transaction records kept by the store are subject to the store's policies.

7. Children's privacy

The App is not directed to children under 14 (or under the age of digital consent in your country), and it does not knowingly collect personal information from children.

8. Security measures

Encryption of the on-device save file, with the key protected by the operating system's key store
Encryption of the account-save copy (encrypted before upload; it can be opened only with that account)
TLS encryption for all external communication
No direct access to the leaderboard store (server functions only), plus device attestation

9. Changes and contact

If this policy is revised because of changes in law or in the App's features, the changes and their effective date will be posted on this page.

For questions about privacy, contact:

Developer and privacy contact: TheReki
Email: shyos0@naver.com