Subprocessors
Version 1 · effective October 28, 2026
Draft. This text is not in force yet.
What this list is
We use other companies, such as cloud providers and an email service, to run Lectern. When one of them handles personal data for us, it is a subprocessor.
Each gets only the data its job needs, and each is bound by a written agreement that protects that data.
The companies are named at launch. Until then, this list shows each job and the data it receives.
Hosting
Runs Lectern's servers: our site, our office, and every platform's site, admin and app.
Vendor: [Vendor — named at launch]. Location: [Vendor location — named at launch].
- Everything Lectern processes passes through it: accounts, platforms, and the records of every platform's staff and learners.
Database
Stores the records of our accounts and of every platform.
Vendor: [Vendor — named at launch]. Location: [Vendor location — named at launch].
- Accounts on our site and the platforms they run.
- Each platform's records of its staff, learners, guardians and buyers: enrolments, attendance, exams and marks, fees, orders, receipts, messages and activity log.
File storage
Stores files.
Vendor: [Vendor — named at launch]. Location: [Vendor location — named at launch].
- Files that platform staff and learners upload, such as images and attachments.
- Documents a platform issues and keeps.
Email delivery
Sends our email, and each platform's email, including email a platform sends from its own domain.
Vendor: [Vendor — named at launch]. Location: [Vendor location — named at launch].
- The recipient's email address and name.
- The message: sign-in links and codes, notices, receipts, and what a platform writes to its learners and guardians.
- Whether the message arrived.
Text messages (SMS)
Sends text messages for platforms, such as sign-in codes and messages to learners and guardians. A platform's own sender name is used only once we have approved it.
Vendor: [Vendor — named at launch]. Location: [Vendor location — named at launch].
- The recipient's phone number.
- The message text and the sender name.
- Whether the message arrived.
Video hosting
Holds and plays the videos in a platform's courses, one library for each platform.
Vendor: [Vendor — named at launch]. Location: [Vendor location — named at launch].
- The videos a platform's teachers upload.
- Each request to play a video, from the learner's browser, through a signed address that expires.
- How much each library stores and delivers each day, which we use to count the platform's use.
Payments for our plans
Our merchant of record. It takes payment for our plans and handles the tax on them. It never sees a platform's learners or their payments.
Vendor: [Vendor — named at launch]. Location: [Vendor location — named at launch].
- The paying customer's name, email address, country and billing details.
- The plan bought, its price and its dates.
Error monitoring
Tells us when something breaks, so we can fix it.
Vendor: [Vendor — named at launch]. Location: [Vendor location — named at launch].
- The technical report of the error.
- The signed-in person's account id, and nothing else about them: no email address, no name.
Not on this list: services you connect yourself
A platform can connect its own accounts at other services. Those services work for the platform, under its contract with them, so they are not our subprocessors.
- the platform's own payment gateway, which takes its learners' payments on its own keys;
- the platform's own AI provider, reached with its own key;
- the platform's own WhatsApp Business account at Meta.
Changes to this list
When we add or replace a subprocessor, we publish a new version of this page saying what changed, and tell customers [Notice period for a new subprocessor — set before launch] ahead.
Questions: [Privacy contact email].