Cookie and Local Storage Policy
Distinguishing storage needed for the service from measurement, advertising and privacy choices. This document covers SoulLocket on devices, the web and embedded content.
English translation of the same document version. Contact support if any wording is unclear or differs between languages.
1. Technologies used
The web may use cookies, localStorage, sessionStorage and IndexedDB. The app uses SharedPreferences, secure authentication storage, local databases and image/file caches. These are not all the same kind of cookie, but they may all store data on your device.
These policy pages do not embed advertising or Analytics code. The account deletion form sends data only when you submit it; the main app and other content pages have separate processing behavior.
2. Categories of stored data
| Category | Purpose and examples |
|---|---|
| Authentication and safety | Sign-in sessions, tokens, device status and legal choices help maintain and protect access. |
| Your settings | Language, appearance, tabs, lock or display configuration; these choices may be saved even when you select “Essential”. |
| Data and caches | Drafts, synchronization queues, downloaded images/files and local databases may contain private content; they are not automatically anonymous. |
| Diagnostics/measurement | Firebase Analytics and Crashlytics may process events, device information, errors and technical identifiers according to their integration. |
| Advertising and transactions | Ad consent status, advertising identifiers, interactions, purchase or reward verification tokens; not all advertising activity should be classified as essential storage. |
3. What “Essential” and “All” mean
In the new integration, “Essential” disables Analytics/Crashlytics collection and blocks ad initialization and loading through the app. “All” permits these optional SDKs; ads must still be allowed by Google UMP and follow operating system permissions. The app records the choice, time and document version on the device; legacy choices without a version require confirmation again.
Withdrawal blocks new requests and removes loaded ads in the app; it cannot recall data already sent or connections already in progress. Native SDKs may keep crash reports locally; the app requests deletion of unsent reports before enabling collection. Older app versions may not include these controls.
4. Relevant providers
Firebase/Google Sign-In, Facebook when used for sign-in, Google Mobile Ads/AdMob, payment platforms, map services and Cloudflare infrastructure may use tokens, caches or technical state for their features. Embedded content, fonts and external files may connect to providers when loaded.
Data categories, purposes and sharing scope are described in the Privacy Policy. Providers' policies do not replace SoulLocket's responsibility for its integrations.
5. Managing and withdrawing choices
- Open Settings → Privacy choices to switch between “Essential” and “All”. Choose “Essential” to withdraw permission for the optional SDK group without clearing app data. Ad privacy choices opens Google UMP choices where applicable.
- Manage location, camera, microphone, notification, health and advertising/tracking permissions in your operating system settings. Available controls vary by device.
- Use your browser's privacy settings to inspect/delete website data. Blocking essential data may end your sign-in session or disrupt features.
- Contact support about privacy rights when the interface lacks the needed action. Clearing app data must not be treated as the only way to withdraw consent.
6. Retention and effects of clearing data
Session data may expire at the end of a session; preferences and local databases may remain until you clear app/website data. Caches have their own lifetimes and may be downloaded again. Signing out does not guarantee removal of all caches, downloads or device backups.
Export or synchronize unsaved data before clearing storage. Uninstalling the app, deleting cookies or disabling permissions does not delete your account, server data or subscription. See the Account and Data Deletion Guide.
7. Updates and contact
This document needs corresponding updates when storage mechanisms, SDKs or choices change. Send questions to hotroviethoangdev.lo.ve@gmail.com, including the platform and app version; do not send passwords, PINs or one-time codes.