Privacy Policy
This policy explains how KeiConsulting (the "Operator") handles information in the iPhone game "Scoop and Serve" (the "App"). The Japanese version prevails if the two versions differ.
1. Information kept on the device
Game progress, coin balances and their breakdown, purchase records (transaction ID, product, price, date), settings, the age band and the year and month of birth are kept in the save data on the device. The year and month of birth and the age band are never sent to the Operator.
When iCloud is on, the save data (including the age band and the year and month of birth) is backed up automatically to the user's iCloud (key-value storage) and restored after a device change or reinstall. Apple manages that data; the Operator cannot see it.
2. Information sent to the Operator's server
Apart from what the game itself needs, the App sends the following to the Operator's server. It contains nothing that identifies a person by itself, such as a name, email address or phone number. The "install ID" is a random value the App creates at its first launch, keeps on the device and also attaches to in-app purchases (the App Store's "appAccountToken"). With it, the Operator links what arrives from the same installation, and the purchase and refund notifications from Apple, to each other. See the External Transmission Policy for when each is sent.
(1) Coin balance report (once a day, and after a purchase or refund)
- Install ID (a random value the App creates at its first launch; also attached to purchases)
- App environment (the App Store, testing such as TestFlight and App Review, or development)
- Unspent paid coins, valued in yen
- The same amount, counting unclaimed Daily Coin Pass coins as paid
- Number of paid coins
- Number of free coins
- Breakdown by App Store country/region (code, yen value, paid coins)
- App version
Purpose: to manage and report the unspent balance of paid coins under the Japanese Payment Services Act. Nothing is stored for users who never had paid coins.
(2) Daily summary (e.g. when the App is closed; a newer copy of the same day replaces the older one)
- Install ID (a random value the App creates at its first launch; also attached to purchases)
- App environment (the App Store, testing such as TestFlight and App Review, or development)
- The (game) day summarized
- First day played
- App version
- App Store country/region code
- Number of sessions
- Play time (seconds)
- Highest level cleared
- Per level: attempts, wins, fail reasons (out of drops / overflow), quits, continues and the coins spent on them, boosters used
- Whether the official daily challenge was played, and practice runs
- Coins earned and spent that day
- Products bought and how many
Purpose: statistics to tune level difficulty, find bugs and improve the service. It never contains the age band, the year and month of birth or the parental-consent answer.
(3) The App Store label
The App Store "App Privacy" section shows the information above and in section 3 as follows. What is linked through the install ID or the app instance ID is declared as "Data Linked to You"; the crash reports sent to Firebase Crashlytics are linked to no one and are declared as "Data Not Linked to You". Nothing is used for tracking (combining it with other companies' data or for advertising).
| Data type | What it is in the App | Purposes | Linked to the user | Tracking |
|---|---|---|---|---|
| Device ID | The install ID (a random value the App creates at its first launch, also attached to purchases) and the Google Analytics app instance ID (a random value Firebase creates) | App Functionality, Analytics | Yes | No |
| Purchase History | Coin balance reports, the purchases in daily summaries, purchase and refund notifications from the App Store, and the purchase records sent to Google Analytics (product and price) | App Functionality, Analytics | Yes | No |
| Product Interaction | Daily summaries (sessions, play time, attempts and results per level and the like) and the in-app activity sent to Google Analytics (launches, screens, level starts and results, shop and purchase steps and the like) | Analytics | Yes | No |
| Coarse Location | The approximate region (about a country or city) Google Analytics derives from the connection's IP address (the device's Location Services are never used) | Analytics | Yes | No |
| Crash Data | The report sent to Firebase Crashlytics when the App closes unexpectedly (where the program was running, the error and the time) | App Functionality | No | No |
| Other Diagnostic Data | The device and app state attached to a crash report (model, OS and app versions, free memory and storage, orientation and the like) | App Functionality | No | No |
3. Information sent to Google (Firebase)
The App uses two Firebase services by Google LLC. Neither receives anything that identifies a person by itself, such as a name or email address, nor the install ID, age band, year and month of birth or parental-consent answer. Nothing is sent to either from devices whose user answered under 13. Outside Japan the App asks first and sends only if you allow it (section 8).
(1) Google Analytics for Firebase
To analyze statistically how the game is played and improve it, the App sends Google the following.
- In-app activity: launches, screens, level starts and results (level number, play time, customers served and the like), shop and purchase steps, purchase records (product and price) and other events the App records
- The app instance ID: a random value Firebase creates for each installation of the App
- Device and app information: device model, OS version, language, app version and the like
- The IP address that comes with the connection: Google derives an approximate region (about a country or city) from it
The advertising identifier (IDFA) and IDFV are not used, and the data is never used for advertising or for tracking with other companies' data.
(2) Firebase Crashlytics
When the App closes unexpectedly (crashes), it sends Google the following so that the cause can be found and fixed. The record stays on the device and is sent at the App's next launch.
- The crash record: where the program was running (stack trace), the error and the time
- Device and app state: device model, OS and app versions, free memory and storage, orientation and the like
- The Crashlytics installation UUID and the Firebase installation ID: random values created for each installation of the App (to count how many devices a problem affects)
- The in-app activity just before the crash (what (1) sends to Google Analytics)
- The IP address that comes with the connection
Google handles both under the Google Privacy Policy. The App Store "App Privacy" label is the table in section 2 (3).
4. Information received from Apple
When an in-app purchase is made or refunded, Apple sends a notification (App Store Server Notifications) to the Operator's server. It contains the transaction ID, product, price and currency, country or region, purchase date, refund date and reason, and the install ID the App attached to the purchase. Purpose: managing paid coins under the Payment Services Act, handling refunds and preventing fraud.
App Store purchases, iCloud and Game Center (leaderboard scores and nickname) are handled by Apple under Apple's privacy policy.
5. Information received in support requests
The email address and message of a support request are used only to answer and handle that request.
6. Service providers and third parties
- The server and database run on services of Cloudflare, Inc. (United States). Data may be stored in data centers outside Japan.
- Google Analytics for Firebase by Google LLC (United States) analyzes how the game is played (section 3). The data is processed and stored outside Japan.
- Firebase Crashlytics by Google LLC (United States) collects reports of the App closing unexpectedly (section 3). The data is processed and stored outside Japan.
- Except where the law requires it, the information is not provided to third parties. It is never sold.
7. Retention
- Daily summaries: 180 days.
- Coin balance records: while paid coins remain, and 400 days after the balance reaches zero; after the end of service, until the legal obligations are fulfilled. Records from test environments (such as TestFlight): 90 days after the last report.
- Purchase and refund notifications from Apple: 7 years (accounting and Payment Services Act records).
- Google Analytics data: event-level data for 14 months; data tied to an installation for 14 months after the App was last used (aggregated reports as Google Analytics keeps them).
- Firebase Crashlytics crash reports: 90 days.
8. Your choices
- iCloud backup can be turned off in the iPhone's settings (coins then cannot be restored on a new device).
- To ask for disclosure or deletion of what was sent to the server, contact us with the Install ID shown under Settings → Support in the App. Daily summaries are deleted; coin balance records may have to be kept for their retention period because of the Payment Services Act.
- Sending to Google Analytics and Firebase Crashlytics can be turned off at any time in the App under Settings → Privacy (one switch turns off both). Outside Japan the App asks first and sends only if you allow it. Crash records from while sending was off are deleted, never sent.
- What is sent to Google Analytics and Firebase Crashlytics carries no install ID or anything else the Operator could use to tell users apart, so the Operator cannot pick out or delete one user's part of it.
9. Children
The App asks for the year and month of birth at the first purchase. The age band and the year and month of birth are kept only in the save data (on the device and, when iCloud is on, in the user's iCloud backup) and are never sent to the Operator. No information is specially collected from children under 13. Nothing is sent to Google Analytics or Firebase Crashlytics from devices whose user answered under 13.
10. Security
All communication is encrypted (HTTPS). The server stores only the information in section 2 and keeps no IP addresses or similar connection logs. Only the Operator can access the server.
11. Changes
Changes to this policy are announced in the App or on this page.
12. Contact
KeiConsulting — contact form
Effective date: October 15, 2026