Security
What is implemented in this version, stated plainly.
- Server-side authorization: organization and role come from a signed, HTTP-only session cookie — never from client input.
- Tenant isolation: every data operation is scoped to the signed-in organization on the server.
- Passwords are hashed with scrypt; login and signup are rate-limited.
- Input is validated server-side; output is escaped by the rendering framework.
- Security headers including a Content Security Policy, frame protection and HSTS.
- The AI receptionist only receives explicitly authorized business information.
This version stores data in memory for demonstration. Production-grade persistence (Postgres with row-level security) is designed but not yet connected. To report a vulnerability, use the contact form.