Meeting Voice
Recorder

PRIVACY POLICY

Privacy policy

Publisher: Mohammad Tootia

Privacy contact: mohammad.toot@gmail.com

Effective date: 2026-10-05

This policy covers Meeting Voice Recorder extension version 0.16.1 and its website at meeting-voice-recorder.vercel.app. Optional extension usage analytics described below are introduced in 0.16.1; version 0.16.0 has no extension usage tracking. The extension helps you record meeting audio, take timestamped notes, revisit recordings, and optionally request transcripts and meeting minutes. Opening a meeting page or the extension does not start recording; you must choose Start recording.

Information the extension handles locally

The extension handles audio you record or import, meeting titles, timestamped notes, transcripts, summaries, provider API keys, provider/model choices, custom summary instructions, note-direction preferences, and temporary recording state.

Recordings and related content are stored in this Chrome profile's local extension database (IndexedDB). API keys and settings use local Chrome storage restricted to trusted extension contexts. Temporary recording state uses Chrome session storage. A meeting-offer dismissal flag may also be stored in the meeting page's session storage. The extension does not synchronize recordings or credentials through Chrome Sync.

Audio, voices, titles and notes can contain names or other personal or sensitive information discussed in a meeting. The extension does not filter such information out. Obtain participants' permission and follow the rules that apply to your meeting before recording or sharing it.

Meeting-page access and microphone behavior

On listed Google Meet, Jitsi Meet and 8x8 sites, the automatic meeting-offer script examines hostnames and meeting-related page elements. For other self-hosted Jitsi meetings, invoking the toolbar grants temporary access to your selected tab. The extension reads that tab's title and URL to identify the source and suggest a title, and uses supported meeting controls to determine microphone mute state. It does not maintain a general browsing-history database.

In meeting-tab mode, tab audio and the extension microphone are separate sources. The extension microphone is excluded from the recorded mix while the supported meeting reports muted, or when an unmuted state cannot be confirmed. Chrome may still request microphone permission or show a device-access indicator. Unsupported controls, website changes and cross-origin embedded meetings can leave your own unmuted voice excluded. Freeform microphone recording uses the selected microphone directly and does not follow a meeting's mute button.

Required site access also includes the listed AI-chat attachment destinations and provider API hosts. Access to those sites is not limited to the moment recording starts.

When you choose to share with an AI service

Local recording, importing, note-taking, playback and exports do not contact an AI provider. The extension has no developer-operated meeting-audio upload server. Optional usage analytics are separate from meeting content and are described below.

Choosing and confirming a Library transcription or summary action sends relevant information directly over HTTPS to the chosen service, using the API key you configured:

Returned transcripts and summaries are stored locally. OpenRouter may forward requests to downstream model providers. Provider fees, retention, access, human review and training/data-use practices depend on the provider and your account configuration. We do not promise zero retention or that providers will never use submitted content for training. Review the destination's policy before sharing sensitive content: Google, OpenAI, Anthropic, and OpenRouter.

Optional website accounts and hosting

The extension's current local features do not require a website account. The optional Account page sends the email address you enter to Supabase Auth to request a sign-in link. Supabase handles account identity and authentication; the account service stores feature-entitlement records and returns your own account's access status. This browser stores session tokens in local storage to keep you signed in. Signing out removes this browser's local session; it does not delete your account.

The website does not read or upload your extension recordings, notes, transcripts, summaries or provider API keys. Managed AI, team sharing, cloud backup, payment checkout and billing are not active features in this version. Creating or signing into an account does not start a paid subscription.

The website is hosted by Vercel, and its account service uses Supabase. Those providers may process ordinary request, access and security logs as part of operating their services. Website analytics are described below; the website has no meeting-audio upload feature. See Vercel's privacy policy and Supabase's privacy policy. Account availability and email delivery depend on the current service configuration.

Optional extension usage analytics

Starting in 0.16.1, Settings includes an optional usage analytics control, off by default. Recording and all other core features work without enabling it. Enabling it requests Chrome permission to contact the narrow PostHog EU ingestion host (https://eu.i.posthog.com/*). No analytics requests are sent without both your consent and that permission.

If enabled, the extension sends a small set of events to our PostHog EU project: active installation on a day, recording saved, audio export completed, and meeting summary completed. Events contain a randomly generated installation identifier, extension version, event time, and only allowlisted coarse source or completion status where relevant. Counts represent consenting browser installations, not an exact count of people; imports, incomplete captures, and failed actions are not presented as successful meetings.

The analytics payload does not include meeting audio, voices, notes, transcripts, summaries, meeting titles, tab URLs, filenames, recording identifiers, provider API keys, account emails, custom prompts, or raw errors. We do not use automatic interaction capture, session replay, screen recording, or analytics cookies in the extension. We do not link the random identifier to your website account or AI account. This identifier is pseudonymous rather than a guarantee of anonymity.

PostHog necessarily receives ordinary connection metadata such as the request IP address and browser request headers to operate the service. The project is configured to anonymize IP addresses and the client disables geographic enrichment. Analytics are used to understand and improve the extension's stated features. See PostHog's privacy policy for its service practices.

Turning usage analytics off stops future analytics requests, aborts requests still in progress where possible, and removes the local analytics identifier and daily activity state. There is no persistent analytics queue or automatic retry. Requests already received by PostHog cannot be recalled by this toggle. Received events remain under the project's and provider's retention settings; contact the privacy address above to request information or deletion. A new identifier is created if you later enable analytics again. Analytics failures do not prevent recording or saving.

Website visits and store statistics

The public website uses Vercel Web Analytics to count page views and approximate visitors on the production Home and Privacy pages. It uses no analytics cookies or permanent cross-site identifier. Vercel processes page paths, safe referrers, and basic browser, operating system, device, and location information for aggregate reports. We remove URL query strings and fragments before sending page views and skip tracking if the incoming referrer could contain private paths or credentials. The Account page and sign-in callback are excluded; form contents, emails, and authentication tokens are not tracked. Browsers signaling Do Not Track or Global Privacy Control are excluded. Content blockers and these exclusions can reduce the reported counts. See Vercel Web Analytics privacy information.

Chrome Web Store provides its own aggregate installation, uninstallation, and listing-discovery reports under Google's policies. These installation reports do not tell us whether someone recorded a meeting or used a feature. They are separate from the optional extension events and website visits.

How information is used

Information handled through Chrome permissions is used for the extension's stated meeting-recording, timestamped-note, local-library, export, transcription and meeting-summary features, and consented content-free usage analytics to improve those features. Website account information is used for sign-in, security and displaying your feature access. Website visit reports help us understand the public website's reach.

We do not sell this information, use or transfer it for personalized advertising, use it for unrelated profiling, or use it for creditworthiness or lending decisions. Transfers of extension content occur for the user-chosen features described above. The developer does not routinely receive or read your meeting recordings. If you voluntarily provide information for support, it is used to address your request. Information may also be used or disclosed when necessary for security or to comply with applicable law.

Meeting Voice Recorder's use and transfer of information received through Chrome permissions follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Retention, deletion and your controls

Local recordings and related content remain until you delete them or remove/clear the extension's storage. Library Delete removes the selected recording and linked local notes, transcripts and summaries. Settings lets you remove provider API keys. Uninstalling the extension or clearing the Chrome profile can remove local data. Export important recordings; local storage is not a backup.

Downloads, backups and copies sent to external services are separate. Deleting a local recording does not remove them. The extension does not currently request deletion of Gemini Files API uploads after processing. Use the destination service's retention and deletion controls for information you sent there.

Website account information remains until account deletion is arranged. Contact us using the privacy contact above to request deletion or ask about your account information. There is no self-service account-deletion button in the current website. Hosting/service logs and backups can be retained under the relevant provider's policies; signing out or clearing browser storage does not delete them.

Meeting audio is saved incrementally. Closing the captured meeting tab attempts to finalize a partial recording; restarting after a shutdown can recover previously saved chunks. A complete file, the last unsaved audio or continued recording after Chrome exits is not guaranteed. Closing the side panel is different from closing Chrome: background meeting capture can continue. Freeform recording depends on its recording page remaining open. Use Stop & save whenever possible.

Credentials and security

Provider API keys are stored locally and sent to the chosen provider for authentication. Some Google requests include the key in the HTTPS request URL; other services use request headers. The extension does not add its own encryption layer to local keys, audio or notes. Anyone with sufficient access to your browser profile or device may be able to access them.

Protect your device, use dedicated restricted keys where available, and revoke exposed credentials. Do not include keys, private meeting audio or participant details in public support issues. Provider/network error messages can appear in the interface or local developer console; review and redact diagnostics before sharing them.

Pricing and policy changes

All current extension features are free. Optional AI processing uses your own provider account and can incur separate provider fees. Optional paid features or services may be introduced later. Changes to pricing or information handling will be announced and reflected in this policy and product disclosures before those changes ship. This policy does not promise that all future features will remain free.

Contact

For privacy questions, account deletion, concerns about this policy or non-sensitive product support, contact mohammad.toot@gmail.com. Do not send private recordings, participant details or API keys in a support message.

Independent project; not affiliated with or endorsed by Google, Jitsi, Vercel, Supabase, PostHog or the configured AI providers. Their websites, accounts, services and privacy practices are governed by their own policies.