Plain facts about security.
A service that holds keys to your ERP and your shop owes you a clear account of what it does with them.
Accounts
Two-step verification (2FA)
Owners and admins need two-step verification with an authenticator app (TOTP) to add or delete connections.
Recovery codes
Ten single-use codes, shown once when you turn 2FA on. Each use notifies you by email.
Passwords
Stored only as Argon2id hashes, never as text.
Roles
Owner, Admin, Operator and Viewer. A Viewer can see but not change.
ERP and shop credentials
Envelope encryption
Every secret is encrypted with AES-256-GCM under a data key that belongs to your organization. That key is itself encrypted with a master key that is not kept in the database.
Never shown again
After saving, no key or password is shown in the app again. When you delete a connection, its keys are erased for good.
HTTPS only
ERP and shop addresses must use HTTPS with a valid certificate. Addresses on a local or private network are refused.
Your data
Per-organization isolation
Every row belongs to one organization and the database enforces the separation with row-level security, so a mistake in a query cannot show another customer's data.
EU hosting
The service is hosted on infrastructure inside the European Union.
The ERP stays the source
The service writes to the ERP only what the order flow defines: sales documents and, if you choose it, new customers.
Verified notifications
The shop's notifications of new orders are accepted only with a valid signature.
This website
No cookies, no tracking
The site is static files. It sets no cookies and loads no analytics or advertising tools, which is why you see no consent banner.
What we do not claim
We do not yet hold third-party certifications (such as ISO 27001) or publish availability figures, and we will not mention them before they exist. If you need something specific for your own review, ask us.
Reporting a vulnerability
If you found a security problem, write to us at info@jnssoftware.com.