An hour of your lecturer’s voice, and what we do with it.

You hand us an hour of a lecture. We transcribe it, turn the transcript into notes, a glossary and questions, and hand all four back. The audio passes through us to be processed; it is not written to our storage, and the finished artifacts are held in your own browser. We do not sell your recordings, and we do not hand them to anyone to train models on.

The rest of this page is the detail behind that paragraph. If you want the handling of one specific recording confirmed in writing before you press record, ask at hi@lectureward.com.

Account details. Your email address, a password hash, and anything optional you choose to add, such as a name or the course a lecture belongs to.

Recordings and what we make from them. Lecture audio reaches our servers in short segments, is passed straight to transcription, and is discarded once the text comes back. The transcript, notes, glossary and questions are returned to your browser and stored there — on your device, under this site’s own storage — rather than in a database of ours.

Operational logs. Technical records needed to run and secure the service: times of access, IP address, browser and device type, errors, and how long a given hour took to process.

Correspondence. Emails you send us, and our replies.

Payment records. Where you pay, our payment provider handles your card details; we see the fact of a payment, not the card.

A lecture recording is not just your voice. It can catch your lecturer, the student next to you, a question someone asked, and whatever was said in the room before the hour started. That is why the recording is held for the single purpose of producing your artifacts and showing them back to you.

If a recording caught something it should not have, delete it — or write to hi@lectureward.com and we will remove it and its artifacts.

Transcribing your recording and producing the four artifacts; keeping them available in your account across devices; running, securing and debugging the service; handling payments where they apply; replying to you; and meeting legal obligations.

We do not build advertising profiles, we do not sell or rent your data, and we do not use the content of your lectures to market to you.

Processing a recording into artifacts and running your account is performance of our contract with you. Security, abuse prevention, debugging and keeping the service running rest on our legitimate interests. Anything beyond that — an optional feature that needs more, for instance — rests on consent you give separately and can withdraw. Some records are kept because the law requires it.

Transcription and note-writing run through OpenRouter, which routes each request to the speech-recognition or language model we have configured, and that model’s provider processes the audio or transcript to answer it. Alongside that we use cloud hosting, error monitoring, email delivery and, where you pay, a payment provider.

They act on our instructions, may process your material only to provide their part of the service, and may not use it for their own purposes. For which models are in use on any given day, and which providers sit behind them, write to hi@lectureward.com and ask — you get names, not a category.

We will disclose material otherwise only where the law requires it, or to protect someone’s safety or our legal rights. We are not in the business of volunteering your lectures to anybody.

Our providers may process data in countries other than the one you study in, including outside the UK and the European Economic Area. Where that happens we rely on the safeguards the law provides for such transfers, such as standard contractual clauses or an adequacy decision. If this matters to your institution, ask at hi@lectureward.com and we will set out the detail for your case.

Audio exists on our side only for the seconds it takes to transcribe a segment. The transcript and the three artifacts made from it live in your browser: clearing this site’s data, or recording over the session, removes them, and nothing of them remains with us to delete.

Operational logs are kept for a limited period for security and debugging. Records we must keep by law — billing records, for example — are kept for the period the law sets.

You can ask for a copy of what we hold about you, export your artifacts, correct anything wrong, delete a recording or your whole account, object to processing based on legitimate interests, ask us to restrict processing, or withdraw a consent you gave.

Write to hi@lectureward.com. We reply within one month, and we will not make you justify a deletion request. If you are unhappy with how we have handled it, you can complain to your data protection authority — in the UK, the Information Commissioner’s Office.

Material is encrypted in transit and at rest, access inside the team is limited to the people who need it to run the service, and credentials are stored hashed. No service is immune; if a breach affects your material we will tell you and the relevant authority as the law requires.

The app uses cookies or equivalent storage to keep you signed in and to remember basic preferences. Where we measure how the site is used, we keep it to aggregate counts rather than tracking individuals across other websites, and anything that needs your consent asks for it first.

Lectureward is for people aged 16 or over. We do not knowingly hold material belonging to anyone younger; if you believe we do, write to hi@lectureward.com and it will be removed.

We can update this page. The date at the top says when, and a change that materially affects what we do with your recordings is notified to account holders rather than quietly published. The terms of use sit alongside this policy.

Access requests, deletion requests, questions about a specific lecture, or a request for our list of processors: hi@lectureward.com.