Subprocessors

These services process institution data (Educator or Student personal data, or course data) on our behalf. Each is bound by its data processing agreement or equivalent terms. All transfers use TLS 1.2 or higher. All institution data is stored in the United States. Where a provider's processing region is not listed here, see that provider's terms.

Amazon Web Services (AWS). Purpose: backend API, LMS connection service (LTI 1.3), file storage, search, queues, short-lived operational records, keys and secrets, and logs. Data: Educator and Student account data (name, email, LMS user ID, role), rosters, answers, grades, uploaded files including scanned paper exams, and logs. Location: United States (us-east-1).

Supabase. Purpose: primary database (PostgreSQL) and sign-in (Supabase Auth, since 30 September 2026). Data: all account and course data, including names, emails, LMS user IDs, enrolments, answers, grades and activity; sign-in identities and sessions. Location: United States (AWS us-east-1).

Vercel. Purpose: hosts the web apps (Mayflower, Library, Educators). Data: data shown in the apps passes through while pages are served. Location: United States.

Upstash. Purpose: cache for API responses and access tokens. Data: short-lived cached API responses, which may include course and grade data. Location: see provider terms.

OpenAI. Purpose: Educator AI features, including grading support, the analytics assistant, and question and content generation. Data: Student answers and handwriting images, sent as written for grading; course data for the analytics assistant. Student names and emails held in our records are replaced with opaque references before model calls. Not used for training. Location: see provider terms.

Anthropic. Purpose: Educator AI features, including question checking, lecture slides and storyboards. Data: course content only; no Student data. Location: see provider terms.

Google Cloud Vision (Google Cloud). Purpose: reads handwriting on scanned paper exams. Data: image crops of handwritten Student names, student IDs and answers. Location: see provider terms.

Auphonic. Purpose: audio clean-up of Educator-recorded lecture narration. Data: Educator voice recordings only; no Student data. Location: see provider terms.

Intercom (including Fin). Purpose: in-app support chat and help centre; Fin, Intercom's AI agent, answers support messages. Data: name, email and role; for Students also school, class and course; support messages. Location: United States.

PostHog. Purpose: product analytics, including session replay. Data: usage events, pages viewed, internal user ID and role, Educator email, and session recordings. Location: United States.

Sentry. Purpose: error monitoring for the web apps. Data: error reports (page, browser and device), which may include user ID and IP address. Location: see provider terms.

SendGrid (Twilio). Purpose: account and service email, including sign-in emails. Data: recipient name and email; email content (sign-in links, invitations, notices). Location: see provider terms.

Mux. Purpose: video hosting, streaming and playback analytics. Data: Educator-uploaded video and audio; playback data linked to an internal user ID, with IP address and browser details. Location: see provider terms.

Stripe. Purpose: payments through Stripe-hosted checkout. Data: purchaser name and email, payment status and customer ID; card data is held by Stripe only. Location: see provider terms.

Contentful. Purpose: published course content. Data: course content only; no Student data. Location: see provider terms.

Our team uses these tools to run the company. They are not used to process Student data.

Slack: team messaging and system alerts. Staff messages and alerts; no Student data.

Linear: issue tracking. Tickets; no Student data.

GitHub: source code and code review. Source code; no Student data.

Google Workspace: staff email and documents. Company email and documents; no Student data.

Video rendering runs inside our own AWS account, so it is not a separate subprocessor.

We update this list when we add, replace or stop using a subprocessor. The Security Officer (Andrew Snead, CTO) reviews each new vendor's security and data terms before we engage it.

Institutions can ask for the current list, or ask about a change, at privacy@blended-teaching.com.