Privacy Policy — Lienox

Last updated: 2026-09-23

1. Local-first by design

Lienox runs on your machine. Your projects, files, conversations, agent definitions, and API keys are stored locally (local database and config), not on our servers.

2. What is processed and where

Prompts & context you send to an agent are transmitted to the LLM provider you choose, using your API key (BYOK). That processing is governed by the provider's privacy policy. We do not receive or store that content on our servers.
API keys you enter are stored locally on your device and used only to call the provider you selected. Do not share your configuration files.
Browser control / computer use: when you ask an agent to drive your browser or run commands, it operates within your local session. Any data it reads is processed locally and/or sent to your chosen provider per your instructions.

3. What we collect

Account data (only if you create a cloud account for licensing/billing): your email and a bcrypt-hashed password. We never store your password in plain text. Billing is processed by Stripe; we do not store card numbers.
Diagnostics/telemetry: we collect anonymous product events (installs, updates, app open/close, feature usage, error and crash reports, and agent-execution metadata such as duration, model identifier, token counts, and success/failure status) associated with a random device identifier, plus basic technical metadata: app version, operating system and CPU architecture, install package type, system language, a per-launch random session identifier, the machine's total and available memory (in rounded gigabytes, sent only with error and crash reports), and a coarse country code derived from the request IP at ingest time (the IP address itself is not stored). Telemetry never includes prompt content, file contents, conversations, or API keys.
Install-link requests (website, opt-in only): if you ask us to email you the install link from a phone, we use your address to send that one email and then discard it — unless you tick the consent box, in which case we store your email address, the language you requested it in, the campaign parameters present in the URL you arrived from (`utm_*`, `ttclid`), and the time you gave consent, so we can email you about Lienox. We do not store your IP address, and this list is never sold or shared. Ask us at the address in §9 and we delete your entry.
Linking diagnostics to your account: telemetry is sent without your account, and we do not store your account alongside it. However, if you create a cloud account and activate a licence, that machine's device identifier is registered against your account so the licence can be bound to it (see §5). That means we can — and, in our internal admin tools, do — associate a device's diagnostics with the account that registered it, in order to provide support, see whether a plan limit is affecting a real customer, and detect licence abuse. The association is made only when we look, never written back into the event records, and it disappears if the device is deactivated or the account deleted. If you never create a cloud account, your diagnostics stay unlinked.

We do not sell your data.

4. Third‑party providers

Using BYOK means your content is processed by the LLM provider you configure (e.g. Anthropic) using your own API key. That processing is governed by the provider's privacy policy — review it before sending sensitive data.

5. Device activation (paid plans)

Paid plans are licensed to one machine at a time. To enforce that, the app sends a device identifier — a hash derived from your machine id, never your name, serial number, or hardware details — when it requests or renews a licence. We store it next to your account, along with a coarse label (operating system) and the time of the last renewal, so you can see which machine holds your seat and move it. Removing the device (or deleting the account) removes that record.

6. Security

We use reasonable measures to protect locally stored data, but you are responsible for the security of your device and accounts.

7. Your choices

You can delete local data by removing the app's data directory.
You can revoke provider access by removing your API keys.
If you gave consent to keep your email after requesting an install link, you can ask us to delete it at any time — write to the address in §9 and we remove the entry.

8. Children

The Software is not directed to children under the age required by your jurisdiction (e.g. 13/16).

9. Contact

Privacy questions or requests: lienox.app@gmail.com.