Privacy Policy

1. Summary

Our games use analytics, ad-delivery, and local device storage to operate, improve gameplay balance, understand crashes and session flow, measure ad performance, and support features such as offline income. Some information is stored only on the player's device, while some information is processed by third-party service providers.

This policy explains what categories of data are collected, how the data is used, what third parties may process it, and what choices players may have depending on their device, platform, and region.

2. Information we collect

2.1 Information you provide directly

• If you contact us by email, we may receive your email address, the contents of your message, and any attachments or information you choose to send.
• If you choose to connect your Google Play Games account on Android to enable cloud save, we may receive your Google Play Games player ID and display name in order to associate your save data with your account.

Connecting a Google Play Games account is optional. The core gameplay does not require you to sign in. Our games do not require you to create an account with us or directly submit your real name, postal address, or phone number to play.

2.2 Gameplay and telemetry events

• Session number, session start time, and session duration.
• Whether a session ended normally or after an unexpected interruption or crash-related event.
• Boost and power-up usage within a session.
• First-launch time, total play time, upgrade purchases, upgrade levels, and the timing of unlocks or purchases relative to first launch.
• Which game objects or content were unlocked and when they were unlocked.
• Economy milestones, such as when players reach certain currency thresholds.
• Offline-income claim information, including reward amount and offline time.
• Return-to-game timing information, such as how long the player was absent before opening the game again.
• Advertising outcome events such as whether a rewarded advertisement was watched to completion or was requested but unavailable.

2.3 Information collected automatically by integrated third parties

• Device model, operating system version, app version, language, approximate country or region, and time zone.
• Install source or distribution source information where available.
• Anonymous or pseudonymous identifiers used by analytics or advertising SDKs.
• Ad interaction information, including ad requests, impressions, clicks, reward completion, and fraud-prevention signals.
• IP address and approximate geolocation derived from IP by service providers.
• Crash and error reports collected by Firebase Crashlytics, including stack traces, exception types, device state at the time of the crash, app version, OS version, device model, and a Crashlytics installation UUID.

2.4 Information stored locally on the player's device

• Session snapshot data used to calculate offline income or restore gameplay state.
• Pending offline reward values stored until the player claims them.
• Other local save information required for gameplay progression and settings.

3. How we use information

• To operate our games and core gameplay systems.
• To analyze retention, progression, economy balance, and feature usage.
• To diagnose technical problems, crashes, failed ad loads, and performance issues.
• To show advertisements, measure ad performance, and help prevent fraud or invalid traffic.
• To support local saves, offline-income systems, and cloud save functionality.
• To respond to player messages, support questions, or privacy requests.
• To comply with legal obligations and enforce our Terms of Service.

4. How we share information

We may share or make information available to the following categories of recipients:

• Service providers and SDK providers, including Google Firebase and Google AdMob, to provide analytics, diagnostics, advertising, measurement, hosting, fraud prevention, and related services.
• Platform providers, such as Google Play or Apple platform services, where necessary for distribution, cloud save, platform compliance, or account-linked platform features.
• Authorities or other parties where disclosure is required by law, regulation, legal process, or to protect rights, security, or the integrity of the service.

We do not sell personal information for money. If our practices materially change, we will update this Privacy Policy before applying the new practice.

5. Third-party services

Our games may use the following third-party service providers:

• Google Firebase (including Firebase Analytics and Firebase Crashlytics) for analytics, crash reporting, diagnostics, and related infrastructure.
• Google AdMob for advertising, monetization, measurement, and fraud prevention.
• Google Play Games Services on Android for cloud save authentication and player identification; Firebase Firestore for cloud save data storage and synchronization.
• Apple CloudKit / iCloud on iOS for cloud save synchronization, where applicable.

Relevant official resources:

• Google Privacy Policy
• Firebase Privacy and Security
• Firebase Crashlytics Data Collection
• AdMob Policies and Restrictions
• Google Play Games Saved Games
• Apple CloudKit

6. Advertising identifiers and ad personalization

Our games may use advertising identifiers to support personalized or non-personalized ads, subject to platform settings and any consent flows required by law.

Players can typically limit ad tracking, reset the advertising identifier, or disable personalized advertising through their device and platform settings.

In some regions, players may also see a consent message before personalized advertising or certain local-storage based ad functions are used, where required by law or platform policy.

7. Cloud saves

7.1 Android cloud saves via Google Play Games and Firebase Firestore

On Android, players may optionally connect their Google Play Games account to enable cloud save in supported games. When connected, save data is stored and synchronized through Firebase Firestore using the player's Google Play Games player ID.

Connecting a Google Play Games account is optional. If the player does not sign in, saves remain local to the device only.

7.2 iOS cloud saves via Apple CloudKit / iCloud

Where supported on iOS, save data may be synchronized through Apple CloudKit / iCloud. This may include game progression, save-state records, timestamps, and data needed to keep the player's progress in sync across Apple devices.

8. Data retention

• Local save and offline-income data generally remains on the player's device until the app is uninstalled or device storage is cleared.
• Email or support messages sent directly to us may be retained for as long as reasonably necessary.
• Analytics, advertising, and related telemetry may be retained by third-party providers according to their own retention policies.
• Cloud-save data may remain in the player's Google or Apple account environment until deleted according to platform behavior.

9. International processing

Third-party providers that support our games may process information on servers located in various countries. Information may be transferred outside the player's country or region.

10. Your rights and choices

• Players may contact us to request access to, deletion of, or additional information about data we control, where applicable.
• Players may manage advertising preferences through device and platform controls.
• Where consent is used for certain advertising or analytics activities, players may be able to change or withdraw those choices through the relevant consent interface or device settings.
• Local gameplay data can generally be removed by uninstalling the app or clearing app storage on the device.

11. Children's privacy

Our games are not directed to children under the age of 13. If you believe a child provided personal information in violation of applicable law, contact us so we can review the request.

12. Security

We take reasonable steps to reduce risk, but no method of storage, transmission, or processing is completely secure. Where supported by the relevant platform or SDK, data transmitted over networks is generally sent using standard secure transport methods such as HTTPS/TLS.

13. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will change the effective date shown at the top of this page. Material changes may also be communicated through the game, store listing, or another appropriate channel where required.

14. Contact

For privacy questions or requests, contact HouneTeam at info@houneteam.com.