Authorized Sub-Processors

Primary database, authentication provider, object storage and serverless (edge function) runtime for the whole platform. Database backups are managed by Supabase.

All application data: accounts, course content, learner progress, audit events, and files uploaded to course materials storage.

Hosts the production build of the Next.js application, edge delivery and web analytics.

The built application (compiled code, not a copy of the database), its HTTPS traffic, request metadata and cookieless page-view counts.

Single gateway to third-party language models, so the platform is not locked to one model vendor.

Prompts and generated content for AI-powered activities (coaching, content generation, quiz assistance) — routed to the underlying model configured per activity. Guardrails keep untrusted user content out of the system prompt before it leaves our servers. Text, speech and transcription run under zero data retention. Image and video generation (only where an organisation switches on "Image and video generation without zero data retention") use a separate key under which the image or video provider may keep the prompt and the output for a short time.

AI model provider, and the AI assistant our support team uses to triage support requests and draft replies.

AI prompts and generated content, when an AI activity is configured to use a Claude model (via OpenRouter or direct). For support: the support emails, chat transcripts and tickets our team processes with Claude to triage them and draft replies.

AI model provider.

AI prompts and generated content, when an AI activity is configured to use an OpenAI model (via OpenRouter or direct).

AI model provider.

AI prompts and generated content, when an AI activity is configured to use a Gemini model.

Text-to-speech for course narration.

Lesson narration text sent for speech synthesis, only when course narration is generated.

Email delivery (invitations, reminders, alerts, receipts).

Recipient email addresses, names and message bodies of transactional and notification emails.

Email sending (SMTP relay for transactional and notification email) and our support and contact mailboxes.

Recipient email addresses, names and message bodies of emails sent through Google Workspace SMTP, and the messages people send to our support and contact mailboxes.

Error monitoring, so faults are found and fixed.

Error reports and performance traces: stack traces, the page or API route, browser and device type, and the internal user ID. Email addresses, IP addresses, cookies, request bodies and tokens are removed before a report is sent.

Payments and subscription billing.

Payment card, UPI and net-banking details, billing contact info.

Organisation-configured payments for storefront sales.

Payment details for that organisation’s own storefront sales, held by Stripe on behalf of the organisation.

Delivering web-push notifications.

A push subscription endpoint and the notification payload, only for people who opt in to browser notifications.

Website analytics.

Cookies (_ga, _ga_*), page views, device and browser metadata — public website only, after consent.

Marketing attribution.

Cookies (_fbp), page views, conversion events — public website only, after consent.

Measuring which advertisements lead to sign-ups.

Cookies (_gcl_au), ad-click identifiers and conversion events — public website only, after marketing consent.

Marketing attribution for LinkedIn campaigns.

Cookies (li_fat_id), page views, device metadata and conversion events — public website only, after marketing consent.

Alternative email delivery providers and sending-domain verification.

Recipient email addresses, names and message bodies, only when EMAIL_PROVIDER or an organisation’s sending domain is set to one of these vendors.

Stock imagery for course authoring.

Search keywords typed by a course author when searching stock photos or video; no learner data.

Customer-initiated integrations. Not engaged by us on a customer’s behalf; listed for transparency.

Only the data an organisation administrator chooses to sync (for example names, email addresses, completion records, calendar events) after that administrator authorises the connection with the vendor.

Customer-initiated xAPI connection, configured by an organisation administrator in Admin > LRS. Not engaged by us on a customer’s behalf; listed for transparency.

xAPI statements (who did what learning, when, with what result). Forwarding sends copies of the organisation’s statements to that LRS; import pulls statements from that LRS at the customer’s instruction (statements pulled from a customer-named LRS at the customer’s instruction).

Customer-initiated chat app (CHT). Only engaged once an organisation administrator installs the Academy app in their Microsoft Teams tenant; listed for transparency.

Replies and cards the Academy bot posts into a Teams chat the organisation installed it in: the message text, buttons and the Teams conversation and user identifiers needed to deliver them.

Third-party course catalogues an organisation licenses.

Catalogue and enrolment requests made with credentials the organisation supplies; learner identifiers only where the organisation enables enrolment sync.

Customer-initiated connector for ambient learning (Gmail, Google Drive). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator (or, for Gmail, the individual worker) authorises, to read the mailbox message metadata or Drive files that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (Outlook, SharePoint). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator (or, for Outlook, the individual worker) authorises, to read the mailbox items or SharePoint documents that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (Zendesk). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the support tickets that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (Freshdesk). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the support tickets that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (ServiceNow). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the incidents that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (Jira, Confluence). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the Jira issues or Confluence pages that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (GitHub). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the repository activity that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (Notion). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the Notion pages that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (HubSpot). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the CRM records that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (Salesforce). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the CRM records that connection is scoped to so they can be matched to learning in the flow of work.

Customer-initiated connector for ambient learning (Zoho CRM). Not engaged by us on a customer’s behalf; listed for transparency.

Requests made with the OAuth or API credentials an organisation administrator authorises, to read the CRM records that connection is scoped to so they can be matched to learning in the flow of work.

Delivering learner messages over WhatsApp and SMS.

The recipient phone number and the text of the learner message for organisations that enable the WhatsApp and SMS add-on, when the platform has configured Meta as the WhatsApp provider; inbound replies and opt-outs (STOP) are received back by webhook.

Delivering learner messages over WhatsApp and SMS.

The recipient phone number and the text of the learner message for organisations that enable the WhatsApp and SMS add-on, when the platform has configured Twilio as the WhatsApp or SMS provider; inbound replies and opt-outs (STOP) are received back by webhook.

Delivering learner messages over WhatsApp and SMS.

The recipient phone number and the text of the learner message for organisations that enable the WhatsApp and SMS add-on, when the platform has configured MSG91 as the SMS provider.