Sub-processor List
1. Current sub-processors
| Sub-processor | Purpose | Data categories | Location |
|---|---|---|---|
| Supabase | Production Postgres database with row-level security | Customer operational data, customer user data | United States |
| Clerk | Authentication and session management | Customer user data (name, email, auth credentials) | United States |
| Cloud and edge providers | Hosting, compute, and content delivery | All data categories in transit and at rest | United States |
| LLM inference provider (name to be published on confirmation of contract terms) | AI inference for the Copilot and Routines | Customer operational data sent for inference | United States |
| PostHog | Product analytics | Site visitor usage events; for demo requesters, name, work email, company, role and number of locations | United States |
| Hostinger | Hosting for foodlineai.com and its demo-request database | Site visitor requests, demo requester data | France |
| Slack | Internal alert to our team for each new demo request | Demo requester data (name, work email, company, role, plan details) | United States |
| Whop | Community signup and payments | Community member data (name, email) | United States |
2. Changes to this list
We will update this page when we add or remove a sub-processor. We will provide at least 30 days notice before a new sub-processor begins processing customer data. To receive notifications of changes, contact privacy@foodlineai.com and request to be added to the sub-processor change notification list.
3. Open items
The model provider's name will be published on this page once contract terms, including data processing and retention provisions, are confirmed. The provider is currently used for LLM inference only, with no customer data used for model training.