Security foundation

Built to protect real restaurant operations.

OrderKo is designed so small restaurants can accept QR and kiosk orders without exposing staff tools, credentials, or operational data to customers.

If credentials are exposed, rotate staff PINs, super-admin secrets, email credentials, and image-upload keys immediately, then review audit logs for unusual activity.

Restaurant-scoped data

Menus, orders, staff credentials, and operational controls are tied to a restaurant record so each business stays separated.

Protected staff areas

Cashier, kitchen, admin, and super-admin screens use server-side session checks instead of being public dashboards.

Hashed staff PINs

Staff PINs are stored as hashes, not readable values, and new PINs must avoid common weak patterns.

Login throttling

Staff and super-admin login attempts are rate limited to reduce brute-force guessing risk.

Safer order submission

Customer order creation is validated, duplicate submissions are blocked, and submission bursts are rate limited.

Production health checks

Public health checks confirm service status without exposing database connection details in production responses.

Operational audit logs

Important restaurant, menu, order, upload, lead, and subscription actions are recorded so operators can investigate what changed.

Browser security headers

The app sends practical headers to reduce framing, content-sniffing, referrer, and browser permission risk.

Security roadmap

OrderKo already has a practical MVP security foundation. These are the next upgrades planned as more restaurants join and operational risk increases.

Owner accounts with stronger identity controls
Two-factor authentication for operators
External uptime/error monitoring
Formal incident response and security review process

If credentials are exposed

Treat leaked secrets, staff PINs, or upload credentials as an operational incident. Rotate first, then review logs and confirm restaurant workflows still behave normally.

Rotate exposed staff PINs, super-admin secrets, email credentials, and Cloudinary keys immediately.
Check Super Admin audit logs for unusual restaurant, menu, order, upload, or lead activity.
Run npm audit before pilot launch and document any accepted dependency risk.
Contact hello.orderko@gmail.com for security concerns or suspected account misuse.