Security
What keeps your data yours: the isolation, integrity and supply-chain discipline the platform runs on — stated plainly, without marketing.
Every stream, result and receipt belongs to exactly one account. Isolation is enforced at the database layer with row-level security — not only in application code — and is exercised in tests on every release. Requesting another tenant's resource returns 404: the API does not even confirm that the resource exists.
Every state-changing request carries an idempotency key. Retries return the original result instead of double-applying; the same key with a different body is rejected as a conflict. Long-running operations are durable: they survive restarts and recover unambiguously rather than guessing.
Production images are built from an accepted source archive, scanned, signed, and deployed pinned to an exact digest — not a mutable tag. What runs in production is byte-identified.
Files submitted to the no-signup demo are processed in memory to produce the result and are not stored. Product data on your account is processed on our own servers solely to provide the service, stays your property, and is deleted on request. Details and your rights: Privacy Policy.
Verified backups precede every schema migration; database changes are applied append-only, in order, by a dedicated role. Rollouts are staged with health checks before public traffic.
Found something? Write to nlsys.io@proton.me — reports are read by the people who can fix them.