Legal Updated 20 November 2026
Privacy policy
This policy says what Lectern stores, why, who handles it, how long it stays, and what you can do about it. We have tried to say it in plain words.
Who runs Lectern
The operator named below runs Lectern and decides how it uses your data. Write to us with any question or request about your data.
- Name
- Oddur Sigurdsson
- Post
- 228 Park Ave S PMB 564444, New York, NY 10003-1502
- [email protected]
What we store
You can browse, watch, save lectures and write notes without an account. Those things stay in your browser. If you make an account, we store this:
- Your email address, and a name once you add one. We ask for the name when you first post a comment, a review or a public playlist. An affiliation and short bio, if you add them.
- The languages you tell us you speak, if you answer. We keep the list and use it to decide what to bring you as the library grows. Today it changes nothing you see.
- A hash of your password (scrypt). We never store the password itself.
- A two-factor secret and recovery codes, if you turn on two-factor sign-in.
- For each sign-in session: the IP address and the browser user agent. Security events, such as a password change, are stored with the same two details.
- Your library (saved lectures, progress and notes) and your saved books, which sync from your browser to your account while you are signed in. For each saved book we keep its slug and the time you saved it. When you remove a book, we keep the slug and the time of the removal for 90 days, so that your other devices do not save it again.
- Your comments, book reviews and playlists, and any moderation strikes on your account.
- Support cases you send: your name, email address and IP address, and what you wrote.
- A copy of each email we send you, kept for 180 days.
- The version of the terms you accepted, and when you accepted it.
- Your answer about the monthly digest and course spotlights, with its time and where you gave it.
When you follow a book link, we record the click with your IP address and browser user agent. The link then opens the book on Amazon. It carries no affiliate tag, and Lectern earns nothing from it. We keep play counts for each lecture, and counts of the plays that passed ten minutes or reached the end. These hold no reader data. We also keep server telemetry for 7 days: traces of the work the server does.
Why we use each kind of data
The law asks for a legal basis for each use of personal data. This table gives the basis for each use.
| Data | Purpose | Legal basis |
|---|---|---|
| Email address, password hash, name, two-factor secret, and each session with its IP address and browser user agent. | To create your account and to sign you in. | Contract: the account you asked for. |
| Library, notes, progress, saved books, playlists, pinned lectures and the layout of the lecture panel. | To keep your library and settings the same on every device where you sign in. | Contract. |
| The languages you say you speak. | To decide which lectures to add as the library grows. | Legitimate interests: a library that readers can use in their own languages. |
| Comments, book reviews and public playlists, with your name. | To show what you post to other readers. | Contract. |
| Lectures you suggest, with your account id. | To review the suggestion and, if you ask, to tell you the result. | Contract. |
| The text of comments and reviews, your strikes and standing, how many comments you just posted, and how much of the lecture you watched. | To keep comments and reviews within the community rules: automatic checks that include a language model, strikes, and the suspension of an account. | Legitimate interests: a site that is safe for readers. Legal obligation, where the law requires us to act on unlawful content. |
| Support cases and takedown notices: your name, email address, IP address and what you wrote. A formal notice also holds your postal address, telephone number and signature. | To answer you, to act on a notice, and to keep a record of the case. | Legitimate interests: answering readers and keeping a record of what we did. Legal obligation, for copyright notices and notices about unlawful content. |
| Book-link clicks: the book, the page, your account id if you are signed in, your IP address and your browser user agent. | To count clicks on book links, without repeat clicks and bursts. | Legitimate interests: knowing which book links readers use, and a count that abuse does not distort. |
| Email about your account: sign-in, password, security, notices about your comments, support, and notices of new terms. | To run your account and to tell you what you need to know about it. | Contract. |
| A copy of each email we send, with its recipient, for 180 days. | To answer a question about an email, and to show what we sent. | Legitimate interests: support, and proof of what we sent. |
| Your email address, and your answer to the monthly digest and course spotlights with its time and where you gave it. | To send the marketing email you chose. | Consent. You can withdraw it at any time. |
| Product analytics kept in memory only: page views, clicks, performance, errors, search terms, and your account id when you are signed in. | To learn how the site is used and where it fails. | Legitimate interests: a site that works. |
| Analytics storage: a random identifier in a cookie or in local storage. | To recognise a browser that returns. | Consent, where we ask for your choice. Elsewhere, legitimate interests: knowing how readers return to the site. You can say no at any time. |
| Ad-click measurement: the click identifier and the cookies listed above. | To learn which of our ads lead to people watching lectures. | Consent, where we ask for your choice. Elsewhere, legitimate interests: knowing which of our ads bring readers. You can say no at any time. |
| Rate-limit counters, security events and server telemetry. | To protect accounts and the site from attack and abuse, and to find faults. | Legitimate interests: the security of the site and of your account. |
| The version of the terms you accepted, and the time. | To show that you agreed to the terms in force. | Legitimate interests: proof of agreement. |
| A question you type in a lecture's Ask box. | To write an answer from the lecture. | Contract: the feature you asked for. |
What you must give us
To make an account, you must give an email address and a password. Without them we cannot make the account. Everything else is optional: a name, an affiliation, a bio, your languages and your email choices.
You must add a name before you post a comment, a review or a public playlist, because other readers see it. A guest gives us no personal data, apart from what every visit sends, such as the IP address.
Analytics and your choices
We measure how the site is used, how fast pages load and where errors happen in our own database. No other service receives this data, and we do not record sessions as video. Event rows in our database are kept 90 days (daily totals without identifiers are kept), and error reports 30 days. If you are signed in and your choice allows analytics storage, events carry your account id only, never your name or email address.
How your choice works:
- We ask for your choice when the network reports that you are in the European Economic Area, the United Kingdom or Switzerland. If the network reports no country, we use your device's time zone, and when that is also unknown we ask.
- Where we ask, we use no analytics storage and no ad-measurement cookies until you say yes.
- A browser that sends Global Privacy Control or Do Not Track is treated as a No everywhere, and we show no question.
- Before a Yes where we ask, and after a No anywhere, analytics runs without cookies or stored identifiers. It keeps what it needs in memory only, and we set no ad-measurement cookies.
- Elsewhere, we do not ask. Analytics storage and ad measurement are on until you say no. You can change your choice at any time under Privacy choices in the footer.
Ads. We run Google ads. When you arrive from one, the address carries a click identifier. If your choice allows ad measurement, we store that identifier, the time of the click, the page you landed on, which of our ad groups the ad came from, your country when our host reports it, the kind of device (desktop, mobile, tablet or unknown, read from your browser and never stored as the browser's own text), how many times that identifier reached us, and a random key in a cookie for 90 days. If an ad address carries an identifier that is not valid, we keep only its length, which kinds of characters it holds, the page and the time, never the value. We use it to learn which ads lead to people watching lectures. When that visitor plays three minutes of a lecture, opens a book link or creates an account within 30 days of the click, or returns on another day within 7 days, we record it against the click and report that conversion to Google. The report holds the click identifier, the kind of action, its time and a number for its worth. It holds no name, email address or account id. A visit that does not come from an ad stores none of this.
YouTube
Lectern uses YouTube API Services. The video player comes from YouTube's privacy-enhanced domain, youtube-nocookie.com, and the script that controls it comes from www.youtube.com. The player loads with the lecture page, so your browser connects to YouTube when the page opens. YouTube may set its own storage when a video plays.
The YouTube Terms of Service apply to the videos and the player. YouTube's handling of your data is covered by the Google Privacy Policy .
Lecture stills, the small pictures on cards and pages, load from YouTube's image servers at i.ytimg.com. We keep no copy. Your browser asks Google for each still, so Google receives your IP address with the request.
Text we send to language models
Some features send text to a language model. We send only this:
- Comments and book reviews, to check them against the community rules. The comment check also sees a little context: the account's role, its strike count, how many comments it just posted, and how much of the lecture it watched.
- The subject and text of a support request, and its details, to sort it for the person who answers it.
- A question you type in a lecture's Ask box, with excerpts from that lecture, to write an answer.
Models run at Google (Gemini) and OpenRouter. We do not add your name or email address to this text. Words you write yourself may contain them.
Automatic decisions
Comments and book reviews pass automatic checks: fixed rules when you post, then a language model. A check can hold or hide a comment or a review, and can add a strike to the account. When a reader reports a comment, a language model can decide the report. A language model can also decide an appeal about strikes: it can restore your standing or keep it.
A person decides every suspension, and every appeal about a suspension. If you disagree with an automatic decision, write to [email protected]. Post: 228 Park Ave S PMB 564444, New York, NY 10003-1502, and a person reads it. No decision with a legal effect on you is made by a machine alone. The community rules say how the checks work.
Who handles data for us
We do not sell personal data. These companies handle data on our behalf.
| Company | For | Data | Where | Safeguard for transfers |
|---|---|---|---|---|
| Railway | Hosting and the database. | All the data this policy lists. | United States | The EU standard contractual clauses in Railway's data processing terms. Railway is also certified under the EU–US Data Privacy Framework. |
| Cloudflare | Network and caching in front of the site. | Every request to the site, including IP addresses. | Worldwide network | The EU standard contractual clauses in Cloudflare's data processing terms. Cloudflare is also certified under the EU–US Data Privacy Framework. |
| Resend | Sending email. | Your email address and the message. | United States | The EU standard contractual clauses in Resend's data processing terms. |
| The YouTube player, the lecture stills and the data API, the Gemini language models, and Google Ads conversion measurement. | Video and still-image requests from your browser, with your IP address; text sent to Gemini; a conversion report for an ad click. | United States and other countries | Google LLC is certified under the EU–US Data Privacy Framework. | |
| OpenRouter | Routes text to language models for editorial writing and checks. | Text sent to a model. The privacy policy says what. | United States | The EU standard contractual clauses in OpenRouter's data processing terms. |
| Amazon | Book links. A book link opens the book on Amazon. Lectern attaches no affiliate tag and earns nothing from it. | Your browser connects to Amazon when you follow a book link. | United States | Amazon.com, Inc. is certified under the EU–US Data Privacy Framework. |
Every one of these companies is in the United States or runs a network around the world. For a reader in the European Economic Area, the United Kingdom or Switzerland, this means that your data leaves your region. The last column names the safeguard that each company's own terms state for such a transfer. Write to us for a copy of the safeguards.
How long we keep it
| What | How long |
|---|---|
| Account, sessions, security events, library, playlists, comments, reviews, strikes, your email choices and the terms version you accepted | Until you delete the account. A session also ends when it expires or when you sign out. |
| Record of each lecture you submit, with our decision | Until you delete your account. |
| Copies of your notes and progress that a catalogue merge keeps so the merge can be undone | For 90 days after the merge, or until you delete the account. |
| Copy of each email we send, with its recipient | 180 days, then deleted. |
| Server telemetry (traces of the work the server does) | 7 days. |
| First-party analytics event rows | 90 days, then deleted. Daily totals without identifiers are kept. Deleting your account removes the link to you. |
| Client and server error reports | 30 days after the error was last seen. |
| Rate-limit counters: a network address or a hashed sign-in address, with a count of attempts | 2 hours after the counter's window ends. The longest window is one day. |
| Support cases and takedown notices | With no fixed end, so that we can answer a later question about the case. Deleting your account removes the link to you and the IP address. The text and the email address you gave stay. |
| Book-link click rows | With no fixed end, so that we can count clicks over time. Deleting your account removes the link to you and the IP address. The browser user agent stays, and a click made while signed out keeps its IP address. |
| Ad-click rows | 13 months, then deleted. They never held an account id. |
Your rights and choices
You have these rights over your personal data:
- Access: ask what we hold about you, and get a copy. The Account page exports everything we store about your account as Markdown or JSON.
- Correction: change your name, email address and profile on the Account page, or ask us to correct anything else.
- Deletion: delete your account on the Account page. This needs your password. Or ask us to delete data.
- Restriction: ask us to stop using your data while we check a question you raised about it.
- Objection: object to a use that rests on our legitimate interests.
- Portability: take your data with you. The export is in Markdown and JSON.
- Withdrawing consent: change your answer at any time under Privacy choices in the footer, and for the monthly digest and course spotlights in your account settings or with the link in each email. A withdrawal does not change what we did before it.
- Complaint: complain to the data protection authority of your country.
To use a right, use the controls on the Account page, or write to [email protected]. Post: 228 Park Ave S PMB 564444, New York, NY 10003-1502. We answer within one month. We may ask you to confirm that the account is yours before we act.
Deleting your account removes the account, its sessions, security events, your library, saved books, playlists, comments, reviews and strikes. Support cases and book-link click rows stay, unlinked from your account and with the IP address removed. Lecture submissions and first-party analytics event rows also stay for their keeping period, unlinked from your account. The copies of emails we sent stay until their 180 days pass. Ad-click rows stay until their 13 months pass. They were never linked to an account.
The export holds your profile, library, notes, saved books, playlists, comments, reviews, your votes on comments, records kept before a catalogue merge, and lectures you submitted. It also holds your sessions and security events, the support cases you sent, your strikes, your book-link clicks, first-party analytics events linked to your account, and the time, kind and subject of each email we sent you. A case you sent while signed out is included once you have confirmed the email address you sent it from. It leaves out secrets: your password hash, two-factor secret, recovery codes and session tokens. It also leaves out the text of our emails, because a reset email holds a live link. Write to us if you want the text of an email we sent you.
The monthly digest and the course spotlights are marketing email. We send them only to a reader who chose them, at sign-up or in account settings. We store your answer, the time you gave it, and whether you gave it at sign-up or in account settings. The link in each of these emails stops it.
Email about your account is service email: sign-in and password messages, notices about your comments, answers to your support cases, and notices of new terms. We send it whatever you chose about marketing email.
Children
Lectern is for a general audience. An account is for people who are at least 13 and old enough to agree to the use of their data in their own country (up to 16 in parts of Europe), or who have a parent's permission. When we learn that an account belongs to a child under 13, we delete it. If you think a child has made an account, write to [email protected]. Post: 228 Park Ave S PMB 564444, New York, NY 10003-1502.
Changes to this policy
When we change this policy, we change the date at the top of the page. The policy describes what the site does on that date.
When we change it in a way that matters, we also tell account holders by email. The next time you are signed in, a notice shows what changed, and you accept the new terms and policy with one button.