Last updated: 3 August 2026
Sub-processors
FoodCore does not run everything itself. A handful of other companies handle data on our behalf so the service works — the one that sends our emails, the one that runs the servers, and so on. In data protection language those companies are our sub-processors. This page lists all of them, what each one receives, why, and where it is based.
A sub-processor is a supplier we pass data to so we can run FoodCore for you — they work to our instructions, they cannot decide to use your data for their own purposes, and this page is the complete, current list. This page sits alongside our Privacy Policy, which explains what data we hold in the first place.
No sub-processor has been added or removed. Two entries are described more accurately:
- Anthropic. The photographs sent for scanning are supplier purchase documents — the receipt or delivery note for stock you buy in — not your own customers' receipts. Neither AI feature sends your customer records. The previous wording was wider than the feature actually is.
- Shopify / WooCommerce. What comes in is orders, with the contact and address details attached to them.
1. Sub-processors Used to Deliver the Service
These handle data from inside the app — your account, and the data you hold about your customers and staff.
| Sub-processor | What they receive | Why | Location |
|---|---|---|---|
| Anthropic, PBC Claude API |
Recipe and ingredient text when you run an AI Check. When you scan a purchase, a photograph of a supplier receipt or delivery note — a business-to-business purchase document, which normally shows your own business details and occasionally the name of whoever signed for a delivery. Neither sends your customer records. | Runs the AI Checks feature, and reads scanned supplier receipts and delivery notes into stock. Anthropic’s API terms provide that inputs are not used to train their models. Scan images are deleted once the scan is applied, discarded or fails, with a backstop sweep for scans never reviewed; while they exist they are stored privately and only an authenticated request can read one. | United States |
| Stripe incl. Stripe Connect |
Your billing name and address for your FoodCore subscription. Where you connect your own Stripe account through Stripe Connect, your own customers’ payment data. | Takes your subscription payment, and lets you take payments from your customers. Card entry happens only on Stripe-hosted pages — no card field is rendered on any FoodCore page and we never receive or store card numbers. | United States |
| Google Calendar API |
Staff shift data — and only where an individual user chooses to connect their own Google calendar. Nothing is sent otherwise. | Puts a user’s shifts into a Google calendar. We request the calendar.app.created scope, which reaches only a calendar FoodCore itself creates — we cannot read or alter existing calendars. Under Google’s Limited Use requirements this data is not used for advertising, not sold, and not used to train models. |
United States |
| Shopify / WooCommerce | Inbound: orders from your own storefront, carrying the buyer’s name, email address, phone number, delivery address and order lines. Outbound: fulfilment status. | Keeps your online shop and your kitchen in step, in both directions. Only applies if you connect a storefront. | Shopify: United States. WooCommerce: runs on hosting you control, so wherever you host your shop. |
| Resend | Recipient email address and the contents of the message being sent. | Sends transactional email — the messages the app has to send to do its job, such as confirmations and account emails. Also handles the welcome email for free-tool marketing opt-ins. | United States |
| Hosting / infrastructure provider | Everything held in FoodCore, at rest — your account data and all the data you hold about your customers and staff. | Runs the servers and the database the service operates on. | Details of the current provider are available on request — email info@foodcore.io. |
We do not currently use any SMS or WhatsApp messaging provider. If we engage one, it will be added here and you will be told before it starts.
2. Sub-processors Used for This Website and Our Marketing
These relate to foodcore.io itself — the marketing site, our newsletter and our advertising. They do not receive data from inside your FoodCore account. Where marked consent-gated, nothing is set or sent unless you accept cookies; see our Cookie Policy.
| Sub-processor | What they receive | Why | Location |
|---|---|---|---|
| Google Analytics 4 G-EJJZYBXJYE |
Anonymised website usage data. No personal data from customer accounts. Consent-gated. | Tells us which pages on this website people read. | United States |
| Google Ads AW-724508800 |
Conversion events such as trial sign-ups. No account data. | Measures whether our advertising works. | United States |
| PostHog | Anonymised usage data, session recordings of visits to this website, heatmap data. No account data, passwords or payment details. Consent-gated. | Shows us where visitors get stuck on the website. | EU-hosted (eu.i.posthog.com) — no international transfer |
| Cloudflare | Technical identifiers and IP addresses. No personal account data. | Serves the website quickly and absorbs attacks on it. | United States / global |
| Tawk.to | Chat transcripts and anything you volunteer in a chat. May collect IP address and browser data. | Runs the live chat widget on this website. | United States / global |
| Sender.net ad6083267e6001 |
Email addresses of newsletter subscribers only (consent-based). | Sends our newsletter. | EU-based — no international transfer |
| Web3Forms | The details you type into a website form — name, email address, message, and for free tools the result you asked us to email you. No account or payment data. | Delivers website form submissions to our inbox. | United States |
| Endorsely | Affiliate click data (anonymised). No personal account data. | Runs our affiliate programme and tracks referrals. | EU / EEA |
3. How We Tell You About a New Sub-processor
If we want to add a sub-processor, or materially change what an existing one does, we will:
- notify active subscribers by email at least 14 days before the change takes effect, so it is not something you discover afterwards;
- update this page and the sub-processor table in the Privacy Policy, and move the “last updated” date at the top of this page;
- tell you what the new supplier receives and why, in the same terms as the tables above.
The 14 days exist so you have time to object or ask questions before anything changes. If you have a concern about a proposed sub-processor, email info@foodcore.io with the subject line “Sub-processor”.
4. Transfers Outside the UK
Several of the companies above are headquartered in the United States: Anthropic, Stripe, Google, Shopify, Resend, Cloudflare, Tawk.to and Web3Forms.
When data goes to a company outside the UK, UK data protection law requires a recognised safeguard to be in place first. Ours are the Standard Contractual Clauses (SCCs) together with the UK International Data Transfer Addendum — a set of standard contract terms, approved for use under UK law, that bind the overseas company to protect the data to a UK-equivalent standard and give people rights they can enforce. In everyday terms: the data can travel, but the protection travels with it.
Two entries do not involve a transfer at all. Sender.net is EU-based and PostHog is hosted on EU infrastructure.
WooCommerce is a special case: it runs on hosting you control, so where that data sits is determined by where you host your own shop, not by us.
5. Questions
For a copy of the safeguards in place with any sub-processor, or any other question about this list, email info@foodcore.io. For the wider picture — what we collect, what we do with it, how long we keep it and what deletion actually does — see the Privacy Policy.