Legal

Privacy Policy

Service: Core Breaker · Package: com.lemoncube.corebreaker
Effective: August 9, 2026 · Last updated: September 3, 2026 (amendment effective September 10, 2026)

Lemon Cube Studio (“we”) operates the mobile game Core Breaker (“the Game”). This policy explains what information is collected through the Game, how it is used, and how you can control it.

1. What we do not collect

The Game requires no registration and can be played as a guest, and signing in is an optional feature used only for cloud saves (Section 2). We do not collect any of the following:

• Name, date of birth, gender, address, or phone number
• Government-issued identifiers
• Contacts, photos, call logs, or text messages stored on your device
• Precise (GPS) location
• Payment credentials such as card numbers — payment is handled entirely by the app store and we never see your card details. To confirm that a purchase is genuine we do receive the purchase token and order number the store issues for that transaction (Section 3).

2. Accounts and where your game progress is stored

Your progress — currency, buildings, stage progression, and characters — is stored on your device by default. While you play as a guest (signed out), your game save stays on your device — it is never uploaded or backed up to our servers or to any third party, and every part of the Game is playable without signing in. The Game does still contact our own game server each time it launches, to fetch notices, maintenance status and live settings. That request carries a player ID generated on your device, along with your app version, platform and language; a limited set of in-game events is sent the same way. Section 3 lists exactly what is recorded and why.

Cloud save (optional)

Cloud save runs only if you sign in with a Google account yourself from the in-game settings. Its sole purpose is backing up and restoring your progress across devices, and no automatic sign-in is triggered anywhere in the Game. When you sign in, the following information is processed:

• Firebase Authentication (Google LLC): your account identifier (UID) and the email address and display name of your Google account — used to keep you signed in and to identify your backup; shown in the Game only as your account label.
• Cloud Firestore (Google LLC): your full game save, the unique identifier and model name of the device that uploaded the backup, the app version, and the time and size of the backup. The device identifier and model are recorded to prevent a backup made on another device from being overwritten by mistake, and are surfaced to you as a “backup from another device” notice.

Each account has a single backup document. Security rules allow only the account owner to write or delete it, and it can be read by the account owner and by our support operators, who may open a backup when they need to investigate a support enquiry or an incident. A backup is uploaded when you tap “Back up now” and, while signed in, automatically at most once every five minutes as the Game saves. Signing out stops automatic backup immediately and leaves the game data on your device untouched.

3. Information processed by our servers and by third-party services

Data processed on our own servers

The Game has its own backend, which we operate on Google Cloud (Firebase) infrastructure. Unlike the analytics and advertising services further below, we are the controller of this data. The following is sent whether or not you are signed in, because it identifies a save rather than a person:

• Player ID (a randomly generated code in the form CB-XXXX-XXXX, shown in the Game so you can quote it to support), app version, platform and language. Sent at launch to fetch notices, live settings and server time, and used as the key for everything else in this list.
• Service event log: a fixed list of events covering purchases, coupon redemptions, rewarded ads, progress milestones and in-game currency movements — with the values attached to each event. Only events on that list are sent; ordinary play telemetry is not. We use it to answer support enquiries such as “my purchase did not arrive”.
• Integrity signals: the offset between your device clock and our server clock, and counters indicating whether in-game currency totals or the save file appear to have been altered. These are used to review suspected abuse. They never block play and never trigger an automatic ban; a person reviews them, and the only measure we apply is exclusion from rankings, which can be reversed.
• Purchase verification records: the product ID, and the purchase token and order number issued by the app store, which we send to Google Play to confirm the purchase is genuine before granting the item. We never receive your card details (Section 1).
• Coupon redemptions: the coupon code and your player ID, so a coupon cannot be redeemed twice.

This data is not used for advertising or for building a profile about you, and it is not sold or shared for marketing. Turning analytics off (Section 4) stops the service event log and discards anything not yet sent. It does not switch off the rest, because we need those records to deliver purchases you have paid for and to run support — see Section 4 for what the toggle does control, and Section 5 for how long each item is kept.

Third-party services

The Game uses the third-party services listed below to operate, improve the service, and deliver advertising. Analytics and advertising data is collected automatically by those providers; we only view it in aggregated, non-identifying form. The cloud save described in Section 2 runs only while you are signed in, and we open a backup only where that is necessary, such as when answering a support enquiry or investigating an incident.

About the advertising identifier

The Game shows no forced interstitial advertising. Rewarded ads play only when you deliberately tap a button to watch one. Your advertising identifier is shared with ad providers only if you consent to personalized advertising; otherwise, non-personalized ads are served.

4. Consent and withdrawal

Analytics collection and personalized advertising can be turned on or off at any time under in-game Settings > Privacy Policy. Your choice is stored on the device and reapplied on subsequent launches. Until you choose, the defaults are analytics on and non-personalized ads; we ask once per device whether to allow personalized ads, after you watch your first rewarded ad.

• Reselect the options under Settings > Privacy Policy in the Game.
• Reset or delete your advertising ID under Android Settings > Privacy > Ads.
• For cloud save, signing out in the settings stops it immediately, and deleting your account removes the cloud backup together with the account (Section 5).
• Uninstall the Game, which deletes all stored consent records and game data on the device.

Withdrawing consent does not restrict normal play. Turning analytics off may limit our ability to diagnose errors, and withdrawing advertising consent may limit access to rewarded ads.

Turning analytics off also stops the in-game event log on our own game server described in Section 3, and discards anything not yet sent. The launch request itself — player ID, app version, platform, language and the integrity observations — still runs, because it is what delivers notices, maintenance status and support rewards and how we detect abuse. To have those server-side records deleted, send us the player ID shown in the in-game settings (Section 8).

5. Retention

• On-device game data: deleted when you uninstall the Game or clear its storage from your device's app settings.
• Cloud backup and account: kept while your account exists, with each new backup replacing the previous one. Choosing Delete account in the Game deletes the cloud backup document and the authentication account immediately; a deleted backup cannot be recovered.
• Service event log (Section 3): deleted automatically 90 days after it reaches our servers.
• Player ID record and integrity signals (Section 3): kept while we operate the Game, because they are what lets us answer a support enquiry about an account we otherwise cannot identify. Deleted on request (Section 8) and when the service closes.
• Purchase verification records (Section 3): kept for the period we are required to retain transaction records under applicable law, so that refunds and disputes can be handled.
• Firebase analytics data: retained for up to 14 months, then deleted automatically under Google’s retention policy.
• Crashlytics records: deleted automatically 90 days after the crash.
• In-game event log on our game server: deleted automatically 90 days after it is received.
• Player record on our game server (player ID, launch count, last-seen time, integrity observations): kept while the Game is operated, and deleted on request — send us the player ID shown in the in-game settings.
• Purchase verification records on our game server: kept while the Game is operated, so that the same purchase is never granted twice.
• Purchase records: retained by the app store operator for the period required by applicable law.

6. Sharing and international transfer

We do not sell your data and do not share it with third parties beyond the service providers listed in Section 3. Because those providers operate globally, data may be transferred to and processed outside your country, as follows.

See the Google Privacy Policy and the Unity Privacy Policy.

7. Children

The Game is not directed to children under 13 (or under 14 where Korean law applies), and we do not knowingly collect their personal information. If we learn that we have done so, we delete it without delay. Parents and guardians may contact us at the address below to request deletion.

8. Your rights

Depending on your jurisdiction, you may have the right to access, correct, delete, or restrict processing of your personal data. If you play as a guest, your game save never leaves your device, so most requests are fulfilled immediately by withdrawing consent and uninstalling the Game; the server-side records in Section 3 are keyed to the player ID shown in the in-game settings, and we delete them if you send us that ID. If you used cloud save, Delete account in the Game removes your cloud backup and account directly and immediately. For anything else, contact us and we will respond within 10 days.

9. Contact

• Lemon Cube Studio
• Email: contact@lemoncubestudio.com

10. Changes to this policy

We will post any changes on this page at least 7 days before they take effect, or 30 days in advance for changes that materially affect your rights, in which case the Game may ask you to consent again.

Revision history

• September 3, 2026 (effective September 10, 2026): discloses the data our own backend processes — player ID, the service event log, integrity signals, purchase verification records and coupon redemptions — and states that these are sent whether or not you are signed in. The service event log stops when you turn the analytics toggle off, while the launch request itself keeps running; the toggle's exact scope is described in Section 4. Also states that our support operators can read a cloud backup, and adds retention periods for the new items.
• August 26, 2026 (effective September 2, 2026): describes the optional cloud save (Google sign-in, backup and restore of progress) and account deletion, and corrects where the consent options live in the Game.
• August 9, 2026: first version.