Last updated: 5 October 2026
To run our products we rely on a small number of specialist companies — for hosting, sign-in, email, card payments and error monitoring. This page lists every one of them, what each can actually see, and how we tell you when the list changes. The list is set out per product: the Inventory Forecaster in section 2.1 and Goods In in section 2.2.
Your data is never sent to an AI or machine-learning service. There is no ChatGPT, Claude or similar anywhere in the product. The forecasting maths runs inside our own database.
When you use one of our products, your business data is stored and processed on our behalf by a handful of specialist providers. Under UK GDPR these are called "sub-processors". We remain responsible to you for what they do with your data.
We keep this list short on purpose. Every additional company with access to your data is additional risk, so we only add one where it genuinely earns its place.
| Provider | What it does for us | What it can see |
|---|---|---|
| Supabase Supabase Inc. |
Hosts the database. This is where your data actually lives. | All data you hold in the service: products, cost prices, stock levels, sales history, suppliers, purchase orders, and your users' names and email addresses. |
| Vercel Vercel Inc. |
Runs the application itself — the web pages and the background jobs. | Data passing through while a page loads or a job runs. Vercel does not keep a copy of your database. |
| Clerk Clerk.com (Clerk Inc.) |
Handles sign-in, passwords and user sessions. | Your users' names, email addresses and login activity. No product, stock or sales data. |
| Upstash Upstash Inc. (QStash) |
Schedules the overnight jobs — the nightly sync and report runs. | Scheduling information only: which account a job belongs to and what type of job it is. No product, stock or sales data. |
| Resend Resend Inc. |
Sends our outbound email — reorder reports, alerts and invitations. | The recipient's name and email address, and whatever is in the email itself (a reorder report will list products and quantities). |
| Sentry Functional Software, Inc. — EU data region (Germany) |
Error monitoring. When something breaks in the application, a report is sent so we can fix it before you have to tell us. | The error message, which page or job it happened in, the browser type, and the code path. Cookies, passwords, sign-in tokens, request contents and IP addresses are stripped before the report leaves our server. No product, stock or sales data is sent unless it happens to appear in an error message. Reports are stored in Sentry's EU region. |
| Open-Meteo Open-Meteo (Zurich) |
Supplies weather data, which helps explain seasonal demand. | Nothing. We request public weather figures for a geographic area. No customer data is sent. |
Payments: Inventory Forecaster subscriptions are bought and paid for through the Linnworks Application Store. Linnworks takes the payment under your own agreement with Linnworks, so it is not our sub-processor, and we never see your payment details. (Until 5 October 2026 this list included Stripe, which no longer handles any Inventory Forecaster data.)
Goods In uses a deliberately short list. Most importantly, your purchase orders, the items on them and the quantities you count never reach our servers at all — they pass directly between the scanner and your own Linnworks account. So none of the providers below can see them.
| Provider | What it does for us | What it can see |
|---|---|---|
| Firebase Authentication Google — London region (europe-west2) |
Handles sign-in: accounts, passwords and sessions. | Your users' email addresses and their sign-in activity. Passwords are held only in salted, hashed form. No purchase order, item or quantity data. |
| Firebase — database, server functions and hosting Google Cloud — London region (europe-west2), United Kingdom |
Stores your install record and runs the server that talks to Linnworks on your behalf. | Your Linnworks user ID, account email address, Linnworks server address and the install token. Not your purchase orders, items or quantities — those never reach our servers. |
| Firebase Crashlytics |
Crash reporting. When the app breaks, a report is sent so we can fix it. | The crash details, the device model and Android version, an anonymous account ID (the Firebase user ID, never the email address) and the Linnworks account ID, so we know which customer is affected. |
| Google Play Integrity Google — via Firebase App Check |
Confirms that requests come from the real app, not from something imitating it. | A device and app integrity verdict from Google Play. No business data and no account data. |
| Resend Resend Inc. |
Sends account-confirmation and password-reset emails. | The recipient's email address and the contents of that email. No purchase order, item or quantity data. |
Goods In collects no usage analytics, no advertising, no advertising ID and no AI service. We do not measure how your team uses the scanner. The only diagnostic data it sends is the crash reports listed above.
Your own Linnworks account is not a sub-processor of ours — see section 3.
Your Linnworks account is your system, not ours. You connect it, and you can disconnect it at any time. We read your products, stock and sales history from it — and write back purchase orders where you ask us to — acting on your instructions.
Because Linnworks is your own contract with your own provider, it is not a sub-processor of ours. Your relationship with Linnworks is governed by your agreement with them. The same is true for Goods In: it reads your purchase orders from your Linnworks account and books deliveries back into it, on your instructions.
Linnworks also collects the subscription payment for our apps, as the operator of its own Application Store and Payment Gateway. It does that under your agreement with Linnworks rather than as a provider acting for us, and we never see your card details.
We do not send your data to any AI or large language model service. Not for forecasting, not for analysis, not for "product improvement". The forecasting is ordinary statistics — sales history, seasonality and supplier lead times — calculated inside our own database.
If that ever changes, it would be a sub-processor addition and you would be told in advance under section 6 below, with the right to object.
Inventory Forecaster: your data is stored in a database hosted in Frankfurt, Germany (EU).
Goods In: the database and the server functions run in Google's London region (europe-west2), United Kingdom. Your purchase orders and counts are not stored by us at all — they stay between the scanner and your own Linnworks account.
Some of the providers above are incorporated in the United States. Where personal data is transferred outside the UK or EEA, we rely on the UK International Data Transfer Addendum and the EU Standard Contractual Clauses, together with each provider's own published safeguards.
Before we add a new sub-processor that will handle your data, we will:
Removing a sub-processor, or replacing one with another that does the same job to the same standard, does not require notice — but we will still update this page.
If you need more detail for your own compliance records — a specific provider's certifications, their data processing terms, or a completed security questionnaire — email privacy@englander.ai and we will help.