Local data and sharing
Loopgarden is published by Black and Blue. The free endless puzzle journey does not require an account, a purchase or optional reporting. This policy covers the Android app com.blackandblue.loopgarden and this privacy, support and deletion website.
The game stores progress, completed-stage counts, unfinished boards and paths, daily results, challenge-code drafts, a garden notebook, cosmetic/display choices and privacy preferences on your device. A local recovery backup may restore older saved progress. These saves are not a cloud account or a public player profile. Local reviewer-access status may also be stored when review access is used.
“Copy this code” places a puzzle challenge code on your device clipboard. It does not export your complete save. A code identifies a puzzle; it does not include your notebook, privacy choices or personal profile. Copies you choose to send can remain with recipients. Clearing a drawn path resets that path, not your entire saved journey.
Optional reporting
Usage statistics and new game-authored crash logging start off each app session. They require a separate choice in Settings and the “I am 18 or older” self-confirmation. Play remains available with both controls off. Adult self-confirmation does not verify age or establish parental consent or regional legal eligibility. Players aged 13–17 can use the free game with optional reporting off.
When you enable “Share usage statistics”, Google Analytics for Firebase is used to understand and improve gameplay. App-authored events describe onboarding, core actions, level starts/completions, hints, Pro views and restoration, with a bounded difficulty tier and journey/daily/challenge mode. These event parameters do not contain notebook entries, challenge codes, puzzle seeds, names or identity-based user IDs. Analytics also processes app interactions, app-instance identifiers and technical device/app information, and can derive approximate location from network/IP information. App-authored payload limits do not remove those SDK operations. See Google Analytics data and privacy.
“Enable local crash reports” enables fixed game-error codes and local Firebase Crashlytics capture for diagnosing faults. Crash reports can include stack traces, app/device/OS details, Crashlytics and Firebase installation identifiers, and native crash information. A crash handler that has already started may continue local capture until the app process ends, even after the switch is turned off.
“Manage pending crash reports” may start local crash capture and check for a pending batch, including reports from earlier sessions when sharing was off. Choose “Send pending reports”, “Delete pending reports” or “Not now”. Sending is a separate optional action. The app does not show the reports’ contents, dates or count. Send and Delete request SDK operations; the screen does not confirm delivery or complete deletion. Reports already queued to send cannot be recalled. An empty result means no pending reports were found at that check; a later crash can create more.
The game configuration turns automatic crash sharing off and applies disable controls when the service initializes. Older installations may have persisted earlier SDK settings. Startup may initialize Analytics to revoke and reset an earlier positive choice. Turning a control off stops new game-owned reporting calls; it does not erase data already processed by a provider or prove the absence of every SDK network operation. The game contains no ads, and its Analytics configuration denies advertising storage, advertising user data and personalization.
Store purchases
Selecting “Explore Pro extras” or “Retry store” initializes the configured RevenueCat store client, checks customer status and requests the loopgarden_default offering. This can involve network requests and anonymous app-user/store information before you buy. “Restore purchase” uses the initialized client. Pro access is checked against the app-specific loopgarden_pro entitlement and product. Free progression remains available independently of store availability or reporting choices.
Google Play and RevenueCat process purchase/restoration history, entitlement state, anonymous app-user identifiers and operational app/store/device information to provide and evaluate purchase access. The app does not ask for a payment-card number or send contact attributes to RevenueCat. A displayed price, cached access state or failed store check is not a completed purchase or restoration. Removing local data does not erase provider purchase history or Google Play transaction/legal records. See RevenueCat’s purchase-data guidance.
Retention and deletion
Local saves and recovery backups remain in app storage until removed or overwritten. The game has no complete in-game save-erasure control. Use Android Settings → Apps → Loopgarden → Storage → Clear storage to remove app-private progress, backups, preferences and SDK storage. Android menu names vary. Uninstalling can also remove local app data; manage any Android/platform backup or previously shared copy separately. The game does not provide a full-save export or publisher-operated cloud recovery service.
At the documented 1 October 2026 configuration check, identifier-associated Analytics event retention was 2 months and user retention was 14 months, with reset on new activity enabled. New activity can extend the user-identifier period. Expired data is removed in Google’s monthly process; these settings do not limit most aggregate reports. See Google Analytics retention.
Firebase states that Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal from live and backup systems. This is not a promised completion date for an individual request. See Firebase privacy and retention. No fixed RevenueCat customer-retention period or automatic remote purge is promised here. RevenueCat customer deletion and Google Play transaction history are separate. See deletion choices.
Providers, website and security
Optional reporting uses Google/Firebase. Store features use Google Play and RevenueCat. These services can process information outside your country under their applicable arrangements. Their processing is separate from local game saves. Provider information is available in Google’s privacy policy, Firebase’s privacy information and RevenueCat’s privacy information.
This website uses local fonts and contains no scripts, forms, tracking pixels or site-set cookies. Its hosting service can process network/security request information. Opening an external link uses that provider’s website rules. App-private storage is not a general encrypted-vault guarantee; take care with copies you share.
Audience, rights and contact
Loopgarden is intended for ages 13 and older. The adult-only reporting choices described above are separate from access to the free game. The app does not verify age or obtain parental/regional consent through its self-confirmation control. Do not enable optional reporting if you cannot meet the applicable eligibility requirements.
Contact Black and Blue at developer@blackandblue.co.in for support or a privacy, access, correction or deletion request. Include Loopgarden and only the minimum information needed to explain the request. Do not send passwords, authentication tokens, payment-card details, reviewer codes or private save exports. Anonymous provider records need safe app-specific matching; an email address alone does not identify an anonymous billing customer.
Rights can vary by location and may be subject to proportionate verification and provider/legal limits. No automatic backend deletion, completed-request receipt or fixed response deadline is promised. This policy is effective 4 October 2026. Material changes will be reflected by an updated effective date on this page.