Back

Last updated: July 3, 2026

Privacy policy

Privacy model for browser-first database work.

S42 Turso Connect is designed so database credentials stay under your browser profile. This page describes the practical limits of that model and the storage choices available in the app.

No Stock42 credential collection
The app does not send Turso URLs or auth tokens to Stock42 application servers.
Session-first storage
New connections are kept only for the current browser session unless encrypted persistence is selected.
Encrypted local vault
Persistent connections are encrypted in the browser with Web Crypto and a passphrase you provide.
Direct Turso access
Queries and table data move between your browser and Turso. The service worker does not cache Turso responses.

What we do not collect

S42 Turso Connect does not include Google Analytics or other third-party analytics scripts. The app does not collect account profiles, database contents, query history, Turso tokens, cookies, or telemetry for Stock42.

Where credentials live

Session-only connections are stored in browser session storage and are cleared by the browser when the session ends. If you enable encrypted persistence, the encrypted vault is stored in local storage and can be unlocked only with the passphrase you provide.

What still depends on your environment

Browser extensions, shared machines, compromised devices, and weak passphrases can expose local browser data. Use private devices, revoke Turso tokens when needed, and prefer session-only mode on untrusted machines.

Service worker cache

The active service worker caches only same-origin static application assets under `/_next/static/` and `/icons/`. It does not cache navigation requests, Turso API responses, SQL results, or credential payloads.

Contact

For privacy questions, contact Stock42 through the official channels listed at stock42.com.