← Echo Crawler

Data & Account Deletion

Last updated: May 26, 2026

Echo Crawler stores game data locally on your device and, if you opt into cloud save, on Firebase servers managed by wmkc. Additional data is collected by third-party services (Firebase Analytics, Crashlytics, AdMob). This page explains how to delete your data from each location.

Delete Local Game Data

All game progress, settings, currencies, equipment, and purchase history stored on your device can be deleted by:

This permanently removes all locally stored game data. wmkc cannot recover this data once deleted.

In-App Data Deletion

To delete local game data without uninstalling the app, uninstall and reinstall the app, or clear app data via your device settings (see above). There is no separate in-app button for local data deletion.

Delete Cloud Save Data

If you signed in with Google and used cloud save, your game data is stored in Firebase Cloud Firestore and your account is managed by Firebase Authentication. To delete this data:

In-App (Recommended)

  1. Open Echo Crawler
  2. Go to Settings → Cloud Save
  3. Tap Delete Cloud Data
  4. Confirm deletion

This deletes your Firestore cloud save data and your push notification token from Firebase servers. Your Firebase Authentication session will be signed out. This action is permanent and cannot be undone.

Note: This does not delete your Firebase Authentication account record. To request full account deletion (including the auth record), contact privacy@wmkc.net with your Player ID.

Via Email

If you cannot access the game, contact privacy@wmkc.net with your Player ID. Please send the request from the email address associated with your account so we can verify your identity. We will delete your account and associated data within 30 days.

Analytics & Crash Data

Firebase Analytics only collects data when you have granted consent. You can withdraw consent at any time via the analytics toggle in Settings → Privacy, which immediately stops all analytics collection.

Firebase Crashlytics is also disabled if you decline the first-launch consent prompt. You can independently re-enable or disable crash reporting at any time via the crash reporting toggle in Settings → Privacy. When you sign out, your user ID is cleared from future crash reports.

Previously collected analytics data is automatically purged after 14 months, and crash data after 90 days. This data is aggregated and cannot be deleted on a per-user basis.

Delete Ad-Related Data

Google AdMob may have collected ad interaction data (impressions, clicks, device advertising ID). To manage this:

Android

  1. Open Settings → Google → Ads
  2. Tap Reset advertising ID or Delete advertising ID
  3. Toggle off Opt out of Ads Personalization

iOS

  1. Open Settings → Privacy & Security → Tracking
  2. Disable Allow Apps to Request to Track
  3. Open Settings → Privacy & Security → Apple Advertising
  4. Disable Personalized Ads

For more information, see Google's Privacy Policy and Apple's Privacy Policy.

Delete Purchase History

In-app purchase records are managed by Google Play or the Apple App Store. wmkc does not store payment information. To view or manage your purchase history:

Refund requests should be directed to the respective platform:

Push Notifications

Firebase Cloud Messaging stores a device token to deliver push notifications. To stop receiving notifications and delete the token:

Disabling notifications causes the device token to become inactive. Inactive tokens are automatically cleaned up by Firebase.

Future Features

When additional online features such as leaderboards are added in the future, this page will be updated with instructions for deleting any additional data. Currently, all server-side data is limited to Firebase Authentication, Firestore (cloud save), Analytics, Crashlytics, and Cloud Messaging as described above.

Contact Us

If you have questions about data deletion or believe we hold data about you that is not covered above:

We aim to respond within 30 days and will process deletion requests for any data stored on Firebase servers within that timeframe.