Legal
Security
How the platform protects your business’s data — and what it does not do yet. Everything on this page describes how the software works today.
Version 1 · in effect since Oct 21, 2026 · Version history
A database for every business
Each business gets its own database in each product application. Inside the applications, every query is additionally scoped to the business it belongs to and refuses to run without one.
Signed service calls
Every call between our platform and the product applications is signed with HMAC-SHA256 using a key pair specific to that product, includes a timestamp and a single-use nonce, and is rejected if it is late, replayed or altered.
Backups with checksums
Every business database and its files are backed up daily. When a cancelled customer’s data is deleted, a final backup is downloaded first and verified with a SHA-256 checksum; it is kept 30 days.
Audit logs
Every state-changing action of our administrators is recorded with who, when and from which IP address, and the applications log sensitive actions such as refunds, corrections and permission changes. Audit entries are kept 730 days.
Rate limiting
Sign-in, password reset, sign-up, demo and contact forms, staff PIN entry and public pages are rate limited to slow down guessing and abuse.
Secrets kept encrypted
Service keys, demo passwords and the payment and WhatsApp credentials that businesses enter are stored encrypted and are never shown again after they are saved. Customer portal sign-in links are single-use and stored only as a hash.
Server-side checks
Prices, taxes, totals, availability and permissions are always recomputed on the server; values sent by a browser are never trusted.
No card numbers on our servers
Online card payments are handled by Stripe. We do not store card numbers.
Roles and approvals
Our support staff have read-only access to our administration, apart from re-sending set-up invitations. Inside the applications, roles and permissions limit what each person can do, with manager approval for sensitive actions where the product supports it.
HTTPS on your own domain
A custom domain is only served after its DNS records prove it belongs to your business, and it gets an automatically issued HTTPS certificate.
Not available yet: two-factor authentication
Staff sign-in uses a password (and a PIN on shared tills and kiosks); two-factor authentication is not available yet. Use a strong, unique password for every staff account and remove people who leave. The customer portal uses single-use sign-in links sent by email instead of passwords.
Reporting a problem
If you believe you found a security issue, please tell us privately at contact@nextgenlb.io with enough detail to reproduce it, and do not access other businesses’ data. Read the privacy notice for how long data is kept.