Terms of service
Version 1 · effective October 28, 2026
Draft. This text is not in force yet.
Who we are and what these terms cover
Lectern is software for teaching businesses: courses, exams, a question bank, printed papers, fees, a store and messages to guardians, in one place. It is made and run by [Company legal name], [Registered address].
In these terms, “we” and “us” mean [Company legal name]. “You” means the person or business that opens an account on our site and runs one or more platforms with it.
A platform is your own place on Lectern: your site, your admin, and the app your learners use. Your staff and learners use your platform under your terms, not ours. These terms are between you and us.
By opening an account or using Lectern, you agree to these terms, our privacy notice, our data processing addendum and our cookie policy. These terms limit our liability; the last section says how.
Changes to these terms
Our terms are numbered versions on our site. This is version 1. Each later version says what changed.
When you sign up, we record which version you accepted, when, and from what address.
When we publish a new version, we ask you to accept it before you next act on our site. Until you do, you can still sign in, read it, accept it, sign out or close your account.
If we don't enforce part of these terms, we haven't given up the right to enforce it later.
Your account
Accounts are for people. An account opened by a bot or a script is not allowed.
You must confirm your email address before you can create a platform.
Keep your password safe, and make sure your staff keep theirs safe too. We can't be responsible for loss or damage when someone signs in with a password you or your staff let slip.
You are responsible for what happens on your platforms, including what your staff do there.
You can change your name, language, email address and password yourself. A new email address takes effect only after you confirm it from a link we send to it.
Your platform, your people and your pages
You decide who works on your platform and who learns on it. Your staff act under the roles you give them.
Your site's terms, privacy, cookie and refund pages are yours to write. We never write them for you, and a page you haven't written doesn't appear on your site.
If you write your terms or privacy page, people who sign up on your platform are asked to agree to it, and your platform records which version each person agreed to.
For the personal data of your staff and learners, you are the controller and we are your processor. Our data processing addendum explains what that means.
Our name and brand appear on our own site and our own email. They never appear on your site or in your learners' app.
Trial, plans and paying us
A new platform starts on our base plan with a 14-day trial. We don't ask for a card to start.
You pay only for the modules you use. Our prices are set for each country in its own money; we don't convert them from another currency.
Our merchant of record, [Vendor — named at launch], takes payment for our plans and handles the tax on them. Where we agree to bill you by hand instead, your platform is paid up to the date we record, and it lapses on that date unless a further payment is recorded.
If a platform on a paid plan goes over its learner limit, we bill the extra learners; we never stop you admitting a learner. A platform on trial stops at its limit instead, because it has no bill to carry the extra.
If you remove a module, it stays on, and charged, until the end of the period you paid for. Then its screens close. On a trial it closes at once. Its data is kept; nothing is deleted.
When we retire a plan, we stop selling it to new customers. Customers already on it keep it.
We give you [Price change notice period — set before launch] notice by email before we change the price you pay.
Refunds: [Refund terms — set before launch].
Money your learners pay you
You are the merchant for everything you sell on your platform. Your learners pay you, not us.
Online payments go through your own payment gateway, on your own account and keys. We never hold your money, and we don't pay it out to you.
Receipts, refunds and any tax on your sales are yours. Lectern gives you the tools: numbered receipts, refunds through your gateway, and a record of who paid what.
When a plan ends
If a trial ends unpaid, a plan is cancelled, or a period paid by hand runs out, your platform shuts. Your site and app say that it is closed, and your staff are told to contact its owner.
The owner can still sign in, renew, and take all of the platform's data out.
Nothing is deleted when a platform shuts. But a shut platform isn't kept forever. Today, once a platform has been shut for 90 days since its plan ended, we schedule its deletion and email the owner the date. Renewing before that date keeps it.
The 90 days is our current setting and may change. Before any deletion, the owner gets an email with its date.
Taking your data out
Your data is yours. A platform's owner can take everything it holds out in one archive, at any time, whatever modules you have bought.
The archive is built in the background, and it can be taken even while the platform is shut.
A sheet that has a matching import can be read back into Lectern as it is.
Once a platform is deleted, we can't bring its data back. Take your archive first.
Closing your account or a platform
You can close your account yourself from your account settings. We ask for your password first.
If you own a platform, hand it to another member of its staff before you close your account.
Closing your account ends your place on every platform's staff; each platform keeps you in its records as former staff. We clear your name and other personal details and keep only the account's id, so past records still make sense. We send a last email to your address, and that address can open a new account at once.
An owner can ask us to delete a platform: [How an owner asks for deletion — set before launch]. The platform shuts at once, and the owner gets an email with the deletion date. Until that date the deletion can be cancelled. Today the wait is 20 days.
On that date we delete every record, file and domain claim the platform holds. Two kinds of record are ours, not the platform's, and are kept for their own periods: payments we recorded by hand, and our own log. Our privacy notice gives the periods.
How our staff reach your platform
Our office sees what it needs to bill and support you: your plan, your usage, your owner, how many staff you have, your domains, and our own log. Outside a support visit, it doesn't read your learners' records.
Every support visit states its reason, ends by itself, and is recorded on our log. The owner is emailed when a visit starts, with its reason and its time.
By default, our support staff need your grant to visit. You can grant access for a day, a week or a month, and end it at any time. A grant ends by itself.
In an emergency, one of our administrators can enter without your grant. They must give a reason, the owner is emailed at once, and the entry always shows on your platform's log.
A visit can only read until one of our administrators allows it to make changes, and that act is logged too. Our staff always sign in with a second factor.
What you may not do
Don't use Lectern to break the law or to harm anyone.
If you break these terms, we may suspend your platform or schedule its deletion. Every such act by our staff records its reason, and a scheduled deletion gives the owner the same email and the same wait as any other.
Some rules on messages are built in and can't be switched off: no text messages in the night hours set for the country, except a code or a link the person just asked for; a text sender name needs our approval; and a WhatsApp message goes only from a template Meta has approved.
In particular, don't:
- upload content you have no right to use, or that is illegal where you or your learners are;
- send messages people didn't agree to receive, or send them under a name you aren't entitled to use;
- try to reach another customer's data, or test, scan or overload our systems without our written permission;
- copy, resell or rebuild Lectern itself, or open accounts with bots or scripts;
- treat our staff abusively.
Your content and our software
You own what you and your people put into Lectern: your courses, questions, papers, records and files.
You give us permission to store, process, copy and show that content only as far as we need to run your platform and the services you use.
We don't check content before it goes up, but we may remove content that breaks these terms or the law.
Lectern itself, its code, design and words, is ours. Don't copy it without our written permission.
The services you connect yourself, such as your payment gateway, your AI provider or your WhatsApp Business account, run on your own accounts under their own terms. We store their keys encrypted and never show them back, but we aren't responsible for those services.
The service, maintenance and bugs
We build Lectern with care and test it a lot, but bugs happen. We fix security and privacy bugs first.
We may change, add or retire features. Moving between plans never rewrites your data.
Sometimes we take Lectern down for maintenance. When we plan it ahead, every customer sees a notice in their admin with the times. During maintenance, your site and app say they are down and when to try again.
We limit how many requests can come in at once, so one customer can't slow down the rest.
Lectern is provided “as is” and “as available”. These terms make no promise of a level of uptime.
Liability, law and questions
As far as the law allows, we aren't liable for indirect or consequential losses, such as lost profits, lost data or lost goodwill, however they arise.
Our total liability to you is limited to [Liability cap — set before launch].
These terms are governed by [Governing law — set before launch]. Disputes go to [Courts — set before launch].
Questions about these terms: [Support contact email].