Privacy Policy

1. At a glance

Coo’s Joint is a single-player Android game. Core progression is saved on the device in the app’s local save file. The game does not require a player account and does not operate a cloud-save database.

The project currently includes an AdMob integration in test mode using Google test IDs; production ad IDs are not configured. This policy describes the additional data handling that may occur if optional rewarded ads are enabled for a public release. No separate gameplay-analytics provider is currently identified in the project. If the release configuration differs, update this policy before distribution.

2. Who operates the game

Publisher / data controller: [Publisher’s legal name] (“we,” “us,” or “our”).

Privacy contact: [privacy email]
Mailing address, if required: [Business mailing address]
Support contact: [Support email or support URL]

Google Play distributes the game. Google may separately process information under its own terms and privacy notices. This policy covers the game publisher’s practices and describes relevant third-party SDK processing included in the app.

3. Information stored by the game

Local gameplay save

The game writes its save to user://coos_joint_save_v1.json in Godot’s app-specific user-data area. The save can contain gameplay progress such as Star Beans and other game currencies, business ownership, managers and upgrades, settings, statistics, story/progression flags, and save timestamps.

The game code does not send this save file to a publisher-operated server or cloud-save service. The file is used on the device to restore local progress. The game does not currently provide account-based or cross-device cloud synchronization.

You can use the in-game reset control, clear the app’s storage in Android settings, or uninstall the app to remove local game data. Android system backup and restore behavior can depend on device/account settings and the final Android manifest; it is not a game-managed cloud-save feature. The publisher cannot recover a local save that has been erased or lost.

Messages you send us

If you email support or privacy, we receive the information you choose to send, such as your email address, message, and any diagnostic details you include. We use it to respond, troubleshoot, and keep records required for security or legal purposes. Please do not send passwords, payment-card details, or other sensitive information.

4. Advertising and analytics

Optional rewarded ads

If production rewarded advertising is enabled, the app may request an optional rewarded ad through Google Mobile Ads (AdMob). You choose whether to start a rewarded-ad flow. Ads may be unavailable because of network, inventory, regional, or consent settings; the game does not promise that an ad will always be available.

Google’s published Android data-disclosure guidance for Google Mobile Ads describes automatic collection/sharing that can include an IP address (which may be used to estimate general location), product interactions such as app launches, taps, and video views, diagnostic information, and device/account identifiers such as the Android advertising ID or App Set ID. The exact data and purposes depend on the SDK version, app configuration, ad partners, region, and user choices. These providers may use data for ad delivery, measurement, analytics, security, and fraud prevention.

The current project uses Google test IDs and is_real=false; those are development settings, not production ad credentials. Before release, the publisher must verify the exact SDK and mediation versions and update this policy and the Play Console Data safety form to match them. If ads are removed, revise this section to describe the shipped configuration instead.

Gameplay analytics / telemetry

No separate gameplay analytics service is currently identified in the project configuration. If we add analytics or telemetry, we will update this policy to name the provider, explain the information collected and purposes, and update applicable consent and store disclosures before enabling it.

5. Device identifiers, cookies, and similar technologies

The native core game does not operate a first-party website or use browser cookies for gameplay. Advertising SDKs or ad content may use advertising/device identifiers, SDK storage, cookies, or similar technologies to deliver and measure ads, prevent fraud, and remember privacy choices. Some identifiers or network signals may be treated as personal data under applicable law.

You can review or reset Android advertising-ID controls in your device settings and manage Google advertising settings through Google’s account tools. These controls do not replace any consent or opt-out rights that apply under local law. Where required, the production app must present an appropriate consent/privacy-choice flow before the relevant ad processing occurs and provide a way to revisit choices; the publisher must confirm that flow is implemented in the release build.

6. How information is used, shared, and retained

• Local game data: used on your device to save and restore progress; not sent to us by the game code.
• Advertising providers: if enabled, Google Mobile Ads and any configured mediation/ad partners may receive information from their SDKs to provide, measure, secure, or improve ad services, subject to their terms, settings, and applicable privacy choices.
• Support: messages are used to reply and address the issue.
• Legal and safety reasons: information may be disclosed if required by law or reasonably necessary to protect users, the service, or legal rights.

Legal bases, where applicable

The legal basis depends on where you live and the final feature/SDK configuration. It may include consent for personalized advertising or non-essential storage where required, legitimate interests for support, service security, and fraud prevention, and compliance with legal obligations. The publisher must confirm the applicable basis and implement the corresponding consent or opt-out flow before enabling production ad processing.

We do not operate an account database or sell the local save file. We do not receive local save data through the game. Third-party advertising processing is governed in part by the provider’s own privacy practices; it is not accurately described as “no data collection” merely because the game has no account or cloud save.

The local save remains until it is reset, app storage is cleared, or the app is removed, subject to Android backup behavior described above. Support correspondence is retained only as reasonably needed to resolve the request, maintain security records, and meet legal obligations. Ad/analytics providers apply their own retention periods; consult their current notices for details.

Some providers may process information in countries other than the one where you live. Any such processing is subject to the provider’s safeguards and applicable law.

7. Your choices and privacy rights

You may clear local game data using the in-game reset feature or Android app-storage controls. The game has no player account, so there is no account profile to close. For personal information handled by us through support, contact the privacy address above to request access, correction, deletion, restriction, or other rights available in your location. We may need to verify a request and may retain information where the law permits or requires it.

Depending on your location and the final ad configuration, you may also have rights to object to or opt out of targeted advertising, sale/sharing, or certain processing. We will provide the required in-app privacy options or consent controls for the release configuration and honor valid choices. Where you live in the EEA, UK, or another region with consent requirements, personalized advertising must not be enabled before the required consent is obtained. Contact us if you cannot find or use a privacy control.

8. Adults and children’s privacy

Coo’s Joint is intended for adults aged 18 and older and is not designed or marketed to children. The app does not currently verify a player’s age; an 18+ intended audience is not itself an age-verification mechanism. If you are under 18, do not use the game.

We do not knowingly solicit personal information from children under 13. If you believe a child under 13 has sent personal information to us, contact the privacy email listed below; we will review the request and take appropriate steps. Before release, the publisher must make the Play Console target-audience, content-rating, and ad settings consistent with the actual game and this 18+ audience statement.

9. Security

The save is kept in the app-specific storage area provided by Android/Godot. The game does not currently describe the local JSON save as encrypted. No method of storage or transmission is perfectly secure. Third-party services apply their own safeguards; consult their current documentation for details.

10. Changes to this policy

We may update this policy when the game, SDKs, legal requirements, or data practices change. We will update the “Last updated” date and, where required, provide additional notice or request consent. Continued use after an effective update is subject to applicable law and any consent requirements.

11. Contact

Related document: Terms of Service and End User License Agreement.

Third-party privacy references

• Google Privacy Policy
• Google Mobile Ads SDK — Android data disclosure
• Google Play Data safety requirements

Google’s SDK disclosures can change. Confirm the disclosure for the exact SDK/version and mediation partners included in the released app.