KaCha Privacy Policy

Last updated: 2026-08-07

ka-cha ("we", "us") respects your privacy. This policy explains what personal data we collect when you use KaCha (the "App"), why we collect it, and what control you have over it. It is written to meet Taiwan's Personal Data Protection Act, the GDPR, and the CCPA/CPRA.

1. Data controller

Name: ka-cha
Contact: ka-cha.bouncing089@passinbox.com

2. What we collect and why

Data	What it is	Purpose	Source
Email address	Returned by Sign in with Apple	Create and manage your account; support	Sign in with Apple
Name	Returned by Apple only on first authorization	Pre-fill your player name	Sign in with Apple
Date of birth	Entered by you at sign-up	Age gate; birthday card	You
Player name	A public name you choose	Leaderboards, level credits, printed on cards (see §5)	You
Account ID	Internal identifier we generate	Link your progress, cards and wallet	Generated
Photos	Photos you upload as a creator to build a level	Generate and publicly display the level	You
Gameplay records	Session times, scores, cards held, gem transactions	Provide the game, leaderboards, support and reconciliation	Generated
Purchase records	Store receipts and fulfilment records	Fulfil purchases, handle refunds and support	in_app_purchase
Device and usage signals	Signals the ads SDK receives to serve and measure ads	Show rewarded ads; prevent invalid traffic	google_mobile_ads

We do not collect your location, contacts, calendar, health data, or microphone input.

3. Third-party services (SDKs)

Google Mobile Ads (advertising) — https://policies.google.com/privacy
Sign in with Apple (authentication) — https://www.apple.com/legal/privacy/
in_app_purchase (billing, handled by the App Store / Google Play)
image_picker (reads the photo you choose; runs entirely on your device)

4. Advertising: we do not track you across apps

The App shows rewarded ads only — ads you choose to watch in exchange for an in-game reward. There are no banner or interstitial ads.

Every ad request we send is flagged non-personalized. Specifically:

iOS: we do not present the App Tracking Transparency prompt and we do not request the IDFA. Our bundled Privacy Manifest declares NSPrivacyTracking = false with an empty tracking-domains list.
Android: we explicitly remove the AD_ID permission from the app manifest, so the ads SDK cannot obtain a resettable advertising identifier.

In other words, we neither do nor are able to link your activity in this App with data from other companies' apps or websites. The ads SDK still receives basic device and usage signals (such as device model, coarse region, and whether an ad finished playing) to deliver, measure, and protect against invalid traffic.

If we ever move to personalized advertising, we will update this policy, obtain your consent on iOS as required, and update our store privacy declarations before enabling it.

5. User-generated content: what becomes public, and the permanent name on cards

Levels in this App are made by players. Before you upload, please understand:

Your photo becomes public. After human review it becomes a level that every player can see. Do not upload recognizable faces, license plates, addresses, identity documents, or anything you do not have the right to publish. (The comparison image and the answer coordinates are kept in non-public storage and are only accessible for the duration of a session.)
Your player name is printed into the card image, and cannot be changed afterwards. Cards awarded on completion carry your player name burned into the public card artwork. That image lives in other players' collections and may be shared — even if you later change your name or delete your account, cards already issued keep the name they were printed with. It is part of the record of who obtained which serial number, and when. Choosing your name is therefore a deliberate step in sign-up.
Levels and leaderboards display your player name. Levels you publish are credited to you.

All user-generated content is reviewed by a person before it goes live, and can be reported afterwards. Confirmed violations may result in the level being removed, cards being voided, or the account being suspended.

6. Retention, location, recipients

Retention: for as long as the purpose lasts, or as required by law.
Location: processed and stored on Cloudflare's global edge network, which may involve cross-border transfer; protected by encryption in transit and access controls.
Recipients: only us and the services listed in §3, for the purposes above. We do not sell your personal data and do not share it with data brokers.

7. Your rights

Under Taiwan's Personal Data Protection Act you may request access, a copy, correction, cessation of processing, or deletion. If you are in the EU/EEA you additionally have the GDPR rights of access, rectification, erasure, restriction, portability, objection, and complaint to a supervisory authority. If you are a California resident you have the CCPA/CPRA rights to know, delete, correct, and opt out of "sale or sharing" of personal information, without discrimination for exercising them.

To exercise any of these, email ka-cha.bouncing089@passinbox.com. If you do not provide sign-in information you cannot create an account or save progress.

8. Account and data deletion

You can delete your account in the App (Profile → Settings → Delete account) or request deletion at https://ka-cha.cc/account-deletion.

What actually happens:

Identifying fields are cleared immediately. Your player name becomes "deleted user"; the link to your Apple/Google identity and your date of birth are erased. Afterwards there is no path back from your Apple/Google account to that record.
Remaining fields are purged after 30 days. That window exists to handle refunds, chargebacks and minor-consent disputes, which often arrive after deletion.
The card issuance ledger and gem transaction log are kept, but no longer contain anything identifying you. They record which card was issued at what time for which win — the issuance history shared by every holder. Deleting a row would undermine the scarcity record of cards other players hold.
Cards already issued keep the name printed on them (see §5.2).
Transaction records required by law are deleted when the statutory retention period ends.

Deletion is irreversible. Signing in again with the same Apple/Google account creates a brand-new account; previous progress, cards and balances do not return.

9. Children

The App is rated 4+ (general audiences). We ask for a date of birth at sign-up to verify age, and we flag users below the local age of consent to the ads SDK via tagForUnderAgeOfConsent. We do not knowingly collect personal data from children under 13; if you believe we have, contact us and we will delete it promptly.

10. Security

We protect your data with encryption in transit (HTTPS/TLS), access controls, and least-privilege design. Level answers and comparison images are kept in non-public storage and served only through short-lived, session-scoped authorization. Back-office actions are role-gated and audit-logged.

11. Changes

We will post revisions on this page and update the "Last updated" date; significant changes will also be announced in the App.

12. Contact

ka-cha.bouncing089@passinbox.com

Generated with assistance from ShipReady based on an actual scan of the project, then corrected clause by clause against the App's real behaviour. Legal review is recommended before publication.