Terms
Terms of Service
The baseline terms for using Lectern. Signed customer agreements control where they say something different.
Last updated: August 21, 2026
Using Lectern
These Terms govern use of lectern.systems, the intake form, the client portal, and the Lectern system we build and run for a customer at its own address on lectern.systems. If your business has a separate signed agreement with us, that agreement controls where it conflicts with these Terms.
Lectern is sold to small service businesses and is intended for a business and the people it authorizes. Where a business gives access to someone under 18, it does so under its own authority and is responsible for the permissions that requires; people under 13 are not given accounts unless a separate written agreement specifically permits it.
What you are getting
Lectern is one shared product. Every customer runs the same codebase with its own configuration: its own address, name, branding, data, and the set of features it has turned on. A build engagement shapes that configuration around how your business works; it does not produce a private copy of the software for you.
Features are enabled and disabled per customer, and the set you have can change as you ask for more or turn something off. We may add, change, or retire features across the product. Anything specific you are relying on, whether that is scope, timeline, a named feature, or a service level, belongs in an order form or a signed agreement rather than in these Terms.
Accounts and access
You are responsible for keeping credentials secure and for what happens under your account. A customer is responsible for authorizing its own users, assigning the right roles, and removing access when someone no longer needs it.
You may not access another business's data, attempt to cross the boundary between businesses, share credentials, or use the service in a way that interferes with its security or reliability.
Your data and the people in it
You own the data you put into Lectern. You grant us the limited rights needed to host, process, transmit, display, analyze, and back it up to provide and support the service.
You are responsible for having the rights, permissions, and notices required to put records about other people into Lectern: your customers, clients, members, families, patients, students, applicants, and staff. We use that data as described in the Privacy Policy, these Terms, and any applicable agreement, and never to advertise to anyone.
One business's data is never shown to another business and is never used to answer another business's question. Where we improve the product from usage, we do it with aggregated or de-identified information.
Prepared work and your approval
Lectern prepares recurring work ahead of you and shows it with the records behind it. Anything addressed to someone outside your business holds until a person at your business clicks. You are responsible for what you approve, so review it before you send it, the same as you would review a draft written by a person.
Once you schedule something for a time you chose, it goes at that time without another click. Scheduling is your approval.
Connected accounts
Where a feature works by connecting an account you already have, you set that connection up yourself through the provider's consent screen, and you are responsible for having the authority to connect it and for following that provider's own terms.
You can disconnect at any time in Lectern, and you can revoke access at the provider. A provider can change or withdraw its access at any time; if that breaks a feature, it is not a failure of Lectern under these Terms, and we will tell you when we know.
AI-assisted features
Some features use AI to read, extract, classify, summarize, verify, organize, or draft from your own materials. AI output can be incomplete or wrong, and it should be reviewed by an authorized person before anyone relies on it for a decision that matters.
These features do the admin, never the trade. They do not grade, tutor, diagnose, advise, or make a professional judgment about a person in your records, and nothing they draft for someone outside your business is sent until you click.
You are responsible for making sure the materials you upload may be processed by Lectern and its subprocessors. Processing your materials with an AI-assisted feature does not give Lectern any ownership of them.
Acceptable use
You agree not to misuse Lectern or use it for unlawful, harmful, or abusive activity.
- Do not upload malware, attempt unauthorized access, probe or attack systems, or disrupt the service.
- Do not use Lectern to collect or process data you are not authorized to handle.
- Do not submit content that infringes someone's rights, breaks the law, or exposes sensitive information unrelated to running your business.
- Do not use a connected account to send content that violates that provider's rules, or to send bulk messages to people who have not agreed to hear from you.
- Do not reverse engineer, scrape, resell, or benchmark the service except as a signed agreement or the law allows.
Intellectual property
Lectern and its software, designs, workflows, documentation, trademarks, and underlying technology belong to Lectern or its licensors. These Terms transfer none of that to you, and a build engagement does not transfer it either.
You keep ownership of your data and your materials. Feedback, suggestions, and ideas you give us may be used without restriction or compensation.
Fees, invoices, and money
Commercial terms such as price, build scope, renewal, cancellation, support, and service levels belong in an order form or a master services agreement. Where one applies, it controls.
As of the date on this page, Lectern has no payment rails of its own. It records what was invoiced and what came in and can draft a reminder, and it stores no cardholder data. Our own invoices to you settle outside the product, and the portal only records what we billed and what you told us you sent. If we add a payment integration, it will come with its own terms and its own entry in the subprocessor list, and the change will be handled the same way as any other material change to these Terms.
If no separate written agreement applies, we may suspend or end access for nonpayment, misuse, a security risk, or a breach of these Terms.
Changes to a live system
Changes to a running customer's system are staged and shown to that customer before they go live. Nothing reaches your live system because a build finished; a person promotes it deliberately. Preview addresses are for review and are not a place to keep real work.
We may perform maintenance, apply security fixes, and update shared infrastructure without prior notice where it is needed to keep the service safe or running.
Disclaimers and limits
Lectern is provided on an as-is and as-available basis except where a signed agreement says otherwise. We do not promise the service will be uninterrupted, error-free, or fit for every workflow a business has.
To the maximum extent allowed by law, Lectern will not be liable for indirect, incidental, consequential, special, punitive, or lost-profit damages. Any liability cap in a signed customer agreement controls for that customer.
Ending the relationship
You can stop using Lectern at any time, and cancellation terms in a signed agreement apply where one exists. We may suspend or end access for the reasons above, and we will give notice where it is reasonable to do so.
After termination we can help you export or delete your data, subject to backups, security logs, and legal requirements. The sections that should outlive the relationship do: ownership, disclaimers, limits, and anything by its nature meant to survive.
Changes
We update these Terms as the product changes, and the date at the top is the date of the current version. If a change is material, we will give reasonable notice by posting the update, emailing customers, or another appropriate channel.
Contact
Questions about these Terms can be sent to jake@lectern.systems.