Kanzi

Delete your data

Kanzi, by Bencode Studio LLC, has no accounts — most of your data lives only on your device and is yours to delete directly. This page explains what exists, how to delete it, and what we keep.

1. Data on your device — delete it yourself

Puzzle progress, your album, beads, settings and gameplay history are stored only on your device. Kanzi → Settings → Reset app data immediately clears that gameplay state; we hold no cloud copy. The last OTA catalog and downloaded artwork use app and operating-system caches and may remain after an in-app reset. To clear all Kanzi app storage, use your device's app-storage controls or uninstall the app, subject to the platform's backup and restore behavior.

2. Diagnostics and analytics — request deletion

If Share diagnostics was on, crash reports and basic play events (with app/device identifiers, no name or contact details) were processed by Google Firebase. To request deletion, email privacy@bencodestudio.com from any address, with the subject “Delete my data”. Because Kanzi has no account and does not know your name or email, we may be unable to connect a general description of your device to a specific provider record. Include only the device platform, approximate dates and any installation or store identifier you already have and are comfortable sharing; do not send card details. We respond within 30 days and delete or request deletion of the records we can reasonably verify and associate with the request. Turning off Share diagnostics in Settings stops further Crashlytics collection and stops Kanzi's closed-list Analytics events when Google's consent state also permits Analytics.

3. What is kept, and for how long

Reward-verification records (a random challenge and transaction ID, never your identity) expire after 10 minutes and are removed within the following minute. The OTA and legal website host may retain ordinary security/request logs under its configured provider retention. Crash and analytics data not subject to a deletion request is retained under Google Firebase's configured/default retention periods and then deleted.

Full details are in the Privacy Policy.