Privacy Policy

1. Progress and information stored on your device

The game stores your coin balance, unlocked maps and items, equipped cosmetics and kits, supply inventory, scores, run statistics, recent run history, and saved splatter marks. It also stores your selected map and audio preferences. These records let you keep playing where you left off and prevent the same coin reward from being granted twice.

A broad age category is stored locally to apply privacy protections. The game does not ask for an exact date of birth. The age category remains on your device; the game passes the applicable child or under-age treatment settings to Google’s advertising and consent tools, rather than including your age category in a cloud save.

The game also keeps local synchronization records, including a randomly generated installation identifier, saved progress, revisions, and timestamps, even when cloud saving is unavailable. After successful Google Play Games sign-in and synchronization, these records can include a hashed player identifier to distinguish accounts. Local backup copies help recover interrupted saves and resolve conflicting progress. These identifiers are separate from advertising identifiers.

2. Google Play Games, cloud saves, and Google API access

The Android game includes Google Play Games Services for signing in and saving progress with Google. You can play locally without signing in to Google Play Games. Cloud saving operates only in builds where the service is configured and sign-in succeeds. Google sign-in and cloud saving are offered only to eligible players after the game’s age check and your choice to enable them. The game explains the information used before you enable cloud features and obtains consent where required. Once enabled, synchronization may resume in later sessions. You can manage cloud saving in Menu → Privacy; turning it off stops further game synchronization but does not erase existing saves.

The game receives your Play Games player identifier to associate progress with the correct account. When synchronization is active, Google stores and returns your saved career progress, map records, and synchronization metadata, including installation identifiers, revisions, and timestamps. This enables restoration and play across devices. Audio settings, an unfinished run, age category, ad consent state, and purchase ownership are not included in the cloud save.

Google also processes Play Games profile information, such as a gamer name and avatar, when you create or update your Play Games profile, and service analytics and diagnostic information to operate and improve Play Games. The game’s own integration uses the player identifier and saved-game features described above. See Google’s Play Games data disclosure.

Google handles authentication and associated authorization. The game uses this access for player identification and saved-game functionality; it does not request access to your Gmail, contacts, or general Google Drive files, or ask for your Google password. The game does not send cloud-save contents or the Play Games player identifier to AdMob. This integration does not send Google access tokens or saved games to a Headstrong-operated server.

Use of information received through Google APIs is limited to the game features described here and is subject to the Google API Services User Data Policy, including its Limited Use requirements where applicable. You can review or remove account connections through Google’s account connection controls. Removing access may stop cloud features; it does not by itself erase existing local or cloud saves.

3. AdMob advertising and privacy choices

The Android game integrates Google AdMob for interstitial ads between runs and optional rewarded ads. When the advertising service is active, Google’s Mobile Ads SDK collects and shares information for advertising, analytics, and fraud prevention. This can include your IP address and approximate location derived from it; advertising and other device or account identifiers; app and ad interactions, such as launches, taps, and video views; and diagnostic information, such as app or SDK performance. The particular information processed depends on the device, consent, SDK version, and ad configuration. See Google’s Mobile Ads data disclosure and Google’s Privacy Policy.

App set ID: Google’s SDK may also handle this identifier for essential non-advertising purposes, such as analytics and fraud prevention. We limit its use to those purposes: it must not be used for personalized ads or ad measurement, or linked with advertising identifiers or personal and sensitive data for advertising purposes. The game’s own code does not read or combine advertising IDs and app set IDs.

The game uses Google’s User Messaging Platform to obtain consent status and show privacy messages when required. Google’s consent tools process and store your choices and whether privacy options need to be available. When Google makes this control available, open Menu → Privacy → Privacy Options to review or change your choices. The Privacy menu and its link to this policy are always available, including when no ads are shown. The game refreshes consent information at launch for the applicable advertising flow, applies age-related protections, and checks Google’s consent-status signal before requesting ads. You can also manage your advertising ID through Android settings. Declining personalized ads does not necessarily stop all ads or all processing needed to serve and secure ads.

For children and players whose age is unknown, the game does not request personalized advertising or remarketing, and does not transmit the Android advertising ID or the other device and network identifiers prohibited by Google’s Families requirements. Any ads shown to these players use appropriately configured advertising SDKs and ad sources eligible under Google Play’s Families requirements. If the necessary protections cannot be applied, the game does not request ads for those players. Contextual ads can still involve limited processing, such as an IP address, ad interactions, and diagnostics, to serve ads and prevent fraud.

Once Ad Free ownership is verified, the game disables new ad requests and removes interstitial and rewarded ads. Buying Ad Free does not delete information already processed by Google or disable Google Play Billing or cloud saves.

4. Google Play purchases

Google Play processes optional in-app purchases. The game handles purchase details such as the product identifier, purchase state, signed receipt, and purchase token to verify ownership, acknowledge the purchase, and restore the benefit. A verified receipt and signature are cached in the app’s private device storage so the benefit can remain available offline.

Google handles payment information through its purchase flow. The game does not ask for or receive your payment card number. Purchase ownership is checked with Google Play separately from your saved game, including after a reinstall. Google’s transaction records are governed by its policies and any applicable retention requirements.

5. Diagnostics and contacting us

The game writes operational warnings and error/status information to local game or Android logs to help identify saving, sign-in, advertising, and billing failures. There is no separate Headstrong analytics or crash-reporting SDK or automatic upload of these game logs to a Headstrong server in this implementation. Google’s SDKs and the Android/Google Play platform may independently process usage and diagnostic information under their own policies and your settings.

If you email contact@headstrong.group, we receive your email address, message, and any attachments you choose to send. We use that information to respond, investigate the issue, or handle your privacy request. Please do not send passwords, payment card details, or other information that is unnecessary for your request.

6. Who processes information and how it is protected

Google provides distribution, Play Games authentication and cloud storage, advertising and consent tools, and purchase processing. Google and the advertising partners involved in serving an ad may process advertising data as described in Section 3, subject to the applicable configuration and privacy choices. Ads and links can take you to other companies’ services, where their own privacy policies apply. Our email service providers process the support correspondence you choose to send us so that we can receive and respond to it.

We do not sell personal and sensitive user data. Information is used and shared for the purposes and with the service providers described in this policy. The game does not operate a separate Headstrong player-account or cloud-save backend. The game’s code does not send your saved progress, Play Games player identifier, or purchase receipts to advertising services. Google may process information in countries other than your own under its Privacy Policy.

Local safeguards: on Android, save files, synchronization records, and cached purchase receipts are stored in the app’s private storage, which relies on Android’s access controls and your device’s protections. The game verifies signed purchase receipts before applying purchase benefits and stores a hash of the Play Games player identifier in local synchronization records.

Network safeguards: authentication, cloud synchronization, advertising, and purchases use Google’s SDKs and services. Google documents TLS encryption in transit for Mobile Ads data and HTTPS for Play Games data. Payment details are handled in Google Play’s purchase flow. No storage or transmission method can be guaranteed completely secure.

7. Retention, deletion, and your controls

Request deletion of Egg Drop Commando information: email contact@headstrong.group and identify Egg Drop Commando and the information you want removed, such as a support conversation or game-associated data. You can submit a request without reinstalling the game. We may ask for information necessary to verify your request and will explain the steps, expected timing, and any records that must be retained. Do not send passwords, payment card details, or access tokens. For information held independently by Google, the controls below provide a direct deletion route.

• Local progress: save files and synchronization records have no scheduled expiry. Open Menu → Privacy → Delete game data to remove local progress and its synchronization backups and recovery copies. The game stops synchronization before deletion so that a pending write cannot immediately restore deleted progress. This can permanently remove progress that has not been synchronized. Privacy preferences and purchase entitlement records are managed separately; clearing the game’s app storage or uninstalling it removes the app’s remaining local records.
• Cloud saves: uninstalling or clearing app storage does not remove the copy held by Google. If you use cloud saving, Delete game data also offers deletion of the game’s cloud save for the signed-in account, with a confirmation of the selected scope. Cloud deletion requires a connection and is complete only after Google confirms it; a failed or pending request is not reported as complete. Cloud saves otherwise remain until deleted through the game or Google’s controls. You can also use Google’s controls for deleting Play Games data without reinstalling the game. A remaining save on another device can be uploaded again if synchronization resumes, so turn off synchronization and remove local copies on your other devices when you want to remove progress completely.
• Purchase records: deleting progress does not cancel a purchase or erase Google’s transaction records. A later successful ownership check can restore your purchase entitlement. Cached receipts remain until app storage is cleared, the app is uninstalled, or ownership verification updates them.
• Age, ads, consent, and platform records: the local age category remains until app storage is cleared or the app is uninstalled. Google’s consent tools retain and update choices under their applicable rules; use Privacy Options when available to change them. Google controls retention and deletion of information held independently by its services under its policies and account controls. Device-log retention depends on the platform.
• Support correspondence: messages and attachments are retained for as long as needed to resolve your request, maintain relevant support records, or meet applicable legal obligations. You can request deletion using the contact above. If information must be retained for a legitimate reason, we will explain the applicable reason when responding to your request.

Depending on your location, you may have rights to access, correct, delete, restrict, or object to processing of personal information, or withdraw consent. Contact us to make a request about information we handle. Headstrong cannot directly delete your Google Account or Google’s independently held transaction and service records; use Google’s linked controls for those records. The game does not create a separate Headstrong account.

8. Children and families

Egg Drop Commando is intended for a mixed audience, including children and adults. Before enabling age-dependent services, the game uses a neutral age-category screen to choose appropriate privacy protections. It stores the broad category locally, without requesting an exact date of birth. Players whose age is unknown receive the more restrictive treatment. This screen is not identity verification, and an advertising consent choice is not treated as proof of age.

Children and players whose eligibility has not been established can play locally without Google sign-in. Google sign-in and cloud features are not enabled for players who do not meet the relevant service and consent requirements. Advertising for children and players of unknown age follows the restrictions in Section 3. The game does not use their information for personalized advertising or remarketing.

Parents and guardians should review the game’s Google Play age rating, advertising, purchases, and Google account controls, and supervise use as appropriate. Google’s services have their own age and account requirements. If you believe a child has provided personal information to Headstrong Group LLC, or have concerns about a child’s use of the game, contact contact@headstrong.group so we can review the matter, delete information we should not retain, and help with available deletion controls.

9. Changes to this policy

We may update this policy as the game, its integrations, or applicable requirements change. The current version will remain available at this URL with an updated effective date. Where required, we will provide additional notice or obtain consent before a new use of information.

10. Contact Headstrong Group LLC

For privacy questions or requests relating to Egg Drop Commando, email Headstrong Group LLC at contact@headstrong.group. Please mention the game and describe your request.