Meeting Notes Agent is a meeting-recording and note-taking tool operated by
Opskitt. This page describes what the Chrome extension and its backend do with
your data. It applies to anyone using the extension, whether under an account
they created themselves or one set up by their organization.
What the extension captures
When you start a recording, the extension captures two audio streams from
your browser tab: the audio playing in the meeting tab (other participants,
via Chrome's tabCapture API) and your own microphone (via
getUserMedia), mixed together into a single audio file. Nothing
is captured unless you explicitly start a recording, and only the tab you
chose to record is touched. While recording, the extension also reads the
participant display names shown on that page and which participant is
highlighted as speaking, so the notes can say who said what. These names and
timings are uploaded to the backend together with the recording and are not
sent to the website or anyone else. The extension does not read other tabs,
page content beyond those names, or your browsing history.
Your account and sign-in
To create an account we collect your email address, your name, and your
company name. You sign in with your email and a password.
Passwords are handled by our authentication provider, Supabase. They are stored there in hashed form. Opskitt's backend receives your password only to check it at sign-in, and never stores or logs it. Supabase also sends the verification and password-reset emails.
Sign-in sessions. After you sign in, the extension holds a session on that computer. The backend stores only a one-way hash of the session tokens. Each session is tied to a randomly generated device identifier and a device description (for example "Chrome on Win32") so that a login is used only on the person's own devices. An account can be signed in on a limited number of devices at once (2 by default); signing in on another one signs out the least recently used.
Sign-in and usage records. We record the time and IP address of sign-ins and uploads, and the recorder name attached to each upload. We use this to keep accounts secure, to detect a login being shared, to prevent abuse, and to measure usage. These records are kept for as long as your account exists.
Older accounts set up before email sign-in may still use an access token. It is stored only as a one-way hash.
What happens to the audio
When a recording ends, the audio file is uploaded over HTTPS to the
service's backend (a Cloudflare Worker, with audio stored in Cloudflare R2
and metadata in Cloudflare D1). From there:
The audio is sent to Deepgram for transcription.
The transcript is sent to Anthropic (Claude) to generate a structured summary.
The summary is emailed to you (and any recipients you specify) via Resend.
Deepgram, Anthropic, Resend, Supabase and Cloudflare are processors acting
on Opskitt's behalf. Your audio and notes are not sold, shared with
advertisers, or used to train third-party models beyond what each
processor's own standard API terms specify.
What's stored, and where
Audio files: Cloudflare R2, scoped to your organization and account.
Meeting metadata and generated notes: Cloudflare D1.
On your computer: the extension keeps your backend URL, notification email, preferences and sign-in session in Chrome's local storage.
Access is limited to your organization's own accounts. There is no
cross-organization data sharing. When paid plans are available, payments will
be handled by a payment processor (Stripe); Opskitt will not store your card
number.
Permissions the extension requests, and why
tabCapture — to record the audio of the meeting tab.
Microphone (via a page permission prompt, not a manifest permission) — to record your own voice, mixed with the tab audio.
activeTab — temporary access to the one tab you choose to record, granted only when you click the extension.
scripting — to run the extension's own bundled script in that tab, when you press Start, that reads participant names and the active speaker. No remote code is loaded.
Host permissions for Zoom, Google Meet and Microsoft Teams — so the extension can recognize those meeting pages and offer to start recording when you join.
Host permission for opskitt.com — to sign in and send recordings to the service.
storage — to remember your backend URL, sign-in session and preferences locally in Chrome.
notifications — to tell you when a recording has finished processing, or when you have been signed out.
downloads — used only as a fallback if the upload to the backend fails, so you don't lose a recording.
offscreen — required by Chrome's Manifest V3 to mix and encode audio outside the service worker.
Your controls
Recording only happens when you click Start in the extension popup — there
is no passive or background recording. You can sign out from the extension's
options page at any time, stop the extension from recording by revoking the
microphone permission, or remove the extension. You can reset your password
from the sign-in page.
To request deletion of your stored audio, notes, or account, use the contact
details below.
Contact
Questions about this policy or your data, or a request to access or delete it: email support@opskitt.com. If your account was set up by your organization, you can also contact its administrator.