Effective date and publisher
Effective date: 2 October 2026, when this policy is published. Meridian Echo is published by Black and Blue. Contact developer@blackandblue.co.in for privacy, support or deletion requests.
Game records on your device
Meridian Echo stores checkpoints, chapter and quest progress, story choices, optional-story progress, control bindings and display settings in app-private storage, with a recovery save backup. Recorded echoes contain virtual movement and interactions for puzzles; they are not microphone, camera or recordings of people. The game has no public player account or cloud-save feature.
Starting a new journey, clearing an echo or leaving chapter replay does not erase every preference, backup or SDK record. Android backup behavior can depend on the installed version and platform. We do not promise publisher recovery of lost progress or exclusion from every platform backup.
Optional usage statistics and technical reports
The game includes Firebase Analytics and Firebase Crashlytics. Game-owned reporting gates start paused. Saved positive choices do not automatically reopen those gates in a new process. Optional activation remains unavailable while consent eligibility for the release's intended audience and regions has not been established.
When enabled, app-authored usage events describe onboarding, chapter and quest actions, recordings, puzzle completion, purchase-screen views and restoration, with bounded chapter/step values. They do not contain dialogue text, story-choice text, a name or email address, precise location or a user ID assigned by the game. Firebase can also process app-instance or installation identifiers, automatic sessions and purchase events, approximate location derived from masked IP addresses, and device, operating-system and app information. The source disables Advertising ID collection and advertising-personalization signals.
Crashlytics can record stack traces, device/app details and technical state. Game-authored diagnostic messages use fixed failure codes, but uncaught or native crashes can include other technical context. Automatic crash-report upload is disabled after initialization. An opened report-management screen can initialize local capture even if future capture is off. Once initialized, local capture can continue until process death after a switch is turned off.
An available pending-report batch has separate Send, Delete and Not now choices. Send queues a provider request; Delete requests removal of the pending startup batch. Neither is a confirmed delivery or complete-erasure receipt, and a queued send cannot be recalled. A later empty availability check does not prove all earlier or current-session reports were deleted. SDK initialization, legacy settings and vendor services can have behavior beyond the game-owned event gates; turning off reporting is not a promise that no technical network activity occurs.
Purchases and access
Google Play and RevenueCat process purchase status, the available one-time unlock and a user-selected restoration. The configured game can refresh purchase status when the paywall opens, and on resume while a paywall or paid-chapter gameplay is active. These requests are independent of optional Firebase choices.
Providers can process purchase history, transaction and entitlement details, anonymous app-user identifiers, app/device metadata and operational request information. We do not ask for payment-card details. Access depends on the matching Meridian Echo product and entitlement; another app's purchase does not grant access. Store records and legal transaction history are separate from local progress.
Review access is a separate device-local grant. Its code is checked locally and is not sent by the game to purchase or telemetry services. Removing review access does not remove purchased ownership.
Retention and deletion
Android Clear storage or uninstall removes app-private game and SDK storage. This loses local progress; the publisher cannot recover it without an independently retained copy. Clearing local data does not erase platform backups, prior uploads, provider records or Google Play transactions.
At the recorded 1 October 2026 configuration check, this app's Analytics property used two-month event retention and fourteen-month user retention with reset on new activity. Activity can renew the identifier-associated user period; expired data is removed monthly. These settings do not apply to all aggregate reports. See Google retention.
Firebase describes a ninety-day Crashlytics retention period before removal from live and backup systems starts; that is not a guaranteed app-specific completion date. See Firebase privacy. We do not promise a fixed RevenueCat customer-retention period. Deleting a RevenueCat customer does not cancel a purchase or erase Google Play's transaction/legal records.
To request help with provider-held data, email developer@blackandblue.co.in with Meridian Echo and a short description. We may need enough information to locate the app-specific anonymous purchase record safely; an email alone may not identify it. Do not send passwords, tokens, reviewer codes, payment-card data or private save exports. We do not promise deletion of records we cannot match, legally required retention, or another application's records in a shared provider project. See deletion choices.
Providers and security
Our configured services are Google/Firebase, Google Play and RevenueCat. Their services use encrypted network transport. This does not promise encryption of every platform backup, support email, exported copy or app-private file. Processing can take place outside your country under the providers' applicable terms and safeguards.
This website has no tracking scripts, forms, remote fonts or advertising pixels. Its hosting provider may process request and security metadata. External links are subject to the destination's rules: Google privacy, Firebase privacy, RevenueCat privacy.
Intended audience and your choices
Meridian Echo's proposed Play audience is players aged sixteen and older. It is not directed to children under thirteen. The app does not verify age or provide parental consent; an age statement does not establish regional consent eligibility. Optional activation remains unavailable until that eligibility is reviewed. This policy does not claim that all minors are blocked from installation or that every region's requirements have been resolved.
Depending on where you live, rights to access, correct, delete, restrict processing or withdraw consent may apply, subject to proportionate verification and provider/legal limits. Contact the publisher using the address above. Changes to this policy will be reflected on this page with an updated date.