Privacy.
Last updated · May 2026
What MeetMate reads.
MeetMate is a Chrome extension that runs on Google Meet and the Zoom Web Client. It reads the caption track those platforms already render on the page so it can produce short reply suggestions during a live meeting. MeetMate does not record audio, video, or your screen, and it does not capture anything outside of the meeting tab.
Where your data lives.
- Live transcripts for the current meeting are stored in
chrome.storage.session, which Chrome wipes automatically when you close the browser window. - Saved meetings (transcript + AI summary) are stored in
chrome.storage.localon your device. They live there until you delete them or clear extension storage. The history is capped at 50 records and the oldest entries auto-prune. - Settings — personas, keyboard binding, toggles — live in
chrome.storage.local. - Daily-quota counter lives in a cookie on
nexai.newdev.netso re-installing the extension cannot reset the cap. See the Cookies section below for details.
What leaves your machine.
When MeetMate asks for a reply, the most recent utterance plus the rolling transcript of the active meeting is sent to NexAI — an OpenAI-compatible language-model proxy hosted at nexai.newdev.net — for a single completion. The same endpoint is used for the optional save-on-leave summary call. Neither MeetMate nor NexAI retains the request body after the response is returned.
No other off-device traffic happens during normal use. Transcripts are never sent to any other server, and saved meetings stay on your device until you choose to export them.
Third-party services.
MeetMate relies on three third-party services to function. Each receives a narrow, purpose-specific slice of data:
- NexAI (
nexai.newdev.net) — the language-model provider. Receives the latest utterance plus the rolling meeting transcript when a reply suggestion or a save-on-leave summary is requested. Requests are not retained server-side. - Firebase Authentication (Google Cloud) — handles Google sign-in. Receives your Google-account email, display name, profile picture URL, and a Firebase user identifier so MeetMate can enforce a per-user daily quota. No other Google data is requested.
- ExtensionPay (
extensionpay.com) — processes Pro subscriptions. Receives your billing email and a paid / unpaid flag. MeetMate never sees your payment card or full billing details.
Account data.
Sign-in is handled by Firebase Authentication using your Google account. MeetMate receives your email address, display name, profile picture URL, and a Firebase user identifier (UID). The UID is used as a stable key for the daily-quota counter. We never receive your Google password or any other Google-account data — no Drive, no Gmail, no Calendar, no Contacts. The OAuth scopes requested are openid, email, and profile only.
Cookies.
MeetMate sets one cookie per signed-in user on nexai.newdev.net:
- Name:
mm_quota_<firebaseUid> - Path:
/__mm_quota__— the cookie is path-scoped so it is never sent on regular API calls to NexAI. - Value: a JSON object
{ date, consumed }— today's date plus today's suggestion count. No tracking identifier, no cross-site linkage. - Why on a separate domain: Chrome wipes extension storage when the user uninstalls. A cookie on a domain we operate survives uninstall + reinstall, which is the only way to keep the free-tier 200/day cap honest.
- Lifetime: 90 days.
Subscription billing.
Payments for Pro are processed by ExtensionPay. MeetMatereceives a paid-or-unpaid flag and your billing email; we never see your payment card. Cancellation is handled inside ExtensionPay; access continues until the end of the current billing period.
Data MeetMate does not collect.
- No audio or video. MeetMate only reads the caption text the meeting platform itself renders. Your microphone and camera are never accessed.
- No screen capture. MeetMate does not read the rest of your screen, other tabs, or any application outside of Meet and Zoom.
- No browsing history. MeetMate does not track which sites you visit. The
tabspermission is used only to detect when a meeting tab closes, so the in-flight AI request can be aborted. - No payment information. Card details and billing addresses are handled by ExtensionPay; MeetMate never receives them.
- No analytics or tracking pixels. MeetMate does not embed Google Analytics, Mixpanel, or any other third-party analytics SDK in the extension.
Contact.
Questions about this policy: email nguyentienm@gmail.com.