Cookie Policy
Last Updated: July 4, 2026 • DocNova Cookie-Free Standard Protocol
Primacy of Local Storage Over Tracking Cookies
To protect user privacy, DocNova utilizes an architectural model that requires **zero HTTP cookies**, zero analytical trackers, and zero marketing pixels. We do not transmit tracking identifiers to any servers.
1. What Are Cookies?
Standard internet cookies are tiny text files sent to your browser by a website server. They are stored on your device and are frequently transmitted back with each network packet to identify user sessions, track search history, compile marketing models, or persist logins across the cloud.
2. Our Cookie-Free Protocol
Because DocNova requires no user profiles, has no remote cloud databases, and operates completely serverless, we do not issue tracking cookies. There are no Google Analytics, advertising pixels, or analytics trackers embedded in DocNova. You can review your web browser developer console at any time to verify that zero cookie headers are present.
3. Essential Browser Storage Utilization
Rather than remote cookies, DocNova utilizes standard HTML5 local storage systems. These storage modules reside exclusively inside your browser sandbox and are never synchronized over the network.
| Storage Name | Retention | Functional Purpose | Security Profile |
|---|---|---|---|
| theme | Persistent | Saves your preferred user interface layout selection (Light Mode or Dark Mode). | 100% Client-Side Only |
| i18n_locale | Persistent | Retains your default workspace language selection (e.g. English, Spanish, Arabic) across browser sessions. | 100% Client-Side Only |
| sw.js (Service Worker Cache) | Persistent | Pre-caches site static assets (HTML, CSS, JS, WASM compilation modules) to guarantee immediate offline-first loading speed. | 100% Client-Side Only |
4. Managing Local Storage Settings
Because these parameters reside on your personal device, you hold absolute authority over them. You can wipe your theme choices, language selections, and cached WASM frameworks instantly using your browser's standard settings (e.g., "Clear Browsing Data" or "Delete site local storage"). Wiping local cache forces DocNova to fetch freshly compiled resources on your next connected load, but is fully safe.
5. Links to Third-Party Portals
Our open-source platform links out to external environments such as the GitHub codebase repository. These third-party sites are governed by their own telemetry, tracking, and cookie standards. We advise reviewing their respective privacy and cookie guidelines when visiting them.
6. Policy updates and Contact
Any modifications to our client-side storage policies will be immediately reflected on this page. If you have questions about our clean storage framework, sandbox scopes, or offline compilation, please read our Privacy Policy or contact our developer community directly at Contact & Support Page.