Privacy Policy

Chico Ball (the "Game") · Beasy App Studio · Effective date: July 5, 2026

This Privacy Policy explains what information we collect when you play Chico Ball on iOS or Android, how we use it, and the choices you have. By playing the Game you agree to this policy.

1. Who we are

Chico Ball is developed and operated by Beasy App Studio. Contact: [email protected].

2. Information we collect

Account information. When you play as a guest we generate a random player identity tied to a device identifier. If you sign in with Apple, Google, Game Center, or Google Play Games we receive your provider user ID and, where you allow it, your name and email address. We never receive your passwords.
Gameplay data. Match results, scores, trophies, level and XP, in-game currency balances (coins/gems), items, missions, chests, friends list, and match history — required to operate the Game and its leaderboards.
Purchase data. If you buy gems, the purchase is processed entirely by Apple App Store or Google Play. We receive a purchase token/receipt to verify the transaction and deliver your items. We never see your payment card details.
Device and technical data. Device model, operating system version, app version, language, IP address (transiently, for connectivity), crash logs, and performance data.
Advertising identifiers. When rewarded ads are shown, Google AdMob may process your device advertising ID (IDFA / GAID), subject to your consent settings (App Tracking Transparency on iOS, ads personalization settings on Android).

3. How we use information

Operate the Game: accounts, matchmaking, multiplayer, leaderboards, friends, rewards.
Deliver purchases and prevent fraud (server-side receipt verification).
Show rewarded video ads that you choose to watch (Google AdMob).
Measure and improve the Game (Firebase / Google Analytics: sessions, retention, feature usage; Sentry: crashes and errors).
Send push notifications you opt in to (e.g. friend invites, rewards ready).
Comply with law and enforce our Terms of Service.

4. Third-party services

The Game uses these providers, which process data under their own privacy policies:

Google AdMob (advertising) — policy, how Google uses ad data
Google Firebase / Google Analytics (analytics) — policy
Sentry (crash and error reporting) — policy
Apple App Store / Google Play (sign-in, purchases, push delivery) — Apple, Google

5. Advertising choices

On iOS you can decline tracking via the App Tracking Transparency prompt and in Settings → Privacy. On Android you can reset or delete your advertising ID and opt out of ads personalization in Google settings. Where consent is required (e.g. EEA/UK), ads are non-personalized unless you consent.

6. Data retention & deletion

Account and gameplay data are kept while your account is active. You can request deletion of your account and associated data at any time by emailing [email protected] from within the Game's Settings → Account, or directly. We delete or anonymize your data within 30 days of a verified request, except records we must keep for legal, security, or fraud-prevention reasons (e.g. purchase records).

7. Children

The Game is not directed at children under 13 (or the minimum age required in your country). We do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will delete it.

8. Security

Data is transmitted over HTTPS/TLS and stored on access-controlled servers in the EU. No method of transmission or storage is 100% secure, but we work to protect your data using industry-standard measures.

9. International transfers & your rights

Depending on where you live (e.g. EEA/UK GDPR, California CCPA), you may have rights to access, correct, export, restrict, or delete your personal data, and to object to processing. Contact us at [email protected] to exercise them. You may also lodge a complaint with your local data-protection authority.

10. Changes

We may update this policy from time to time. Material changes will be announced in the Game or on this page; the effective date above always reflects the current version.