Trust centre.

How Second Listen looks after lessons, and what the tool does and does not do.

Last updated 3 November 2026.

Second Listen Governance Pack. The same facts in one document, to share with a data protection officer or governors.

Open the Governance Pack

How a lesson flows

Every lesson takes the same path. Lessons never leave the United Kingdom, and at each step less is kept.

  1. Recorded
    The teacher's own device

    The teacher chooses to record a lesson, or uploads one. They can add a learning intention, success criteria and the class's Curriculum for Excellence level.

    Nothing is kept on the device by Second Listen.

  2. Uploaded
    Supabase storage, United Kingdom

    The audio is uploaded, encrypted in transit, to private storage.

    Kept only until it has been turned into text.

  3. Turned into text
    Microsoft Azure AI Speech, UK South

    The audio is transcribed. Microsoft processes it in memory and stores none of it.

    Our copy of the audio is deleted within seconds.

  4. Names replaced, sensitive content checked
    Second Listen's service, London

    Pupil and staff names become labels such as [Pupil A]. The text is checked for signs of protected or sensitive personal information; if any is found, everything is deleted and nothing is analysed.

    Nothing new.

  5. Read against QI 2.3
    Amazon Bedrock, London

    The labelled text, with the teacher's intention, criteria and level, is read against eight HGIOS 4 QI 2.3 indicators. Zero data retention is switched on.

    Amazon keeps no copy. Our transcript is deleted as soon as the reading is done.

  6. Reflection shown
    Supabase database, United Kingdom

    Up to four moments, each quoting the lesson, with a question and ideas to weigh up.

    Seen by the teacher only. Kept 14 days, or up to six weeks if they plan a next step from it.

What leaders see

School and local authority leaders never see a lesson or a reflection. They see counts across lessons by indicator, shown only once five staff have joined, never by teacher.

Companies we use

CompanyWhat it doesWhat it receivesWhere
SupabaseDatabase and storageEverything we keepUnited Kingdom
VercelRuns the website and serviceRequests as they pass through; nothing keptLondon
Microsoft (Azure AI Speech)Turns lesson audio into textThe lesson audio, processed in memory and not storedUnited Kingdom (UK South)
Amazon Web Services (Amazon Bedrock)Reads the text against the indicatorsThe lesson text with names replaced by labels, and the teacher's intention, criteria and level. Not storedUnited Kingdom (London)
BrevoSends sign-in codes by emailThe work email address and the codeEuropean Economic Area (France and Germany), during the pilot

How long things are kept

DataHow long
Lesson audioSeconds. Deleted as soon as it has been turned into text.
Lesson text (transcript)Deleted as soon as the lesson has been read, usually within a minute or two. Amazon keeps no copy.
Learning intention, success criteria, levelKept with the lesson's moments and removed with them.
The moments from a lesson14 days. Up to six weeks if the teacher plans a next step from that lesson.
Reflective cycles (next steps)Until the teacher deletes them.
Sign-in codesTen minutes to use; deleted after a day. Brevo keeps a log of each email for one month.
Accounts, school membership and rolesWhile the local authority uses Second Listen.
Log of role changes, downloads and authority accessWhile the local authority uses Second Listen.
Approaches saved in the Research ExplorerUntil the teacher removes them, or their account ends. Seen by the teacher only.
Pilot survey answers (if a teacher chooses to answer)Until the pilot has been evaluated, and no longer than 12 months. Seen by Second Listen only, as totals.
Failed sign-in attempts30 days, without storing the network address itself.
Whole-school figuresKept, because they are counts that cannot identify anyone.

A daily job deletes anything past its time. When a local authority stops using Second Listen, we return or delete its data within 30 days and confirm in writing.

The AI model

TranscriptionMicrosoft Azure AI Speech (fast transcription, British English), in UK South. Its confidence scores give the teacher a rating of how clearly the lesson was heard, shown as signal bars on their reflection.
Reading the lessonClaude Sonnet 4.6, a large language model provided by Amazon Web Services through Amazon Bedrock, run in London. Lessons are sent to Amazon Web Services in London only.
Data retentionAmazon Bedrock's zero data retention setting is on for London. Model invocation logging is off.
TrainingNo lesson, reflection or other personal data is used to train any AI model, by us, Amazon Web Services or Microsoft.
What it is givenThe labelled transcript, the eight indicators with what to listen for, worked examples, the bank of teaching approaches, and the teacher's own intention, criteria and level if given.
What it producesUp to four moments, each quoting the lesson, with why it matters, a question, and a few ideas to weigh up. A common thread across the lesson. Fewer moments when a recording is short (at most two, or none): it is never stretched to fill a number.
What it cannot doScore or grade a lesson, judge a teacher, assess a pupil, invent a research source, or show anything to anyone but the teacher.

Checks on every reflection

  • Every indicator must be accounted for; a reflection that misses one is retried rather than shown incomplete.
  • Every quotation is checked against the lesson, word for word. If one cannot be found, the reflection is retried; if it still cannot, that moment is removed.
  • A recording with only about a minute of talk is not read at all: the audio is deleted, nothing is saved, and the teacher is asked to try a longer stretch of teaching.
  • A suggested approach must come from the fixed bank for that indicator; anything else is removed.
  • Ideas that read as a research claim, an instruction, or run too long are removed.
  • Words describing individual pupils' feelings, ability or behaviour are counted and watched (the rules forbid them).
  • Formatting is tidied (for example, em dashes are removed) before the teacher sees anything.

Human oversight

The tool makes no decision about anyone. It offers moments for the teacher to think about; the teacher decides what, if anything, to do next. Every moment quotes the lesson, so the teacher can check it against what they remember. Suggested approaches come only from a fixed, referenced bank, each with its caveats, chosen and checked by people, not generated.

Security and checks

LocationLessons are stored and processed in the United Kingdom, encrypted in transit and at rest.
Sign-inStaff sign in with a six-digit code sent to a work email on the local authority's own domain; it works once, lasts ten minutes and allows five attempts. Only a keyed hash is stored.
AccessRoles are checked on every request. Leaders see counts only, and nothing below five staff.
LoggingRole changes, downloads and every local authority opening of a school's figures are logged.
Less to loseAudio deleted in seconds, transcripts once read, names replaced first, and a daily job deletes anything past its time.
Our accessOnly Second Listen's administrator can reach the database, through accounts protected by multi-factor authentication.
TestedAutomated tests check, on every change, that personal data can reach only the companies listed, in the places listed.

Independent reviews and certifications

ReviewStatus
Independent penetration testPlanned before Second Listen is sold. A summary will be published here.
ICO registration (data protection fee)Registered with the Information Commissioner's Office, reference ZC293582, since 4 November 2026.
Accessibility (WCAG 2.2 AA)Assessment and accessibility statement planned before Second Listen is sold.

If personal data is ever lost or exposed, we tell the local authority straight away and help it decide who else needs to be told, including the Information Commissioner’s Office.

Governance

The local authority is the controller and decides how the data is used. Second Listen Ltd is its processor and acts only on its instructions, under a written data processing agreement.

Things we never do

  • We never sell, rent or share personal data for anyone else's purposes.
  • We never use lessons, reflections or any personal data to train AI models, and we don't allow the companies we use to.
  • We never score, grade or rank a lesson or a teacher.
  • We never show a school or local authority leader a teacher's lessons, reflections, next steps, or whether or how often they use Second Listen.
  • We never assess, profile or make a decision about a pupil.
  • We never put lesson content in an email.

Things we commit to doing

  • We tell the local authority before we add or change a company we use, or change where data is processed.
  • We keep a log of significant changes to how lessons are handled, and share it with the authority’s data protection lead.
  • We help with any request from a teacher, parent or pupil to see, correct or delete their data.
  • We return or delete everything within 30 days if an authority stops using Second Listen.
  • We keep this page and the privacy notice up to date, and date every change.

For buyers

Deployment

  • Runs in a web browser on a computer, tablet or phone. Nothing to install.
  • Records with the device’s own microphone, or takes an uploaded recording.
  • Staff sign in with their work email on the authority’s own domain. Sign-in emails come from Second Listen, so they should be allowed through email filters.
  • No connection to school management systems, and no pupil accounts or pupil records.

Procurement

  • Licensed to a whole local authority, covering every school and teacher in it.
  • Pilot schools from January 2027 have a free pilot term.
  • On request: a data processing agreement, the Governance Pack, and help with your own data protection impact assessment.

Support

Something we haven’t covered?

Ask us directly. We’re happy to talk it through with you or your data protection team.

Ask a question