LiveScribe
Effective August 10, 2026

Privacy, in plain language.

LiveScribe captures captions only after you start it. It does not join meetings as a bot and does not record meeting audio.

Data LiveScribe handles

LiveScribe may handle meeting captions, speaker names supplied by the meeting platform, meeting page title and URL, transcript highlights, questions entered by the user, generated answers and summaries, and an Anthropic or OpenAI API key if the user chooses that AI option.

Storage and retention

Transcripts, answers, summaries, and meeting metadata are stored in Chrome local extension storage on the user's device. LiveScribe retains up to 50 sessions and allows users to delete sessions from the extension popup. Uninstalling the extension removes its Chrome extension storage.

Optional Anthropic and OpenAI API keys are stored in Chrome local extension storage and are not placed in Chrome sync storage.

AI processing and sharing

AI processing occurs only when the user asks a question, requests a summary, or tests an AI connection.

Local AI companion

The selected transcript content and prompt are sent through Chrome Native Messaging to software installed on the same computer.

Anthropic API

If selected, transcript content, the prompt, and the user-provided API key are sent directly over HTTPS to Anthropic. Anthropic processes that data under its own terms and privacy policy.

OpenAI API

If selected, transcript content, the prompt, and the user-provided API key are sent directly over HTTPS to OpenAI. OpenAI processes that data under its own terms and privacy policy.

LiveScribe does not operate a developer-controlled transcript server. The developer does not sell meeting data, use it for advertising, or permit humans to read it.

Permissions

  • Supported meeting-site access detects meeting routes and reads captions only after user consent.
  • Chrome storage saves settings, transcripts, summaries, and the optional API key.
  • Native Messaging communicates with the separately installed local AI companion.
  • Anthropic and OpenAI host access supports the corresponding optional direct API connection selected by the user.

Security

External API traffic uses HTTPS. Communication with the local companion uses Chrome's Native Messaging channel. Users should protect API keys and meeting transcripts as sensitive information.

Changes and contact

Material changes to these practices will be disclosed in the extension and this policy before new data handling begins. For privacy questions, use the support options on the LiveScribe support page.