1. Scope and operator
This policy covers the app, this website and support inquiries. Our operator details and contact information appear on this page. External services also have their own policies.
2. Records on your device
You can play without an account. Cards and their copy counts, seals, Brew shards, decks, achievements, pending rewards, settings and local backup copies are stored on your device. Battles and journeys in progress are not saved. Deleting cloud records or your cloud account does not remotely erase records stored only on your device.
Card-back and battle-background choices are also stored on your device. If a previously selected paid outfit remains on the device, the app rechecks its entitlement at startup using the currently linked account before applying it. A saved choice alone does not prove purchased access or initiate a new account-linking or purchase action.
3. Optional sign-in and backups
You may link a Google account. Apple is available only in supported builds where that option appears. Firebase Authentication processes account identifiers, email addresses, authentication and connection information, and provider-supplied profiles such as display names and photo URLs. The app does not use profile photos for its own features.
After linking, follow the prompts to choose the records to continue with; automatic backup then starts. Changes to cards and their copy counts, seals, Brew shards, decks and achievements are saved in Firestore, with failed uploads retried. You can disable automatic progress backups or save manually. Backups include some settings, a random device identifier, timestamps, revisions and integrity information. Records from different devices are not automatically combined; restoring requires your choice.
In supported builds, cloud saves, reads and deletion requests go through our server, which checks account authentication and Firebase App Check information. To prevent abuse, we use Apple App Attest on iOS and Google Play Integrity on Android, sending information about app or device authenticity to Apple or Google. This protects cloud features and is separate from optional usage analytics. App Check does not itself verify age or parental approval.
Cloud features require verification using a supported device and an officially distributed app build. Cloud saving and restoration may be unavailable if these checks cannot be completed. They are unavailable on iOS 15. Cloud records from TestFlight builds are stored separately from regular distribution builds and cannot be transferred between those environments. If in-app deletion is unavailable, you can still request deletion through the contact listed on this page.
4. In-app purchases and restoration
If you buy or restore optional cosmetics, Apple or Google processes the store payment. We do not receive your credit-card number or bank-account details. We use the product, purchase/refund/revocation status, verification times, store transaction identifiers and purchase-verification information, and their association with your app account to verify purchases, provide cosmetics, restore access after a device change, reflect refunds and revocations, and prevent improper grants and duplicate processing.
Verification uses Google services including Firebase and sends necessary purchase-verification information to Apple or Google servers. We retain transaction locators or purchase tokens needed for ongoing verification in encrypted form on our server. Account associations use the app account identifier, randomly generated purchase-linking identifiers, and pseudonymized information derived from the Google or Apple provider identity used to sign in and from store transaction information. This information is not anonymous.
Purchase protection also checks account authentication, app/device authenticity, and applicable revocations of app-use approval. Supported Android versions process Play Integrity evidence bound to the operation and authentication information through Google and our server. We may process the identifier needed to check revocation and whether providing that identifier is required. These processes protect purchases and restoration separately from optional analytics. We do not independently request your date of birth or identity documents.
5. Optional usage analytics
App analytics is off by default. With permission on each device, Google Analytics receives screens, tutorial progress, battle, achievement and collection results, seal changes, action outcomes, and app/device information to improve usability and understand usage.
We do not attach names, emails, custom deck names or save files, or link the authentication user ID to analytics. SDK installation identifiers mean reports are not completely anonymous. We do not use advertising IDs, serve ads or personalize advertising. You can stop analytics in settings.
Google Analytics uses IP addresses from network requests to estimate the country, region or city for usage analysis. The app does not obtain precise location from GPS or similar sensors.
Only if you allow analytics do we send events about cosmetic previews, purchase actions, pending approval, server-verified purchases, restoration and cosmetic selection to Google Analytics. These events contain the product identifier, cosmetic type and categorized operation result. We do not attach purchase-verification information, purchase tokens, transaction identifiers or authentication user IDs to these analytics events.
6. Diagnostics and notices
Diagnostics has separate, optional consent and is off by default. If enabled, Firebase Crashlytics processes error categories, code locations, app/OS/device information and installation identifiers for troubleshooting. App-reported Dart exception messages are replaced by categories; we do not add names, emails or saved-game files. Not all OS/SDK diagnostic information can be removed.
If you enable both analytics and crash reporting, recent analytics events (including screen views), with their event names and associated parameters, may be included in diagnostic reports to investigate the issue. We do not attach your saved-game files to diagnostic reports.
Choosing to fetch notices contacts Firebase Remote Config, where Google processes installation identifiers and related information. We do not use it to change battle rules, rewards or draws.
7. Website and support
Website analytics follow one site-wide policy. In the EEA, UK, Switzerland and Brazil, Google Analytics page-view and click measurement stays off until you allow it. In Japan and the United States it runs unless declined. Where the region is unknown or has not been assessed, it stays off unless allowed. Your choice applies to every page and can be changed or withdrawn in Analytics settings at the end of the page. Grants are stored in localStorage for up to 180 days; refusals remain until changed. Google, our Firebase App Hosting provider, processes ordinary connection information to deliver and secure the site.
Analytics uses cookies and measurement identifiers. Declining or withdrawing stops new reporting and removes analytics cookies that this website can delete. Previously processed data is not automatically erased. See the website privacy policy for details.
Support uses your reply address, message and optional attachments to respond, investigate, verify identity and address rights requests. Do not send passwords, authentication codes, save files or unnecessary information.
8. Providers and overseas processing
We use Google services for sign-in, backups, purchase verification and restoration, refund handling, analytics, diagnostics, notices, abuse prevention, processing related to revocation of app-use approval, and web hosting. We also use Apple services for iOS app-download and device checks, payment and purchase verification, and refund or app-use approval revocation notifications. Providers may process information outside Japan, including in the United States. Japanese storage locations do not mean all processing stays in Japan. We review provider policies and terms and handle information under applicable law.
We do not sell information or disclose it without a lawful basis, such as service-provider processing, consent or legal requirements. We use protections including encrypted connections and access controls.
We do not retain authentication tokens, App Check tokens, signed Apple app-download data, raw verification identifiers, purchase-verification information, purchase tokens or save-file contents in our own operational logs. Information needed for processing is sent to servers or external services and may be received and processed temporarily by the cloud platform. Cloud-platform and external-service logs may retain metadata needed for communications and troubleshooting, such as IP addresses, request times and HTTP results. Limiting retention in our own logs does not mean that no communication information is transmitted, processed or retained.
9. Retention and deletion
Local records remain until you clear app data, delete the app or otherwise remove them. Manage OS backups separately. Cloud game records remain until individual or account deletion. Google states that removal of Firebase Authentication data from its systems and backups may take up to 180 days after deletion is requested.
Google Play purchase and refund notifications may be retained in Google’s notification delivery infrastructure for up to seven days for delivery and retry. This is separate from the 180-day retention of records used to prevent duplicate processing after receipt.
We retain the deleted account identifier and deletion status to prevent delayed uploads from restoring deleted records. This deletion marker contains no saved-game content and currently has no automatic expiry. You may contact us about the need to retain it.
Processing-history records for Apple revocation notifications (including pseudonymous identifiers) are scheduled for automatic deletion 90 days after receipt. Deletion is performed asynchronously by Firestore after that deadline, so records do not disappear immediately at expiry. The pseudonymous identifier associated with the revocation and its revocation status instead have a retention-review deadline 90 days after first receipt and are not automatically deleted. Repeat notifications do not extend this review deadline. We review the purpose and necessity of retention, and how deletion would affect handling of the revocation, before deciding on retention or deletion under applicable law. Contact our published support address about retention or deletion.
GA user/event retention follows the service settings; aggregate statistics have different conditions. Under Google's policy, Crashlytics crash stack traces and associated identifiers are retained for 90 days before deletion begins. Support records are deleted when no longer needed for the inquiry, disputes or legal obligations. Stopping collection or deleting an account does not erase every report already sent.
Links between a cloud account and a pseudonymized store identifier used for cloud backups are scheduled for automatic deletion 90 days after the last applicable cloud operation. Firestore deletes them asynchronously after expiry, rather than immediately. Account deletion removes the account’s saved records in both regular and TestFlight environments and its cloud-backup linking records. Deleting a link does not clear a separately maintained revocation status.
To prevent storage abuse and excessive operations in a short period, we retain minimal information needed to enforce usage limits, such as operation times, counts and upload amounts linked to the account identifier. This contains no save-file contents. After account deletion, we retain it until its scheduled expiry to prevent abusive retries and similar activity. Expiry is set two days after the last operation counted toward usage limits. Counting another operation, such as a deletion retry, updates that expiry. Firestore deletes the information asynchronously after expiry, so actual removal may take additional time.
Purchase records are managed separately from cloud game backups. To verify and restore valid purchased access and prevent improper grants after a refund or revocation, we retain account-to-purchase associations, pseudonymized transaction and sign-in provider identifiers, the product, entitlement/refund/revocation state and verification times. These purchase-related records remain after account deletion and currently have no automatic expiry. You may contact our published support address about retention or deletion. We will explain the records we can identify, the purpose and necessity of retention, and the available action considering restoration and fraud prevention.
Encrypted identifiers used to keep verifying a valid one-time purchase are retained while needed to verify and maintain that access; account deletion alone does not erase them. When we confirm that access has been revoked, for example following a refund, they become subject to removal through reconciliation. Records used to recheck an unsettled payment are assigned an expiry 32 days after we record a purchase verification result showing that the payment is unsettled; that expiry is removed when the purchase is confirmed active. The 32-day period is not a deadline for payment or the purchased entitlement itself.
Purchase/refund notification deduplication records are assigned expiry 180 days after their creation. Small purchase-rate and verification replay-control records expire two days after the last update. Temporary purchase-start records expire after ten minutes, and request-idempotency records after 24 hours from creation or update. Further relevant operations may update an expiry. These are scheduled-expiry times, not guarantees of immediate deletion; Firestore may take additional time to erase an expired record.
10. Your information rights
Contact us to request information about purposes, access, correction, deletion, restriction or withdrawal of consent as provided by applicable law. We verify identity as necessary and respond under that law. Where available, you may also contact or complain to the competent supervisory authority.
Because analytics and diagnostics are not linked to authentication user IDs, we may be unable to identify particular reports. We will explain limitations and available action. See the account deletion page for instructions.
11. Age checks and minors
KAMOSUBI is intended for people aged 13 or older. Minors must obtain parental or guardian approval and consent where applicable law requires them. If you cannot legally consent to optional reporting yourself, leave it disabled and consult your guardian.
In mobile versions supporting age checks, the app first checks applicability and sharing status using the supported operating system or app store at startup. When checks are required or age information is shared through the platform, age bands and parental app-use approval status are used to evaluate access on the device. An authoritative response that checks are not required does not trigger an independently forced age-sharing request. The app does not independently request a date of birth or identity documents. Age bands and their sources are not sent to our server or analytics, or retained in stored records or our own logs. The access decision and identifiers needed to check revocation status for cloud and purchase features are held temporarily in memory while the app is running. Processing by the operating system or store follows its provider’s policies.
Access is restricted on the device when the operating system or store indicates that a user is under 13. In regions requiring verification, or when an API response is unknown or fails, an error is not treated as verification that the user is an adult. Follow the screen instructions to retry or check store settings. If the operating system or store confirms that checks are not required, optional age sharing is declined outside regions requiring verification, or an older system does not support the API, platform restrictions and our Terms of Use apply; age is not treated as verified. Restrictions after a parent revokes app-use approval are enforced through the operating system or store. Revocation alone does not automatically delete records stored with us. See the account-deletion instructions if you want those records deleted.
Separately, our server receives notifications from Apple when parental approval to use the app is revoked. These include the app-download transaction identifier (AppTransaction ID), a notification identifier, and the signed timestamp of the revocation notice. After verifying the signature and target app, we pseudonymize identifiers using keyed HMAC and store records in Firestore to handle duplicate or out-of-order notifications and assess the response needed. These pseudonymous identifiers are not anonymous information. Our server temporarily receives the notification for verification, but our application does not retain the raw notification, original identifiers, age or date of birth in stored records or operational logs. Cloud-platform access logs may retain HTTP metadata, such as the time of a request.
When you use cloud or purchase features on iOS, the app sends signed Apple app-download information and a device-verification identifier to our server to check the signature, target app, environment and device correspondence. We handle the originals and raw identifiers only in memory during verification, then pseudonymize the app-download transaction identifier with keyed HMAC and link it to the Firebase account identifier. On Android, the verification installation identifier obtained from Play Age Signals, and whether providing it is required, are sent to our server to respond to revocation of app-use approval. Supported builds use Play Integrity to check binding to the operation and authentication information, then pseudonymize and link the identifier. These records are not anonymous. App Check and Play Integrity do not themselves verify an age band on our server.
When a verified Apple notification or Google Play revocation list confirms withdrawal of app-use approval, supported cloud and purchase features restrict access. Cloud features check the applicable store identifier. Purchase features also check past revocation subjects linked to the purchase account to prevent improper grants. Revocation alone does not automatically delete saved records. Signing in again, presenting newer app-download information or reaching 90 days does not clear a revocation. Automatic restoration after renewed approval is not currently supported. Contact our published support address about deletion or access restrictions.
Contact us if you believe a child’s information was sent without required consent. We will investigate and take appropriate action under applicable law, including deletion where required.
12. Changes
We update the effective date when this policy changes. We will announce material changes affecting purposes or rights in advance on this website and, if you have enabled in-app notices, in the app. We will obtain fresh consent where legally required.
