Local data and sharing
MischiefSteps saves unlocked progress, challenge presets, best/retry counts, active runs, local pass-and-play results, assist/input/sound/haptic/display preferences, privacy choices and a last-verified Pro access cache on your device. A local recovery backup can restore an older save. Android or independently retained backup copies may be separate from current app storage.
Result cards are generated locally and shared only when you choose a recipient. Recipients can retain the image or challenge code. Local pass-and-play uses one device and is not network multiplayer. The game does not record people or impersonate their messages.
Optional reporting
Usage reporting and crash capture are separate choices. They are off by default, and declining them does not block core play. Optional reporting requires confirmation that you are at least 18. Saved positive choices remain paused after a cold start until you confirm them again in Settings; recovery requires a fresh choice.
If enabled, Google/Firebase Analytics may receive onboarding, level/core-action, hint and Pro purchase/restore events, with bounded world and game-mode values. The game does not put player names, seeds/challenge codes, level names, free text, location or identity-based user IDs in those event parameters. SDK services may process installation/app identifiers, automatic usage events, device/OS/app details and diagnostics. Analytics can derive approximate location from IP addresses separately from the game's parameters.
Opening pending-report management can initialize local Crashlytics capture. A handler that has already initialized can keep capturing until the app process stops, even after the local switch is off. Reports may include stack traces, technical app state and device details, including earlier sessions. Fixed game failure codes limit app-authored messages; uncaught/native exceptions can contain additional context.
Pending reports have separate Send, Delete and Not now choices. Send and Delete request SDK actions; they are not delivery or erasure receipts. Queued sends cannot be recalled. An empty availability check does not establish that every earlier or current report was deleted.
Turning reporting off or resetting Analytics does not erase earlier uploads. SDK startup and previously stored SDK state may affect network behavior; we do not promise a complete absence of network traffic when a switch is off.
Store purchases
Checking the Play price or restoring a purchase contacts Google Play and RevenueCat. The RevenueCat integration starts from those store actions rather than free play or onboarding. It may process anonymous app-user identifiers, purchase/restoration records, entitlement status, store/device metadata and operational request information. These store operations are separate from optional Firebase choices.
The game keeps a tagged last-verified Pro status locally for offline access. A cached status or failed network check does not establish current remote ownership. The app does not ask for a payment-card number. Removing local data does not erase provider history or Google Play transaction/legal records.
Retention and deletion
Android Clear storage or uninstall removes app-private saves, local recovery backup, generated private result-card files, preferences and SDK storage. You lose progress. Shared cards/codes, independently retained backups/files and provider records require separate management. There is no complete in-game erasure control.
Our Analytics property's recorded settings, checked on 1 October 2026, are event retention of 2 months, user retention of 14 months and reset on new activity enabled. These controls apply to identifier-associated event/user data, not most aggregate reports. New activity refreshes the user-identifier period; expired data is removed monthly. See Google retention.
Firebase documents Crashlytics traces and associated identifiers held for 90 days before removal from live and backup systems starts; this is not a confirmed app-specific deletion completion date. See Firebase privacy.
To request help with provider records, contact us using the details below. Anonymous billing records require safe app-specific identifier and alias matching before a deletion request can be handled. No fixed RevenueCat customer-retention period or automatic remote purge is promised. RevenueCat customer deletion does not cancel or erase Google Play transactions. See deletion choices.
Providers and security
Optional reporting uses Google/Firebase, and store operations use Google Play/RevenueCat. Providers may process information outside your country. App-private storage is not a universal encrypted-vault or security guarantee; take care with exported or shared copies.
This static site contains no scripts, forms, remote fonts, tracking pixels or site-set cookies. Hosting services may process network/security metadata. External links follow their providers' rules: Google privacy, Firebase privacy, RevenueCat privacy.
Audience, rights and contact
MischiefSteps is intended for teens and adults aged 13 and older and is not marketed to children under 13. If you are under 18, leave optional reporting off. The reporting eligibility confirmation does not age-lock the game or establish compliance with every country's minor-consent rules.
Publisher: Black and Blue. Contact developer@blackandblue.co.in with MischiefSteps and the minimum information needed for a support/privacy/deletion request. Do not send passwords, authentication tokens, payment-card details, reviewer codes or private documents/save exports. An email address alone does not identify an anonymous billing customer. Sending a request does not establish its receipt or completion.
Depending on where you live, access, correction, deletion, restriction or consent-withdrawal rights may apply, subject to proportionate verification and provider/legal limits. No fixed response deadline is promised. Material policy changes will be reflected here.