Local Storage & Cookies Policy
Last Updated: March 16, 2026
1. Introduction
This policy explains how the Thea mobile application (“Thea,” “the App”), published by Efebia Srl (“Efebia,” “we,” “us,” or “our”), uses local storage technologies on your device.
As a mobile application, Thea does not use traditional browser cookies. Instead, the App uses on-device storage technologies to maintain your session, preferences, and cached data.
2. Technologies Used
| Technology | Type | Description |
|---|---|---|
| MMKV | Encrypted key-value store | A high-performance, encrypted storage library used for securely storing user preferences and cached data on your device |
| AsyncStorage | Key-value store | A standard React Native storage mechanism used for authentication tokens and cached profile data |
| React Query | In-memory cache | A runtime data-fetching and caching layer that keeps recently accessed data in memory to reduce network requests. This data exists only in the app’s memory and is not persisted to disk |
3. What Is Stored
The following data may be stored locally on your device:
| Data | Storage | Purpose |
|---|---|---|
| Authentication token (JWT) | AsyncStorage | Keeps you signed in between app sessions |
| Cached user profile | AsyncStorage | Displays your profile without waiting for a network request |
| Theme/appearance preference | MMKV | Remembers your selected theme (light/dark) |
| Timezone cache | MMKV | Avoids repeated timezone lookups |
| Language preference | MMKV | Remembers your selected language |
| Recently fetched data | React Query (in-memory) | Reduces loading times and network usage |
4. Purpose
Local storage is used exclusively for the following purposes:
- Session persistence: Keeping you signed in so you don’t need to log in every time you open the App
- Performance: Caching frequently accessed data to reduce loading times and minimize network requests
- User preferences: Remembering your display and language settings for a consistent experience
We do not use local storage for tracking, advertising, or profiling.
5. Data Lifecycle
- On logout: Authentication tokens are cleared, and all in-memory cached data (React Query) is purged. Locally stored preferences are cleared.
- On account switching: All cached data from the previous account is cleared before loading the new account’s data.
- On app uninstall: All locally stored data (MMKV, AsyncStorage) is completely removed from your device by the operating system.
- No cross-app tracking: All local storage is sandboxed within the Thea app. No other app can access Thea’s stored data, and Thea cannot access other apps’ data.
6. Third-Party Local Storage
Thea does not include any third-party SDKs that store data locally for analytics, advertising, or tracking purposes. Specifically:
- No analytics SDKs (e.g., Google Analytics, Firebase Analytics, Mixpanel)
- No advertising SDKs (e.g., AdMob, Facebook Ads)
- No crash reporting SDKs (e.g., Crashlytics, Sentry)
- No attribution or tracking SDKs
7. Contact
If you have any questions about this policy, please contact us at info@efebia.com.