Legal
Privacy policy
Lectern is built to keep your work on your device. This says what reaches us, when, and what we do with it.
Effective October 23, 2026
Without an account
The apps record, edit, caption and export on your device. What you record, write or answer stays there unless you share it or go live. The apps don't track you, show ads, or report how you use them, and they send a crash report only if you say yes. Nothing in Lectern recognizes faces or voices, or works out who is speaking.
A few things do reach the network, and only these:
- The speech model. The first time you make captions, the desktop app downloads Whisper's speech model from app.lecternvideo.com. Captions are then made on your device.
- Following your voice. The prompter listens with Whisper, on your device, in the Windows and Linux apps, and elsewhere with your system's speech recognizer unless you choose Whisper in Settings. Some recognizers work on the device; others send audio to their maker under its own privacy policy: Windows' online speech recognition goes to Microsoft; Apple's and Android's may go to Apple or Google when the language's on-device model isn't installed; and in the browser, Chrome sends audio to Google. The IT page lists each one.
- Going live. When you choose Go live on…, the app streams to the service you pick (YouTube, Facebook and so on), straight from your device, unless you choose to send it through Lectern.
- Updates. The desktop app checks Lectern's cloud for a new version a few seconds after it opens and every few hours while it's open, and downloads one if there is. The check sends nothing about you; like any request, it carries your network address.
- Crash reports, if you say yes. When Lectern runs into a problem, it asks whether to send a report, and shows you what's in it: what went wrong in Lectern's own code, the app's version, your system (Windows, say, or the browser), and when. Nothing of yours is in it: no recordings, scripts, file names or paths, account or device. It goes to Lectern's cloud, which passes it on to Sentry without your network address. In Settings you can have reports sent without asking, or never kept.
Nothing else leaves the device. The IT page has the detail.
With an account
For now, accounts are offered in the United States and Canada (we check the country a sign-up comes from by its network address, and keep nothing of it). The app works anywhere without one.
An account (optional) holds:
- your name, email address, and password (stored only as a one-way hash);
- the devices signed in, with each one's network address and browser or app version, so you can be signed out of them and abuse can be stopped;
- what you've bought, and your organizations and your role in them;
- if you turn on two-step sign-in, the key your authenticator app shares with us and your backup codes, both encrypted;
- the files you upload to share, with the network address each was uploaded from, and your share links;
- if you sync your library, the files you sync, each with its name and folder in your library, its size and type, when it was last changed, and the name of the device that changed it;
- your payments' records: what, when, how much. Card details go to our payment reseller, PaddleLink (Stripe)Paddle or Link (Stripe), and never reach us;
- if you're in an organization's Library, what you publish there, your comments, likes, bookmarks and who you follow.
Organization admins see their members' names, email addresses and the storage each uses, and the names and sizes of files in the organization's shared storage with who uploaded each. They see the share links whose files are in that storage, with who made each, and viewers' answers to those projects' questions and their scores, which they can download, and each viewer's views of those links. They can't open files in the shared storage that no link uses, and they don't see what you sync, which is kept in your own storage. An organization that verifies its email domain can let people with an address there join by confirming it, as members or as viewers of its Library. Its admins also see its activity log: what each admin changed in it, and who joined and left, with when.
We look at an account's records only to give support you ask for, to keep the service safe, or when the law requires it. Our support tools can show the app as an account sees it; each use is logged, and they can't change its password, email or name, or delete it.
Syncing your library
If you're signed in and have storage, the apps sync your library, so it's on every device you sign in on: new recordings, scripts and projects (with their captions and transcripts), and anything else you choose to sync. Turn off Sync new files in the app's Settings, or untick Sync to the cloud when you record or add something, to keep it on your device. Signed out, nothing syncs.
Synced files are uploaded to our storage at Cloudflare (R2) and kept there for you. No link serves them, and other accounts, organization admins included, can't open them. They count against your storage. Keep local deletes a file's synced copy from our storage at once, and leaves it on your device. Deleting a synced file moves it to the trash on your other devices too; its copy is kept 30 days, so it can be restored on any of them, and is then deleted.
Streaming through Lectern
If you choose to send a live stream (or a video at a set time) through Lectern, the app uploads it to us in short pieces, and our relay sends it on to the services you picked. The pieces are deleted within two days of their upload (a video set for a later time, within 33 days, since it can be set up to a month ahead) and aren't kept as a video, unless the stream has a page on Lectern: then its replay is kept, with the page, until you delete the page in the app, and it counts against your storage (or your organization's, if its hours paid for the stream). The services' stream keys go to the relay with each broadcast and are dropped when it ends (a scheduled video's, once it has gone out); they're never saved in our database. We record each broadcast's times, destinations and the hours it used, to count your hours.
Sharing
When you share by link, anyone with the link can watch what you shared. Viewers don't need an account. If a project asks questions, viewers' answers are stored for its owner, by a random id for viewers who aren't signed in, unless the owner turned off keeping answers: then the page sends nothing about who watches. Search engines are asked not to index shared pages.
When something shared plays, the viewing is counted for the link's owner: when it started, how much was watched and where it stopped, whether it finished, the kind of device (phone, tablet or computer) and the website it was embedded on. A viewer who isn't signed in is counted by the same random id as their answers; a project whose owner turned off keeping answers counts each viewing without any id. No network addresses are kept with viewings or answers. If the owner keeps a link to invited viewers, the email addresses they invite (typed in, or sent by a payment service the owner uses) are kept with the link, and a viewer's address is used to email them a code; passes last up to 30 days in the browser. If you sign in with Google, Microsoft or Apple, we get your name and email address from them (with Apple's Hide My Email, an address of Apple's that forwards to yours), and keep which provider you used; we don't get your password there, and they learn only that you signed in to Lectern. A stream watched on Lectern keeps its chat's messages, by the name given (or the account's), with the stream's page: until its host deletes the page, or their account. The host can delete messages while the stream is on; once it's over, the chat is closed and what was said stays on the page. If the owner turns comments on, anyone with the link can comment by the name they give, and the comment stays with the link for its owner; a signed-in commenter's comment is kept with their account too, and is in their data export.
Anyone watching can report what they see. A report holds what it says, the email address the reporter gives (if any) and their network address, so we can act on it and stop false reports.
An organization's Library
An organization can have a Library: a place, for its people only, where members publish videos and projects, and members and viewers watch, search, comment, like, bookmark and follow. Viewers join with a free account, by an invite code or their school's or organization's email domain, and get no storage or other part of its plan.
- What you publish (its title, description, category and collections) is seen by everyone in the organization, with your name. Publishing a synced recording makes a share link from it, as sharing from the app does: we copy the file (and its captions and chapters) for the link, and our cloud makes smaller copies of it for slow connections. The recording's captions are kept as words so the Library's search finds what was said.
- Comments are seen by the organization's people, with your name. The video's creator and the organization's admins can hide or delete them, and the creator is emailed when there are new ones.
- Likes, follows and views are shown as counts; who liked or follows whom isn't shown to others. What you bookmark is yours alone. To count each person's view once a day, we note who opened what that day (UTC), then forget it; only the counts stay.
- Reports of a video or comment go to the organization's admins, with what the report says and who made it. Reports of child sexual abuse material or intimate images shared without consent also come to us, and hide the video at once.
Search engines are asked not to index the Library. As with any share link, a published video's files can be opened by someone who has their exact address. The organization decides what its Library is for; we run it for them.
This website
This website uses no cookies, and makes no requests to anyone but Cloudflare, which hosts it, unless you play a help page's video (below). Cloudflare counts its visits for us (Cloudflare Web Analytics): the pages viewed, the site that sent you, your country, and your browser and kind of device, with nothing kept in your browser to tell visits apart. We see only the totals. The website remembers a light or dark theme you pick in your browser. If you join the waitlist, we keep your email address to tell you when Lectern opens. We also keep the country you joined from and the app and language you used, to know where to open next. We keep all of it until you make an account or ask us to remove it. The app in the browser, and an organization's Library, use cookies only to keep you signed in: one sign-in for both, at app.lecternvideo.com and library.lecternvideo.com.
If you send us feedback from the feedback page, we keep what you write, and your email address if you give one, so we can read it and reply, and it's emailed to our inbox. We delete it from our database after a year and from our inbox once we've dealt with it, or sooner if you ask at support@lecternvideo.com. Votes for what's in development need no account: your browser remembers what you voted for and a random code, sent with each vote so you can take it back, and we keep each vote with a one-way hash of that code. To stop one network address sending too much or voting twice, we keep a one-way hash of the address, made with a key that changes every day, with the message or vote until the day is out (UTC), then delete it. We never keep the address itself.
A help page's video loads nothing from YouTube until you press play. Then it plays from YouTube (youtube-nocookie.com), which gets your network address and may store data in your browser, under Google's privacy policy.
Why we use it
Each use has a reason the law recognizes (in the EU and UK, a "legal basis"):
- To give you what you asked for (our contract with you): your account and sign-in, storage, syncing your library, share links, streaming, organizations and their Libraries, and what you buy.
- To keep Lectern safe (our legitimate interest, and yours): devices' network addresses, sign-in limits, reports, the address each upload came from, and the daily hashes that limit feedback and votes.
- To keep Lectern working (our legitimate interest): errors on our servers, and the website's visit counts.
- Because the law requires it: payment records for tax, and reports of child sexual abuse material, with what's kept for them.
- Because you chose it (consent): the waitlist, feedback you send, crash reports you send, and your name on a project that asks for it. You can take it back at any time.
For an organization's members, and the answers to a link's questions, the organization or the link's owner decides what the data is for, and we handle it for them. We don't use anything for advertising, profiling or training AI models, and nothing about you is decided automatically.
Who we share it with
Only the services that run Lectern, for that purpose:
- Cloudflare: hosting, storage, the database, the streaming relay, making copies of recordings published in a Library, and sending email (sign-in codes, invitations and notices). Cloudflare may also check images served through its network against lists of known child sexual abuse material, and report matches itself.
- Sentry: crash reports you choose to send, and errors on our servers. Sentry doesn't get your network address, and it keeps them for up to 90 days.
- Purelymail: our email inbox. What you write to us (support, legal, security, and feedback from this website) is kept there.
- Paddle: payments. Paddle is the merchant of record and keeps purchase records under its own privacy policy.Stripe: payments, sold through Link, Stripe's checkout. Link is the merchant of record and keeps purchase records under its own privacy policy.Paddle and Stripe (sold through Link, Stripe's checkout): payments. Each is the merchant of record for what it sold, and keeps purchase records under its own privacy policy.
- Apple and Google: purchases made in the iPhone, iPad and Android apps.
- The services you stream to (YouTube, Facebook and so on) get what you send them, under their own privacy policies.
We don't sell data, or share it for advertising. We don't scan what you upload. We disclose what the law requires, such as reports of child sexual abuse material to the National Center for Missing & Exploited Children (NCMEC), and answers to valid legal process (how we handle those).
Where it's kept
We're in the United States, and Cloudflare keeps the database and files in North America. Crash reports are kept by Sentry in the United States too. If you use Lectern from elsewhere, what you send comes here. Cloudflare's data processing terms, which are part of our agreement with it, include the European Commission's standard contractual clauses for that.
How long we keep it
- Your account, until you delete it.
- Files in storage, until you delete them. 90 days after your storage ends, files beyond any free allowance are deleted (an organization's shared storage, 30 days after its plan ends).
- Files you sync, until you delete them or keep them local. A synced file you delete is kept 30 days, so it can be restored, then deleted. When your storage ends, synced files are deleted with your other files, as above; the copies on your devices stay.
- Pieces of a shared project that no link uses (a share stopped partway, say), 7 days after the last upload to that project.
- What you shared in an organization's storage, after you leave it: if the organization keeps what's shared with it, until the organization deletes it (with no one's name on it once you delete your account); if it lets you take it, it moves to your own storage, and what doesn't fit stays 30 days for you to make room, then it's deleted.
- A stream's pieces, up to two days after they're uploaded; a video set for a later time, up to 33 days. A stream with a page on Lectern: its replay and its chat, until you delete the page (or your account).
- Viewers' answers, for a year; viewings, for about 13 months.
- In a Library: what you publish, until you or the organization take it out (or its link is turned off); comments, likes, bookmarks and follows, until they're deleted, or your account is; who opened what, until the day is out.
- Crash reports, up to 90 days at Sentry. We keep none ourselves.
- Feedback from this website, a year in our database. The hash of a network address kept with feedback or a vote, until the day it was made is out.
- Files on a link taken down for breaking our rules, 30 days, unless the link was hidden by a report of child sexual abuse material or intimate images that we haven't reviewed yet.
- Material kept as evidence for a report to NCMEC, at least a year from the report, as the law requires, and until we close the case.
- An account's data that police or a court asked us to preserve, 90 days from the request (180 if it's renewed), or until the process it was for is done.
- Reports about an account, after the account is deleted: they're kept for others' safety.
Your choices and rights
Download everything your account holds, or delete your account and its files, from the app's Account screen. Change your name, email and password there too. You can ask us anything about your data at support@lecternvideo.com.
Wherever you live, you can ask us to show you what we hold about you, correct it, delete it, stop or limit a use of it, or send it to you in a form you can take elsewhere. We answer within a month. Where an organization or a link's owner decides what the data is for, we pass your request on to them, or help them answer it. In the EU and UK, you can also complain to your data protection authority.
Children
Accounts are for people 13 and older: we don't knowingly collect personal information from children under 13, whom the Children's Online Privacy Protection Act (COPPA) protects. If we learn that a child under 13 has made an account, we delete it and what it holds. That includes viewer accounts in an organization's Library: a school gives viewer access only to students 13 and older. Children can watch what's shared with them: a link whose owner turned off keeping answers sends nothing about who watches, no name, answers or id.
Schools
Teachers and staff at any school can use Lectern, and a school can buy seats for them. Seats for students are for colleges and universities: a primary or secondary (K–12) school's plan is for its staff, and students in grades K–12 can't have seats in it. Its students 13 and older can be viewers of its Library, with accounts of their own.
K–12 students can watch what their teachers share. For a project with questions, the teacher turns off keeping answers, and the link then sends nothing about who watches. A K–12 school that wants its students' answers kept needs a data privacy agreement with us first (in Illinois, under the Student Online Personal Protection Act); write to us.
When a college or university uses Lectern, we act as a "school official" under FERPA: we use students' records only to provide the service, under the school's direction, and never for advertising or sale. We'll sign a short data addendum saying so.
A student's account in a college's plan holds:
- their name and email address, and their password as a one-way hash;
- the devices signed in, with each one's network address, browser or app version and times;
- their organization, their role in it, and how and when they joined and left;
- the files they upload to share (with each one's size, type and the network address it came from), their share links' titles and dates, and the storage they use;
- the files they sync, if they have storage of their own, with the details above;
- their answers to questions in projects they watch, with the time;
- in the organization's Library: what they publish, comment, like, bookmark and follow, as above;
- for broadcasts sent through Lectern: times, destination names and hours used (not the stream keys).
We don't collect a student's date of birth, age, grade, student ID number, address, phone number, demographics, grades, health or special-education records, location beyond the network address, or biometric data. Nothing recognizes faces or voices in our cloud; captions are made on the device. What a student records and writes stays on the device unless they sync it or upload it to share. The services that handle it are the ones listed above; the speech model's download from our server, and the crash reports a student may choose to send, carry no student data.
We'll tell a school within 30 days of determining that its students' data was breached.
Changes
We'll post changes here and, if they matter, email account holders before they apply. Questions about privacy: support@lecternvideo.com, or write to Lectern Video LLC, PO Box 4001, Bartonville, IL 61607.
Lectern is made by Lectern Video LLC, PO Box 4001, Bartonville, IL 61607. Questions about this page: hello@lecternvideo.com.