Legal Center
Last Updated: October 9, 2026·Effective: October 9, 2026
PrivacyVerified Codebase Spec

Cookie & Storage Policy

Exhaustive accounting of all browser storage mechanisms, authentication tokens, and preference keys utilized by ENCLAVE.

1. Our Storage Philosophy

ENCLAVE strictly rejects behavioral advertising, third-party analytics scripts, and persistent tracking beacons. We utilize browser storage solely for strictly necessary functions—specifically maintaining your authenticated session and remembering your interface theme.

Storage Invariants
  • • No third-party tracking cookies or advertising networks.
  • • No cross-site fingerprinting or persistent device graphs.
  • • All stored client keys are accessible only on your local browser origin.

2. Cookies vs. Local Storage

Modern web applications can store state using HTTP cookies or browser Web Storage APIs (such as localStorage). ENCLAVE relies primarily on client-side Web Storage to ensure that sensitive tokens are never automatically attached to outbound HTTP requests across foreign domains.

3. Complete Audit of Browser Storage

Below is a complete, verified list of all storage keys created by the ENCLAVE client application:

Storage KeyTypeData ContainedRetention DurationPurpose
enclave_auth_userlocalStorageJSON object (id, email, displayName, role)Persistent until manual sign-out or deletionMaintains client authentication state and workspace identity.
enclave_active_sessionslocalStorageArray of active session descriptors (device type, timestamp)Persistent until revokedEmpowers user to view and revoke active device sessions in Security Center.
enclave_themelocalStorageString value: "light" | "dark" | "system"PersistentRemembers your visual interface appearance preference.
enclave_pwd_recordlocalStorageClient password record stringPersistent until account deletionValidates password updates in local client session manager.
enclave_pending_email_changelocalStorageTemporary verification token and new email addressExpires in 15 minutes or upon verificationFacilitates secure email change verification workflow.

4. Third-Party Trackers & Beacons

ENCLAVE loads zero third-party tracking scripts, including Google Analytics, Meta Pixels, Hotjar, or advertising tracking beacons. No tracking consent banners are required because no non-essential profiling cookies or trackers are deployed.

5. How to Manage & Clear Storage

You can inspect, manage, or delete all ENCLAVE storage at any time using:

In-App Self-Service Deletion

Navigate to Profile & Settings and click "Delete Account Permanently" to instantly wipe all local tokens and session keys.

Browser Developer Tools

Press F12 → Application / Storage tab → Local Storage → Click "Clear All".

6. Questions & Inquiries

If you have questions regarding our browser storage implementation, reach out to our privacy engineering desk:

Inquiries & Grievance Redressal

For formal data rights requests, security disclosures, or regulatory inquiries concerning this policy, submit a verified request through our official channels.

Related Legal & Privacy Documents