Privacy details
Effective 22 August 2026
MeetScribe is local-first. Recordings, transcripts, summaries, meeting details and settings are stored in your browser profile. There is no MeetScribe account database and this site does not install analytics or advertising trackers.
Deployment operator and contacts
This deployment is provided by MeetScribe deployment operator, which is responsible for the deployment configuration and the local-first processing described here. Contact privacy@example.invalid for privacy requests and security@example.invalid for confidential security reports.
What stays on your device
- Recording chunks are journaled to IndexedDB during capture, then assembled into the saved recording.
- Saved recordings, imported files, transcripts, summaries, chat history and meeting metadata remain in IndexedDB until you delete them or clear the site’s browser storage.
- API keys are kept in session storage by default. If you enable “Remember API keys,” they are stored in this browser profile.
Optional processors you control
- Groq transcription: when you request cloud transcription, meeting audio and selected settings are sent directly from your browser to Groq using your key. Review Groq’s privacy policy and the terms attached to your Groq account.
- AI summaries and chat: when requested, transcript text and meeting context are sent to the Groq, OpenAI or custom endpoint selected in Settings. For OpenAI, review OpenAI’s privacy policy. A custom endpoint is governed by that endpoint operator’s terms.
- On-device transcription: the pinned Whisper model is downloaded through MeetScribe’s fixed-purpose Hugging Face relay. Model-file requests contain no recording or transcript content. After the model is cached, transcription runs in your browser.
- Browser live captions: this feature is off by default. If you explicitly enable it, your browser may send microphone audio to its own speech-recognition service. This processing is controlled by the browser vendor and is separate from the selected MeetScribe AI provider.
Retention and deletion
MeetScribe does not set a server-side retention period because it does not upload your saved library to a MeetScribe server. Delete individual recordings from the library or use Settings → Storage → Delete all recordings. Browser cleanup, profile deletion or private-browsing expiration can also remove local data, so export important meetings.
Operational data
Cloudflare may process ordinary web-delivery information such as IP address, request URL and security logs when serving this site or the pinned model relay. MeetScribe does not intentionally put recording content, transcripts or API keys in those URLs or logs. Review Cloudflare’s privacy policy.
Purpose, legal basis and your choices
The operator processes ordinary delivery and security data to provide and protect the service. Recording and local analysis happen at your direction in the browser. Optional provider processing happens only when you select and invoke that provider. The operator must identify the legal basis applicable to its users and jurisdiction; this may include performing a requested service, legitimate interests in operating and securing the deployment, consent where required, or compliance with law.
Depending on your jurisdiction, you may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or review by a privacy regulator. Most meeting content is controlled directly through this browser profile: export or delete recordings in the library, or use Settings → Storage → Delete all recordings. Contact the privacy address above for requests concerning operator-held delivery or support information.
Security and browser support
Use a current Chrome or Edge release for screen capture and verify the browser sharing indicator before recording. Camera, microphone and display access remain subject to browser permission prompts. No browser-only recorder can guarantee recovery after device loss, browser-profile deletion or exhausted disk quota.
Questions
For privacy questions, contact privacy@example.invalid. Report potential vulnerabilities privately to security@example.invalid; do not include recordings, transcripts, API keys or exploit details in public issues. Non-sensitive product feedback may use the MeetScribe GitHub repository.