← Lienox
Privacy Policy — Lienox
Last updated: 2026-11-06
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. The one exception is Lienox Sync (§6), which is opt-in and stores only an end-to-end encrypted copy that we cannot read.
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. If you turn on Lienox Sync (§6), they are also included in the end-to-end encrypted copy, which we cannot read. 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 §10 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.
- Lienox Sync (only if you turn it on): an end-to-end encrypted copy of your configuration that we cannot read, plus a small set of metadata about it. Details in §6.
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.
If you use Lienox Sync, the encrypted copy is stored with Cloudflare R2 (Cloudflare, Inc.), which acts as our storage subprocessor. Cloudflare receives only the encrypted file and cannot read it either.
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. With Lienox Sync, the same seat decides which computer may save the cloud copy, so two computers never overwrite each other.
6. Lienox Sync (Ultra, opt-in)
If you turn on Lienox Sync, the app uploads a copy of your configuration so you can continue on another computer: agent memory, the skills and mods you created or edited, cron jobs, workflows, routing rules, pipelines, the project list (name, folder name and git remote URL — never the project files), agent definitions (never their conversations), project credentials, selected settings and tokens, your GitHub token and your BYOK provider keys.
- The copy is encrypted on your device (AES-256-GCM) with a recovery key that is generated on your computer and never sent to us. We store the encrypted file with our storage provider (Cloudflare R2) and cannot decrypt it. If you lose the recovery key, nobody — including us — can recover the copy.
- Alongside it we keep only metadata: its size, a checksum, a version number (generation), when it was saved, the app version, and the name of the computer that saved it (its hostname, which is also used as the label of the device that holds your seat, §5). Project folder names and git remote URLs travel inside the encrypted copy; we do not see them.
- Conversation history, project files, logs, telemetry, your licence and device identifiers are never included.
- We keep the current copy and the previous one. You can delete the cloud copy at any time (Settings → Sync), and it is deleted when you delete your account. If your subscription ends, the copy stays available for restore only for 30 days and is then deleted automatically. Your local data is never touched.
7. Security
We use reasonable measures to protect locally stored data, but you are responsible for the security of your device and accounts.
8. Your choices
- You can delete local data by removing the app's data directory.
- You can delete your Lienox Sync cloud copy from Settings → Sync, or turn Sync off on a computer.
- 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 §10 and we remove the entry.
9. Children
The Software is not directed to children under the age required by your jurisdiction (e.g. 13/16).
10. Contact
Privacy questions or requests: lienox.app@gmail.com.