Security & privacy overview

Restora 360 never sees or stores raw card details. All card data flows directly to Stripe via Stripe Elements (client-side tokenisation), which is PCI DSS Level 1 certified. The only payment data Restora 360 keeps is the Stripe PaymentIntent id + last 4 digits + brand — for reconciliation only.

Every restaurant has its own data store. API routes enforce tenant scoping on every request — there is no way one restaurant can read another's orders, menus, or customer data. Verified via requireTenantAccess(tenantId) on every protected endpoint.

Every sensitive action is audit-logged: who logged in when, who changed pricing, who deleted what, who cancelled an order, etc. Logs are append-only and retained for 1 year (longer on Enterprise plans).

In transit — TLS 1.2+ everywhere; HSTS enforced. At rest — production data is encrypted by the underlying database (Stripe handles card data; we handle restaurant data via disk-level encryption at our hosting provider).

Every owner + super-admin account supports TOTP-based 2FA. Setup under Account → Two-factor authentication. Backup codes are generated on enrolment so you can't lock yourself out.