Security and data
Your supplier records, kept apart and kept honest
What Foodhelm does to protect your data, what it does not do yet, and who else touches it.
Where it runs
- Microsoft Azure, Canada Central region. The application, its database (Azure Database for PostgreSQL) and the documents you file are stored there, encrypted at rest by Azure.
- HTTPS only, with HTTP Strict Transport Security; a strict Content-Security-Policy on every page, which allows no scripts or requests to any other site.
- Today Foodhelm shares Azure infrastructure with the system it grew out of at Stephano Group, as separate applications and separate databases. It moves to Azure resources of its own before the first outside plant's data is loaded.
How companies are kept apart
- A database schema per company. Each company's lines, suppliers, documents, requests and logs live in a schema of their own. Every query runs inside the asking person's company schema, or not at all; there is no shared table for a filter to get wrong.
- A least-privilege database login. The application signs in to its own database only.
- The assistant answers only from the asking person's company records, through the same company-scoped reads. It reads and changes nothing, and text inside a supplier's document is treated as data, never as an instruction.
Who can do what
- Roles: owner, admin, member, read-only. Only the people you invite can see your workspace.
- Sign-in: a password (at least 10 characters, stored as a scrypt hash), or your Microsoft or Google account. Attempts are rate-limited, and an account locks for a while after ten wrong tries. Sessions are HttpOnly cookies.
- Two-step verification for password sign-in: a six-digit code from an authenticator app (Microsoft Authenticator, Google Authenticator, 1Password and the like), with ten one-time recovery codes. Each person switches it on in their profile; the team page shows who has. Its secret is kept sealed, a code works once, and switching it on signs every other browser out. Signing in with Microsoft or Google uses your own organization's second step.
- A person approves. Nothing the system reads is filed without a named person accepting it — including a certificate it finds in a certifier's directory. A supplier's approval status is a named person's decision; the risk flag beside it only informs. The product makes no release, approval or recall decision.
- A full log of who changed, accepted or rejected what, and when — the record an auditor asks for.
Your mailbox and your ERP
- Credentials you give us (a mailbox connection, an ERP key) are sealed with AES-256-GCM, bound to your company and to their one purpose, and never shown again. Changing an ERP's address requires the secret to be typed again.
- Foodhelm only reads your ERP: which ingredient is bought from which supplier. It writes nothing to it.
- When you connect your own mailbox, Foodhelm sends your supplier requests and reads replies to them. E-mails that fail their sender's authentication checks (SPF / DMARC) are not treated as a supplier's. Each company has a daily sending limit.
AI, and what it is not allowed to do with your data
- Documents are read, and the assistant answers, through Anthropic's Claude models over Anthropic's commercial API. Anthropic's commercial terms do not permit it to train models on that content.
- Foodhelm does not use your data to train models, build benchmarks or feed any shared index unless you opt in, in writing, with a name and a date.
- A reading is a proposal: it waits in Review for a person.
Services we use (subprocessors)
| Service | What for | Where |
|---|---|---|
| Microsoft Azure | Hosting, database, document storage, secrets | Canada |
| Anthropic | Reading documents; the assistant | United States |
| Microsoft 365 | The mailbox Foodhelm provides, when you use it instead of your own | Microsoft's data centres |
| Certifiers' public directories (OU Kosher, Star-K, USDA Organic INTEGRITY, SQF, Non-GMO Project) | Looking a certificate up: the identifier printed on it, or the certified company's name, is all that is sent | The certifier's |
| Your own Microsoft 365 or Google mailbox | Only if you connect it: requests and replies | Your provider's |
What we do not have yet
Foodhelm is in early access and does not yet have a SOC 2 report or an ISO 27001 certificate, and a company cannot yet require two-step verification of all its people (each person switches it on). We will answer a security questionnaire on request, and we will say here when either changes.
Leaving
Your matrix, documents and logs are yours. When you leave, we hand them over and then delete them, as set out in the terms. Questions or a security concern: hello@foodhelm.com.