Legal
Privacy
Lingua treats your code and your filesystem as private. They stay on your device unless you choose to send them, and telemetry and crash reports are off until you opt in. The app makes a few requests of its own, to check for updates and to check a license. Both are described below.
What we never collect
- Your source code. Snippets stay on your machine. Execution history keeps run data in memory on your device, and it never leaves the device.
- Your filesystem. Project paths, file names, and directory listings are not transmitted to us.
- Your input. Keystrokes, clipboard contents, and command history are not logged.
- Personal identifiers. Telemetry carries no email, name, location, or device identifier.
What we collect (only if you opt in)
Telemetry is off by default. The first-run consent prompt explains what gets sent if you opt in:
- Event names from a fixed list — for example,
overlay.opened,runner.executed,feature.blocked. - The properties allowed for that event, such as a run's status or a SQL engine. They pass through a redaction layer and never include code, file paths, environment values, or license tokens.
- The Lingua version, the operating system, and the license tier.
- A random session ID that changes each time the app starts.
Events are sent to a self-hosted endpoint we control. There is no third-party analytics vendor in the desktop app. You can revoke consent any time from Settings → Privacy; revocation stops transmission immediately and any locally queued events are discarded.
Crash reporting
Crash reports are opt-in under the same consent flow, and off when no crash endpoint is configured. Lingua attaches no code, file paths, or project names to a report, but Electron includes a diagnostic minidump, and a minidump can contain data that was in memory at the crash.
Updates
The desktop app checks GitHub Releases shortly after launch and then hourly, downloads any update, and installs it when you quit. No setting turns this off. The web build asksupdates.linguacode.dev for the latest version at startup to show an update banner. Both exchange version information, not your project data.
License and device checks
Paid plans use signed license tokens that are verified on your device. Lingua may also check them against licenses.linguacode.dev for activation, status refresh, device limits, recovery, trials, and education access. That service keeps a device identifier and coarse device details, such as the operating system, to enforce limits and list your devices in Settings. Tokens travel in authorization headers, never in URLs.
Code you run
Code you run can reach the network. Settings → Privacy → Network from running code sets Allow, the default, Ask or Block for the Worker, Pyodide and Ruby WASM runtimes. It is a best-effort guard, not a sandbox. Node, Deno, Bun, Go, Rust and system Ruby are outside it. Hosts it blocks, and hosts you allow when asked, are listed in Recent activity on this device with only the runtime and the host.
Clipboard
Apply from clipboard on panel focus is off until you turn it on, and needs Pro. With it on, Utilities reads the clipboard when it opens and when the window regains focus, and works out on your device what kind of value it holds. Only the kind stays: the text is not stored, logged or sent, and nothing polls the clipboard in the background.
AI features
Explain error, Explain selection, Edit with AI, Ask AI in SQL and the cron phrase composer are off until you set a model in Settings. Lingua ships no remote endpoint or key, and sends nothing until you choose Send after seeing the exact payload. Secret-looking values are redacted first. The payload is what the feature needs: the error, the tab's code and its runtime values only if you include them, the selected code or the whole file, the file with the span to edit marked, or the cron phrase. SQL sends table and column names and types, never rows.
- Local sends only to
localhostor127.0.0.1, such as Ollama. Nothing leaves the device. - My endpoint sends to the provider you configure, under your account and its terms.
On desktop the key stays in the system keychain when one is available, otherwise in local storage. On the web it stays in the browser's local storage. Conversations are never saved, and telemetry never carries prompts, answers, endpoints or keys.
This website
linguacode.dev is a static site on Cloudflare Pages. We do not run a third-party analytics script. If we add Cloudflare's first-party Web Analytics, it runs without cookies and without sending data to any other vendor.
The web build
app.linguacode.dev uses the same renderer as the desktop app. Pyodide is served from the same origin as the app. The larger DuckDB and Ruby runtimes download from downloads.linguacode.dev when first needed.
The SQL engine
The SQL workspace runs DuckDB inside the app. Lingua ships the DuckDB extensions it uses (JSON, ICU and Parquet) and turns off DuckDB's download of the others fromextensions.duckdb.org, so typing or running a query does not contact that host. A query that needs another extension fails and names it. SQL still reaches any host it names itself, such as a URL passed to read_csv.
Instant SQL runs a sample of the statement under the cursor as you type, on Local and on your device. It never runs a write or a statement that names a remote URL on its own, and its rows are not saved. Settings → Editor → SQL workspace turns it off.
Database connections
A database connection goes from your device to the server you set up. Lingua runs no service in between. Turso, Neon and Cloudflare D1 go over HTTPS to those providers.
On desktop, passwords, tokens and key passphrases are encrypted with your system keychain, or stay in memory until you quit for a connection that asks each session, and always where no keychain is available. They are never written in plain text or logged, and the interface cannot read a saved one back. The list of saved connections has no secrets. It holds names, hosts, users and databases in a file only you can read on macOS and Linux. In the browser, Turso and Neon connections last for the tab and their tokens stay in memory.
Results and driver errors from a connection stay in the session and leave run capsules. A query on a connection reaches disk with its secret literals masked. Telemetry carries the engine and the step that failed, never a host, user, query or row. A crash report's minidump can hold what was in memory, such as a password in use or rows, which is one reason crash reports are opt-in.
For an SSH tunnel, Lingua reads ~/.ssh/known_hosts and ~/.ssh/configand does not write them. It opens a private key from ~/.ssh only when you pick it, your ssh config names it, or you save a connection imported with it. A saved connection keeps the key's path, not its content. Host keys you trust are kept in a file of Lingua's own, and with the SSH agent the agent holds the key.
Importing connections reads the file you pick, the file beside it that completes it, or the.env files at the open project's root, and drops every password. An export has no secrets.
Contact
Questions about privacy? Email hello@linguacode.dev. Source for the telemetry pipeline is in themain repository.