← BarMeetExt home

Privacy Policy — BarMeetExt (BarMeet)

Last updated: 20 October 2026

This policy describes how the BarMeet Chrome extension (Google OAuth application name: BarMeetExt) handles information when you use the extension. This page is public; you do not need to sign in to read it.

Who we are

BarMeet is published as a Chrome extension. The developer contact email shown on the Chrome Web Store listing and on the Google Cloud OAuth consent screen is the primary contact for privacy questions.

Summary

Google API scopes

When you connect, BarMeet requests the OAuth scope https://www.googleapis.com/auth/calendar (Google Calendar). That scope allows the extension to:

BarMeet does not request Gmail, Drive, Contacts, or other Google APIs.

Information accessed and how it is used

Data Purpose Where it goes
Google account identifier (email / profile from OAuth) Show that you are connected; sign out and token revoke Used only in the extension; not sent to a BarMeet backend
Calendar events (title, start/end, links, attendees if present on the event) Display meetings, join links, reminders; create/update/delete when you ask Fetched from Google Calendar API; held in extension memory while in use; not uploaded to our servers
OAuth access tokens Authenticate Calendar API requests Managed by Chrome Identity on your device
Extension settings (durations, reminder toggles, etc.) Remember your preferences chrome.storage on your device

Data retention

Calendar event content is not persisted on BarMeet servers. Cached data in the extension is refreshed from Google and cleared when you sign out or remove the extension. OAuth tokens remain until you sign out, revoke access in your Google Account, or uninstall the extension.

Data we do not collect

BarMeet does not intentionally collect or upload:

Sharing and disclosure

BarMeet does not sell or share your personal information with third parties for their marketing. Calendar requests are sent only to Google (Calendar API) under Google’s terms and your consent. We do not transfer Google user data to other services except as needed to provide the extension features you trigger (for example, opening a Meet URL in a new tab).

Google API Services User Data Policy

BarMeet’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, Google user data is used only to provide or improve user-facing features of BarMeet, is not used for serving ads, and is not sold to third parties.

Third-party services

Authentication and calendar operations use Google (OAuth and Google Calendar API). See Google’s Privacy Policy. Distribution is via the Chrome Web Store (Google).

Security

Communication with Google uses HTTPS. Because there is no BarMeet backend database, your calendar is not stored on our infrastructure. You are responsible for securing access to your Google Account and device.

Your choices and rights

Depending on where you live, you may have rights to access, correct, or delete personal data. Because BarMeet does not host your calendar data, exercising those rights for calendar content is primarily done through Google Calendar and your Google Account.

Children

BarMeet is not directed at children under 13 (or the applicable age in your region).

Changes

We may update this policy when the extension changes. The “Last updated” date at the top will change when we do. Material changes may also be noted in Chrome Web Store release notes.

Contact

For privacy questions, use the developer contact email on the Chrome Web Store listing for BarMeet or the support email on the Google Cloud OAuth consent screen for BarMeetExt.


Application home · Markdown version