Meeting Browser Alert

Privacy Policy

Last updated: June 10, 2026

Overview

Meeting Browser Alert helps users notice upcoming meetings directly in the browser. The extension reads events from the connected calendar only to calculate visual alerts and provide quick access to the meeting link.

Data Accessed

When the user connects Google Calendar, the extension may read:

• event title;
• start and end time;
• meeting link, when available;
• basic information needed to identify the meeting platform.

The extension does not request permission to create, edit, or delete events.

How Data Is Used

The data is used to:

• show the next appointment in the popup;
• display a visual alert on open pages;
• open the meeting link when the user clicks Join;
• remind the user when a meeting has already started within the configured window.

Storage

Settings, temporary event cache, dismissed alerts, and preferences stay in the user's browser using chrome.storage.local.

Data Protection

Calendar data is protected through the following mechanisms:

• All processing happens locally inside the user's browser — no calendar data is transmitted to external servers.
• Authentication is handled exclusively through Google's OAuth 2.0 flow via Chrome's built-in chrome.identity API. The extension never sees or stores the user's Google account password.
• OAuth access tokens are managed and stored securely by the Chrome browser, not by the extension itself.
• Temporary event data is stored only in chrome.storage.local, which is sandboxed to the extension and inaccessible to websites or other extensions.
• The extension requests only read-only access to calendar events (https://www.googleapis.com/auth/calendar.readonly), limiting the scope of accessible data to the minimum necessary.

Data Retention and Deletion

Google user data is retained only as long as necessary to display alerts:

• The event cache is temporary and is refreshed periodically; events that have already passed are not retained.
• No calendar data is written to persistent storage beyond the browser's local extension storage (chrome.storage.local).
• The user can delete all Google user data at any time by disconnecting Google Calendar in the extension's options page. This revokes the OAuth token and clears all cached events and preferences.
• Uninstalling the extension permanently removes all locally stored data, including any cached events and settings.
• The extension does not retain any Google user data after the connection is revoked or the extension is uninstalled.

Data Sharing

Meeting Browser Alert does not sell data, does not share data with third parties, does not use analytics, and does not send calendar events to its own servers in this version.

Browser Permissions

The extension uses:

• identity to connect to Google Calendar with OAuth;
• storage to save local preferences;
• alarms to periodically check upcoming meetings;
• tabs to detect whether a meeting link is already open;
• offscreen to play short sound alerts;
• access to https://www.googleapis.com/* to read Google Calendar events;
• content scripts on http and https pages to display the visual alert.

User Control

The user can:

• pause alerts;
• disable sound;
• disable overlay and visual effects;
• change the language;
• dismiss alerts;
• disconnect Google Calendar.

Contact

For privacy questions or support, use the contact channel listed in the Chrome Web Store.