How we protect your data

Tenant isolation

iFoodlab is a multi-tenant platform: every customer (tenant) has its own isolated data. A request is scoped to the signed-in user's tenant, and database-level access rules enforce that boundary so one tenant can never read or write another tenant's records. New systems and modules are built to the same isolation rules before they are switched on.

Encryption in transit and at rest

All traffic to and from the platform is encrypted in transit over HTTPS/TLS. Data is encrypted at rest in the database and in file storage. Uploaded files are served through short-lived, access-scoped links rather than public URLs.

Backups

The production database is backed up automatically on a regular schedule and supports point-in-time recovery, so data can be restored after an error or incident. Backups are held with the same encryption and access controls as live data.

Independent penetration testing

The platform is tested by an independent penetration test, and findings are tracked to resolution. Our most recent security assessment is complete and its findings have been remediated and verified.

Security checks on every release

Security is part of how we ship, not a one-off. Automated security checks run in our build pipeline as a gate on every release, and access rules are verified as part of that process so a change cannot quietly weaken isolation or exposure.

How AI features handle your data

AI features are optional and always keep a person in control:

• Your data is never used to train AI models.
• Only the record in question is sent for a given request — not your whole account.
• Every AI action is written to your own audit log.
• A person reviews and approves before anything the AI drafts becomes a record. The AI advises; it never signs.
• You can turn AI features off.

AI processing is carried out under a commercial agreement with our AI provider that excludes using your data for model training and sets a limited retention period. See the Data Processing Agreement for the sub-processors we use.

Access and accounts

Access to the platform is per named user, with role-based permissions inside each tenant and an inactivity timeout on sessions. We follow least-privilege access internally and keep administrative access to production restricted and logged.

Reporting a concern

If you believe you have found a security issue, please contact us so we can investigate promptly. We will acknowledge your report and keep you informed of the outcome.