Security

Security at nlsys

What keeps your data yours: the isolation, integrity and supply-chain discipline the platform runs on — stated plainly, without marketing.

Tenant isolation

The product data platform — where your signals, results and receipts live — enforces isolation at the database layer with row-level security, not only in application code, and it is exercised in tests on every release. Requesting another tenant's resource returns 404: the API does not even confirm that the resource exists.

The account area — sign-in, balance, invoices — is a separate, smaller service. Its isolation is enforced in the application's queries and covered by tests; it holds your account record, never your signal data.

Integrity of operations

Every state-changing request to the product API 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.

The same rule covers money and metering: payment events are de-duplicated by their provider event id, and a repeated usage report with the same reference is recognised and never charged twice.

Supply chain

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.

Your account

Human authentication is handled by the NLSYS Auth0 tenant through the branded auth.nlsys.io domain. Auth0 owns password hashing, email verification, reset, brute-force protection and optional MFA. The cabinet keeps only an encrypted, HttpOnly, Secure, SameSite browser session and never stores a local password database. Machine access uses independently revocable platform API keys; raw secrets are shown once and the platform stores only their hash.

Data handling

The public CSV estimator reads file shape locally and does not upload signal values. Product files are sent only after sign-in and explicit job launch. Product data stays the customer’s property and is processed to provide the requested service. Details: Privacy Policy.

Operational discipline

On the product data platform, verified backups precede every schema migration, and database changes are applied append-only, in order, by a dedicated migration role. Rollouts are staged with health checks before public traffic.

Payments

Card payments are processed by Stripe, a certified PCI DSS Level 1 payment processor. Card details are entered on Stripe-hosted payment pages and never touch our servers; we receive only the payment confirmation. The site and the customer workspace are served over HTTPS (plain HTTP redirects to HTTPS).

Reporting

Found something? Write to nlsys.io@proton.me — reports are read by the people who can fix them.