SAVENTRA

Cookie Policy

Last updated: 13 July 2026

1. Our Cookie Stance

Saventra uses zero tracking cookies, zero analytics cookies, and zero advertising cookies. By architectural design — not by configuration.

2. What Are Cookies?

Cookies are small text files stored on your device by websites. They can be used for authentication, preferences, analytics, or advertising. Saventra's use is limited to the first two categories only.

3. Cookies We Use

Cookie Name	Provider	Purpose	Duration	Category
localStorage (wealth_v4)	Saventra (first-party)	Your encrypted financial vault — this is the AES-256-GCM encrypted blob containing all your financial data. This is NOT a cookie; it's browser storage that never leaves your device.	Until you delete it	Essential
localStorage (wealth_meta)	Saventra (first-party)	Encryption metadata — salt and password verification hash. Does NOT contain your password or key.	Until you delete it	Essential
localStorage (wealth_audit)	Saventra (first-party)	WORM audit log — tamper-evident security log of vault operations.	Until you delete it	Essential
sessionStorage	Saventra (first-party)	Rate-limiting state for brute-force protection on vault unlock. Cleared when you close the tab.	Session	Essential
localStorage (theme, sidebar, etc.)	Saventra (first-party)	UI preferences — theme choice (light/dark), sidebar collapsed state, language selection.	Until you clear browser data	Essential
Google Fonts CSS	fonts.googleapis.com	Font delivery for the Inter and Playfair Display typefaces. Google may log the request for font licensing compliance. No cookies are set by Google Fonts.	N/A (no cookies)	Essential

4. Cookies We Do NOT Use

We explicitly confirm the absence of:

• Google Analytics (no _ga, _gid, _gat cookies)
• Facebook Pixel (no _fbp cookie)
• Any advertising or retargeting cookies
• Any third-party tracking scripts
• Session cookies for authentication (there is no server-side session)
• Hotjar, Mixpanel, Amplitude, or any analytics service
• Intercom, Crisp, or any customer chat widget

5. Why localStorage Instead of Cookies?

Saventra stores your encrypted financial data in localStorage — not cookies — because:

• Cookies are transmitted to servers with every HTTP request. Saventra never needs your data in a cookie — authentication uses a Bearer token sent only to our API, and your workspace lives in local storage (and, with an account, in an encrypted cloud backup).
• localStorage data stays on your device and is never sent anywhere unless you explicitly export it.
• localStorage can hold larger amounts of data than cookies (5-10 MB vs 4 KB).

Your encrypted vault in localStorage is functionally equivalent to a file on your hard drive — it does not leave your device.

6. Managing Your Data

You are in complete control:

• Clear vault data: Use the "Reset all data" button in the app sidebar, or clear your browser's localStorage for saventra.app.
• Export first: Always export an encrypted backup (.wbk file) before clearing data.
• Browser-level control: Your browser's settings allow you to clear localStorage and sessionStorage for individual sites.
• Private browsing: Saventra works in private/incognito mode. In this mode, all data is cleared when you close the window — this is actually a feature if you want a temporary session.

7. Google Fonts

We use Google Fonts to serve the Inter and Playfair Display typefaces. This is the only external resource loaded by Saventra. According to Google's documentation, Google Fonts does not set cookies and the Fonts API is designed to minimize data collection. The request to fonts.googleapis.com includes only the font names and your browser's user agent (needed to serve the correct font format). No personal data is transmitted.

8. Changes to This Policy

If we ever add any cookie-based functionality (which we do not plan to do), we will update this policy and notify users. Given our architecture, the most likely change is the removal of Google Fonts in favor of self-hosted fonts — further reducing external dependencies.

Back to Saventra