Back to PingMeet

Privacy Policy

Last updated: September 2026

Your privacy matters. PingMeet is designed with privacy-first principles. All your data stays in your browser - we don't operate any servers that collect or store your information.

Data We Access

Data Type Purpose Storage
Calendar Events Display meetings & send reminders Local Only
OAuth Tokens Authenticate with Google/Microsoft Local Only
Email Address Display connected account Local Only
Meeting Duration Track time in meetings Local Only
AI API Keys Generate meeting insights & action items Local Only Optional
Meeting Captions Extract action items after a call Local, then deleted Opt-in
Action Items & Recaps Show what you agreed to in past meetings Local Only Opt-in

Data Storage

All data is stored locally in your browser using Chrome's Storage API. This includes:

We do not have servers that store your data. When you uninstall the extension, all data is automatically deleted.

Automatic deletion

Third-Party Services

PingMeet connects to the following services only when you explicitly connect your calendars:

Your API key goes directly from your browser to the provider you chose. It never passes through us, because there is no “us” in the request path — no PingMeet server is involved.

What We DON'T Do

AI Insights (Optional Feature)

If you choose to enable AI-powered meeting insights:

Meeting Action Items (Optional Feature)

This is the only feature that touches what people actually said. It is off by default, and turning it on is not enough on its own — each meeting must also be approved before anything is read.

When enabled and approved, PingMeet reads the captions the meeting itself is already displaying on Google Meet, Zoom (web) or Microsoft Teams (web), and uses them to extract action items when the call ends.

What this feature does

Your controls

Other people in the meeting

Other participants are not notified by PingMeet that you are extracting action items. Recording and note-taking rules differ by jurisdiction, employer, and platform. You are responsible for having whatever consent or disclosure your situation requires.

What is not supported

The desktop apps for Zoom and Teams cannot be captured — a browser extension has no visibility into them, and no extension can provide this. Only meetings you join in the browser are eligible.

Permissions Explained

Permission Why We Need It
identity OAuth authentication with Google/Microsoft
notifications Show meeting reminder notifications
alarms Schedule reminders at the right time
storage Save your settings and calendar data locally
tabs Open meeting links when you click "Join"
offscreen Play reminder sound in background
downloads Export weekly meeting reports
idle Detect a locked or idle screen, so a reminder can be made louder when you are least likely to see it. Reports only active / idle / locked — never what you are doing.
Site access to meet.google.com, zoom.us, teams.microsoft.com Read on-screen captions for action items, and detect that you actually joined. Used only for meetings you approved; nothing is read otherwise.

Google API Services User Data Policy

PingMeet's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Scopes we request, and why

Scope Why PingMeet needs it
calendar.events Read your upcoming events so reminders can fire before a meeting starts, and write the two changes you ask for from the popup: creating an event, and declining an invitation.
calendar.calendarlist.readonly List the calendars on your account so you can choose which ones PingMeet watches. Reads names only, never event contents.
userinfo.email Show which account is connected, so you can tell two accounts apart. Displayed in the extension and never sent anywhere.

Transfers of Google user data

PingMeet operates no servers, so Google Calendar data never reaches infrastructure we control. There is exactly one case in which it leaves your browser: if you turn on the optional AI Insights feature and supply your own API key, event titles, start times, durations and attendee counts for the day are sent from your browser directly to the AI provider you selected, to generate that day's summary. This transfer is off by default, requires a key you provide, and is described in AI Insights above. No other Google user data is transferred to any third party, and none of it is used for advertising, sold, or used to train general-purpose models by us.

Google user data is never read by a human, except where you explicitly ask us for support, where it is required for security purposes, or to comply with applicable law.

Your Rights

You have full control over your data:

Changes to This Policy

We may update this privacy policy from time to time. Any changes will be reflected in the "Last updated" date above.

Contact

If you have questions about this privacy policy or how PingMeet handles your data, please open an issue on our GitHub repository or contact us at:

srewoo@gmail.com