Security

Your data stays yours and separate

• Every restaurant gets its own database. A restaurant's files are stored under its own folder and the app refuses to serve a file that belongs to another restaurant.
• The owner decides which parts of the app each admin and manager can open. Pay information is limited to the owner and anyone the owner explicitly allows.

Accounts and sign-in

• Passwords are stored only as one-way hashes, with a 12-character minimum. Accounts lock for 15 minutes after repeated failed attempts, and sign-in and public endpoints are rate limited.
• Sessions use signed cookies (HttpOnly, Secure, SameSite) that expire after 12 hours.
• Passkey sign-in is supported. Password-reset links are single use and expire.
• Platform staff sign in separately from restaurant users.

In transit and at rest

• All traffic uses HTTPS with HSTS. Strict content-security, frame and content-type headers are set.
• Databases and file storage are provided by leading cloud providers that encrypt data at rest.

Chef Benny and AI

• The AI agent only acts for the person who asked, with that person's permissions. Changes to pay, taxes, alerts, job posts and similar records are shown as a card and only made when a person confirms.
• The agent cannot delete data, change sign-in or security settings, or reach other restaurants. Everything it writes passes a filter that keeps internal and technical text away from people.
• Chats with Chef Benny are deleted at sign-out and after one day at most. We do not train AI models on your data.

Monitoring and response

• Sensitive actions are written to an audit log. Server errors, failed jobs and files that could not be read are recorded as incidents, and a serious new incident alerts our team immediately.
• We keep dependencies up to date, run vulnerability checks, and review code for security before release.
• If an incident affects your data we will tell you without undue delay and follow the breach-notification terms in our Data Processing Addendum.

Compliance status

We are not yet certified under SOC 2 or ISO 27001. We build to the controls those frameworks describe and plan to pursue an independent audit. We will say so plainly here when that changes.

Report a vulnerability

If you find a security problem, email [email protected]. Please give us reasonable time to fix it before sharing it, do not access other people's data, and do not disrupt the service. We will not take legal action against good-faith research that follows these rules, and we will thank you.