MeetAnnotate AI requires a free account, starting with a 7-day free trial, then a paid subscription (see "Account and Subscription" below for exactly what that involves and why). Your annotations themselves stay local to your browser unless you separately turn on Collaborate, and MeetAnnotate AI includes no analytics, telemetry, or third-party tracking of any kind.
The one exception beyond the account itself is the optional Collaborate feature: if you explicitly turn it on for a meeting, your cursor position, your display name, and what you draw are sent to MeetAnnotate AI's real-time messaging service (InsForge) so other participants who also turn it on can see them live. This only happens while Collaborate is on, and never otherwise. See "Collaborate" below for exactly what that involves.
MeetAnnotate AI adds a drawing overlay (pen, highlighter, shapes, text, laser pointer, etc.) on top of supported video-meeting web apps — Google Meet, the Zoom web client, Microsoft Teams, and Webex — so you can annotate your screen during a call, optionally shared live with other participants who also enable it.
Stay entirely in your browser tab's memory unless you turn on Collaborate (see below). They are never written to disk, and disappear when you close the tab, navigate away, or turn the overlay off. There is no history and no server-side storage of anything you draw, with or without Collaborate on — collaboration is live-only, not persisted.
Stored via the browser's built-in chrome.storage.sync API so your preferences follow
you to your other Chrome installations if you have Chrome Sync enabled. This sync is
Google Chrome's own built-in browser-sync mechanism, governed by your Google Account
and Chrome Sync settings — MeetAnnotate AI's own code never transmits this data anywhere
itself; it only reads and writes it through the browser's local storage API. Your display
name is only ever shown to others when you separately turn on Collaborate.
Stored locally per-tab/per-device via chrome.storage.local and chrome.storage.session.
This data never leaves your device and is not part of Chrome Sync.
Only captured when you explicitly click the Screenshot button or press its keyboard shortcut. The image is composed entirely inside your browser and saved directly to your own Downloads folder via a standard browser download — it is never uploaded or transmitted anywhere, even while Collaborate is on.
MeetAnnotate AI does not read, record, transcribe, or transmit your meeting's own audio, video, or chat, and has no access to your camera. The one exception is the optional Voice Note tool, which uses your microphone when you explicitly use it — see "Voice Note" below for exactly what that involves. Outside of actively using that one tool, MeetAnnotate AI has no microphone access and only draws an overlay on top of the page you're viewing.
Collaborate lets other people in the same meeting, who also turn it on, see your annotations and cursor live. It's a separate, explicit toggle — turning on the overlay itself never turns this on. Collaborate (and the Host Controls, Reactions, and Voice Note sync features that build on it) is only available during your free trial or on the Collaboration subscription tier — the cheaper Annotation tier does not include it. See "Account and Subscription" below for what that involves.
While Collaborate is on, MeetAnnotate AI sends to its InsForge project:
While Collaborate is off (the default), none of this is sent anywhere.
How "meetings" are kept separate: a scrambled (hashed) version of your meeting's URL is used to group participants into the same private channel, so unrelated meetings don't see each other's drawings. Important limitation: this channel currently has no login or access control — anyone who has the extension installed and learns your meeting link (for example, if it was shared somewhere you didn't expect) could technically join that same channel and view the shared annotations for that meeting, without needing to actually be in the video call. Don't rely on Collaborate for sensitive or confidential drawing content. This is a known limitation of the current version; a more secure, authenticated version is planned for a future release.
Nothing is stored: Collaborate is live-only. There's no database of past annotations, no meeting history, and no record kept after everyone disconnects.
Platform support: Collaborate currently only works on Google Meet. It's unavailable (the button is disabled) on Zoom, Teams, and Webex for now.
Host Controls: while collaborating, the first person to turn on Collaborate in a meeting is treated as its "host" for this feature — this is not real Google Meet host data (no such information is available to browser extensions); it's simply whoever connected first, and it automatically passes to the next-longest-connected participant if that person leaves. The host can lock drawing to themselves ("Host Mode"); other participants can then send a request to draw, which includes their display name, and the host can approve or deny it. Like the rest of Collaborate, this enforcement happens in each participant's own browser, not on a server — it is not tamper-proof against a modified copy of the extension, the same limitation already described above for the no-login channel.
An account is required to use MeetAnnotate AI at all — you're prompted to sign in the first time you try to use it. New accounts get a 7-day free trial with full access (local annotation and Collaborate), starting from the moment your account is created. After the trial, continued use requires a paid subscription:
Signing up/in: your email address and password are sent to InsForge to create and authenticate your account. Your password is never seen or stored by MeetAnnotate AI's own code — it's handled entirely by InsForge's authentication system. Email/password sign-up requires verifying your email with a one-time code sent to that address.
Subscribing: clicking a "Subscribe" button opens Stripe's own hosted checkout page in a new browser tab. MeetAnnotate AI never sees or handles your card details — that page, payment processing, and ongoing billing are handled entirely by Stripe. MeetAnnotate AI only ever learns which plan (if any) is currently active on your account, not any payment details. "Manage billing" similarly opens Stripe's own hosted billing portal for changing your payment method, switching plans, or canceling.
What's stored: your account (email, a securely hashed password, and its creation date — used only to calculate your trial period) lives in InsForge's authentication system; a single plan field ("none," "annotation," or "collaboration") tied to your account lives in MeetAnnotate AI's InsForge database, updated automatically when Stripe reports your subscription status changing. No card numbers, billing addresses, or other payment details are ever stored by MeetAnnotate AI or its InsForge project — only by Stripe.
Signing out: clears your local session; your account, trial status, and any subscription remain intact on InsForge/Stripe and you can sign back in at any time.
Voice Note is a hands-free annotation tool: click to place it, then speak, and your words appear as text (with common spoken math terms like "alpha" or "squared" converted to symbols like α or ²).
Whenever you use this specific tool, your spoken audio is sent to Google's own built-in Chrome speech-recognition service so it can be turned into text. This is a standard part of Chrome itself (the same underlying service behind Chrome's other built-in dictation features) — MeetAnnotate AI does not operate, see, or store the audio itself; it only receives the transcribed text back from Chrome. This happens every time you use the Voice Note tool, regardless of whether Collaborate is on.
This is independent of Collaborate: the transcribed text is only sent to other meeting participants if you have also separately turned on Collaborate — in that case it's shared the same way any other annotation is (see "Collaborate" above). With Collaborate off, a Voice Note stays local to your own browser tab, like any other annotation.
Outside of actively placing and speaking into a Voice Note, MeetAnnotate AI has no microphone access at all.
| Permission | Why it's needed |
|---|---|
storage |
Save your preferences and session state locally (and sync preferences via Chrome's own sync), as described above. |
| Host access to meet.google.com, zoom.us, teams.microsoft.com, teams.live.com, webex.com | Required so the drawing overlay can be injected into those specific pages, and nowhere else. MeetAnnotate AI cannot see or act on any other website. |
| Host access to MeetAnnotate AI's own InsForge project | Required for account sign-in and subscription billing (needed to use the extension at all), and for the optional Collaborate feature's real-time connection. |
No other permissions are requested. If a future version adds a permission (for example, for planned AI features described in the product roadmap), this policy will be updated to disclose exactly what it's for before that version is released.
MeetAnnotate AI uses three third-party services:
No analytics, ad network, or tracking provider of any kind is used anywhere in the extension.
MeetAnnotate AI does not knowingly collect any information from anyone, including children. Because an account is required to use the extension, it is not intended for use by children who cannot create their own account per InsForge's and Stripe's own terms of service.
If a future version changes what data is collected or how (for example, adding persistence, authentication, or timer-based/co-host permissions to Collaborate), this policy will be updated and the update will be reflected in the extension's Chrome Web Store listing before that version is published.
Questions about this policy can be sent to: meawpong2008@gmail.com