The anim8 application uses client-side storage mechanisms, including browser cookies and HTML5 Local Storage, to manage session authentication, app configuration, and locally configured API integrations.
While traditional cookies are occasionally exchanged for secure HTTP routing, the anim8 desktop, web, and mobile environments (delivered via Capacitor wrappers) primarily utilize HTML5 Local Storage. This technology provides enhanced client-side performance, lower network overhead, and secure on-device containment of user configurations.
These keys are strictly required to operate the basic functions of the social media simulation. Disabling local storage will prevent authentication, reset local configurations, and wipe unsaved sandbox progress.
| Registry Key | Operational Objective | Lifespan |
|---|---|---|
| anim8_token | Holds the secure JSON Web Token (JWT) identifying your authenticated session. | Persistent (Until Logout) |
| current_universe | References the active universe identifier you are currently executing. | Persistent |
| theme | Stores your structural theme preference (dark or light mode). | Persistent |
| anim8_ai_language | Determines the translation target language passed to the synthesis pipeline. | Persistent |
| anim8_ai_provider | Maintains your chosen active generation pipeline (Gemini, Groq, or OpenRouter). | Persistent |
| anim8_ai_model | Flags the specific model variation targeted within your selected pipeline. | Persistent |
If you configure private API credentials locally to bypass system-wide execution limits, your keys are stored inside local storage under keys such as anim8_gemini_key, anim8_groq_key, and anim8_openrouter_key. This data remains on your physical hardware unless you explicitly select the options to synchronize your configuration to our cloud databases, in which case it is encrypted using AES-256-CBC prior to dispatch.
We do not embed third-party advertising cookies or behavioral profiling brokers. Subscription tokens, Google Play Store, and Apple App Store in-app transaction states are processed locally on-device through safe platform integrations, such as the RevenueCat Capacitor plugin, which may manage distinct operational values locally.
You can clear all stored parameters at any time by executing a "Log Out" within the main menu or by wiping your browser cache or mobile app storage settings. This will immediately destroy all local authentication tokens, active keys, and session parameters.
For deep technical questions regarding our on-device storage design, contact our engineering team at [email protected].