Security

Encryption

All traffic between your browser and Neucelle is encrypted in transit with TLS. Stored data — including invoice images and extracted line items — is encrypted at rest by our database and object-storage provider (Supabase).

Per-account isolation

Every row of data is scoped to a single restaurant account and enforced at the database layer with Postgres row-level security (RLS). A signed-in user can only read or write data belonging to the account(s) they are a member of — there is no shared, cross-tenant view of invoices, recipes or costs.

Access control

• Authentication is handled by a dedicated identity provider (Clerk); we never store raw passwords.
• Internal access to production data is limited to the people who need it to operate the service, and is used only to support, debug or maintain the platform — never to browse your data.
• Connected POS and accounting integrations use scoped OAuth grants (read-only where possible) that you can revoke at any time.

Where your invoices live

Invoice files and extracted data are stored in our object storage and database in [TODO: confirm hosting region — e.g. EU (Frankfurt)]. Optical character recognition is performed by our OCR subprocessor (Mindee). The full list of subprocessors and where they operate is in the Privacy notice.

Backups and availability

The database is backed up by our infrastructure provider so data can be restored after a failure. The application runs on managed, auto-scaling infrastructure.

Reporting a vulnerability

If you believe you have found a security issue, please email [TODO: security@neucelle.ch] with the details. We welcome responsible disclosure and will acknowledge your report.

Security is a moving target; this page describes the controls in place as of the date above and will be updated as they evolve.