Live Classroom Captions — Chrome Extension Last updated: June 2, 2026
Live Classroom Captions ("the extension") is a Chrome extension that provides live speech-to-text captioning with on-screen translation overlays for classroom teaching. This Privacy Policy explains what information the extension accesses, how it is used, and what is and is not stored or transmitted.
Microphone audio. When you start a captioning session, the extension converts your spoken words into text in real time. How that happens depends on the recognition mode you choose in Settings:
In both modes, the extension keeps only the resulting text, never an audio recording.
Caption text for translation. When you enable target languages, the extension sends the transcribed caption text to Google Translate's public translation endpoint so the captions can be displayed in those languages for students. Only the caption text itself is sent — no microphone audio, account information, or other personal data is included in translation requests.
Room Sharing (only if you enable it). Room Sharing lets students see your live captions on their own devices. It runs on a free Google Firebase project that you create and control; there is no developer-run server involved. When Room Sharing is on, the extension writes your caption text and its translations to your Firebase Realtime Database so the students who joined your class can read them live. Students join with a code you share and connect using anonymous Firebase sign-in — no student login or account is required. For each connected device the extension stores only an anonymous identifier and recent "last seen" timestamps so you can see how many students are reading; it does not collect student names, email addresses, or any other personal information. Caption data in a room is short-lived and is cleared when the session ends or the room expires. Because the Firebase project is yours, the data there is governed by your own Google account and Firebase's terms.
Your OpenAI API key (only if you use AI Mode). If you choose AI Mode, the API key you enter is stored only in your browser's local extension storage on your own computer. It is sent only to OpenAI to authenticate your own transcription requests, and is never transmitted to the developer or anyone else.
Your Google Drive (only if you enable transcript saving). If you choose to enable transcript saving, the extension requests permission to access your Google Drive using the drive.file OAuth scope. This scope grants the extension access only to files the extension itself creates. The extension cannot read, modify, or see any of your other Google Drive files. When transcript saving is enabled, the extension automatically creates a folder named "Live Classroom Captions Transcripts" in your Drive and saves your session transcripts there as Google Docs. You can move, rename, or delete this folder at any time; if it is removed, the extension simply creates it again. When you connect Drive, the extension also reads the email address of the Google account you connect (using the userinfo.email permission) so it can show you which account transcripts are being saved to. It does not read your email messages or any other Google data.
The active browser tab. The extension injects content scripts into the tab you are viewing in order to display caption overlay boxes on the page. It reads no page content; the overlay is drawn on top of whatever page you are presenting.
On your computer. Your settings (preferred languages, caption box positions, styling preferences, chemistry vocabulary lists, etc.), any class join codes you save, and — if you use AI Mode — your OpenAI API key are stored in Chrome's local extension storage on your own computer. Transcripts of recent sessions are also stored there until they are either saved to your Drive or deleted by you.
In your Google Drive. If you enable transcript saving, completed transcripts are saved as Google Docs in a folder the extension creates in your Drive (named "Live Classroom Captions Transcripts"). These Docs are owned by your Google account and are subject to your own Drive sharing settings. The extension's developer cannot see or access them.
In your Firebase project (only if Room Sharing is on). When you enable Room Sharing, live caption text and minimal, anonymous connection records (an anonymous device ID and timestamps) are stored temporarily in the Realtime Database of the Firebase project you created. This is your own Google Cloud project; the developer has no access to it, and the data is cleared as rooms end or expire.
Nowhere else. The developer operates no backend server and never receives your data. Apart from the Google services described here (Web Speech, Translate, Drive, and — only if you enable Room Sharing — your own Firebase project) and OpenAI (only if you enable AI Mode, under your own key), your data is not sent to any third-party system.
Depending on the features you use, the extension may rely on the following third-party services:
The extension is designed for use by teachers in classroom settings. It is intended to be operated by adult educators. The extension does not knowingly collect any information from children directly. When Room Sharing is on, students receive your captions on their devices and the extension records only an anonymous connection for each device (no names, email addresses, or logins). Students whose voices may be captured in student-response mode or the accommodation room have their speech transcribed and translated the same way as the teacher's speech: audio is not stored, only the resulting text appears in captions and (if enabled) the saved transcript.
Teachers should follow their school's and district's policies regarding the recording of classroom transcripts. Transcripts may contain student responses, which are educational records subject to FERPA in U.S. schools. The extension provides editing and deletion tools so teachers can review and remove sensitive content before saving.
This Privacy Policy may be updated occasionally as the extension evolves. The "Last updated" date at the top of this page reflects the most recent revision. Material changes affecting how user data is handled will be reflected in the policy before the corresponding changes take effect in the extension.
Questions about this Privacy Policy or the extension's data practices can be sent to:
chris85cool17@gmail.com