Cookie & Local Storage Notice
Effective 2026-07-28 · Version 1.0This notice explains what Lonzo stores on your device and why. It is deliberately short, because we store very little: we use only storage that is strictly necessary to sign you in and run the app, plus a small amount of storage for your preferences. We do not use advertising cookies, and we do not embed third-party analytics or tracking software.
This notice applies to the Lonzo web app and our native mobile app(s). It is a standalone notice and is also linked from our Privacy Policy.
Cookies, local storage, and IndexedDB — the plain version. A cookie is a small piece of text a website stores in your browser and sends back to the server on each visit, while local storage and IndexedDB are browser databases that keep data on your device and are not automatically sent to any server. Lonzo relies mainly on IndexedDB and local storage — data that stays on your device to sign you in and remember your preferences — rather than on tracking cookies.
1. What we store, and why
This is the complete set of what Lonzo stores on your device. The key names below begin with tλnk: — an internal system prefix from our underlying platform, not a separate service or a third party; they are listed exactly as they appear on your device so you can find and verify them yourself:
| Key | Where | Category | Purpose | Retention / Expiry |
|---|---|---|---|---|
tλnk:auth:credentials | Browser localStorage (web); secure app storage (mobile) | Strictly necessary | Your session/auth credential — keeps you signed in without re-entering credentials each time. | Cleared on logout; the session expires after 30 days of inactivity. |
tλnk:shell:keys | Browser IndexedDB (web); secure app storage (mobile) | Strictly necessary | Your device identity keypair. The private key is non-extractable — generated on your device, it cannot be read out or exported, and never leaves the device. This is security storage, not tracking. | Persists until account deletion or until you clear site/app data. |
tλnk:shell:session_urn | Browser sessionStorage | Strictly necessary | The identifier of your current session. | Cleared on tab close. |
tλnk:reload:attempts | Browser sessionStorage | Strictly necessary | A transient guard that prevents a reload loop if the app fails to load. | Transient; cleared on tab close. |
Vista del Lago Software LLC sets no server cookies. All of the storage above is client-side (localStorage, IndexedDB, and sessionStorage); none of it is a cookie sent to our servers on each request, and none of it is used for tracking.
We do not store more than we need to run the Service for you.
Third-party functional requests. To render the interface, the web app loads a small number of assets from third-party content-delivery networks: Google Fonts (fonts.googleapis.com / fonts.gstatic.com, for the Inter font) and the jsDelivr CDN (for KaTeX, highlight.js, and Mermaid). When your browser requests these assets, the provider necessarily receives your IP address to serve the file. These providers set no cookies we control and perform no tracking through these requests — they are functional asset requests, not trackers. We intend to self-host the Inter font and vendor these libraries to eliminate the third-party calls; until then, we disclose them here.
2. Essential vs. non-essential
Every key we store is strictly necessary — the auth credential, the device identity keypair, the current session identifier, and the transient reload-loop guard (see the Section 1 table). These are required for login, security, and running the app, and they cannot be turned off without breaking sign-in and the Service.
We have no functional/preference, advertising, analytics, or performance-tracking storage, because we use none.
3. What we do NOT do
To be explicit:
- No advertising cookies, pixels, or ad SDKs.
- No third-party analytics or tracking software embedded in the web or mobile app.
- No cross-site or cross-app tracking, and no building of advertising profiles.
- No "sale" or "share" of personal information through cookies or similar technologies, as those terms are used under US state privacy laws (e.g., CCPA/CPRA).
The only third-party network requests we make are the functional CDN asset requests disclosed in Section 1 (Google Fonts and jsDelivr). Those requests expose your IP address to the provider so it can serve the asset, but they set no cookies we control and perform no tracking — they are not analytics or advertising technology. Our "no third-party analytics or tracking" statement remains true; we disclose the functional CDN requests alongside it for completeness.
Because we do not sell or share personal information and do not track you, the opt-out-of-sale/share mechanisms that heavier services carry are not applicable to us.
As of this notice, the web and mobile builds set no CAPTCHA / bot-protection cookies (reCAPTCHA, hCaptcha, Turnstile, or similar), no CDN / WAF / edge-provider tracking cookies, and no crash-reporting or diagnostics SDK that attaches device identifiers (Sentry, Crashlytics, or similar). The only third-party requests are the functional CDN asset requests disclosed in Section 1, which set no cookies we control.
These statements are re-verified against the browser and mobile builds on every release. If any such tool is ever added for a non-essential purpose — including first-party analytics or crash reporting that uses device identifiers for anything beyond strictly-necessary security and reliability — we will update this notice and add consent controls before it ships (see Section 6).
4. Do we need a consent banner?
Because we use only strictly-necessary storage and no advertising or tracking technology, EU/UK ePrivacy rules do not require a blocking consent banner — this informational notice is sufficient. We have deliberately chosen not to deploy consent-management infrastructure we do not need.
This conclusion holds only while our storage remains strictly necessary. If any non-essential technology (analytics, advertising, or crash reporting keyed to device identifiers) is later introduced, a consent banner becomes required in the EU and UK, and we will re-review this notice and its classifications before that technology ships.
5. How to control local storage
You can clear this storage at any time:
- Web: clear your browser's site data / IndexedDB for Lonzo, or use your browser's privacy controls. Doing so removes the local keypair and logs you out — you can simply sign in again to generate a fresh key.
- Mobile: clearing the app's data through your device's operating-system settings has the same effect and will log you out.
Clearing storage does not delete your account or your data on our servers; it only removes what is stored on your device.
Per-browser controls. Every major browser lets you view, block, and delete cookies and site data from its settings. For step-by-step instructions, see your browser's own help pages — for example, Google Chrome, Apple Safari, Mozilla Firefox, and Microsoft Edge each publish a "clear cookies and site data" / "manage cookies" help article in their respective support centers.
6. Do Not Track and Global Privacy Control
Because we do not track you across sites or apps and do not sell or share personal information, there is nothing for a Do Not Track (DNT) or Global Privacy Control (GPC) signal to opt out of. We honor such signals to the extent applicable law requires, but they do not change our behavior — which is already tracking-free.
7. Changes to this notice
We may update this notice from time to time. The version and date at the top will change, and we will flag material changes. If we ever introduce a new non-essential technology, we will update this notice and put appropriate consent controls in place first.
8. Contact
Questions about this notice: privacy@lonzo.ai · Vista del Lago Software LLC