Skip to content

Instantly share code, notes, and snippets.

@Zainulhassan01
Created February 17, 2026 08:33
Show Gist options
  • Select an option

  • Save Zainulhassan01/a55d9ed441acf11c5c8c3053ecb87505 to your computer and use it in GitHub Desktop.

Select an option

Save Zainulhassan01/a55d9ed441acf11c5c8c3053ecb87505 to your computer and use it in GitHub Desktop.
Privacy Policy for Meeting Copilot Chrome Extension

Privacy Policy for Meeting Copilot Last updated: February 17, 2026

Overview

Meeting Copilot is a Chrome extension that helps you capture action items from Google Meet sessions and integrate with Slack and Jira. We are committed to protecting your privacy.

Data Collection and Storage

What We Collect API Configuration: Your API endpoint URL and authentication token (stored locally in your browser) Meeting Transcripts: Captions from Google Meet sessions (sent to your configured backend server) Action Items: Extracted tasks and commands from meetings (processed by your backend)

Where Data is Stored Locally: Your API token and endpoint configuration are stored in Chrome's local storage on your device only Your Backend Server: Meeting transcripts and action items are sent to YOUR selfhosted backend server (not our servers) No ThirdParty Storage: We do not store any of your data on external servers

How We Use Your Data

Meeting Transcription: Captions are captured from Google Meet and sent to your configured backend AI Processing: Your backend uses AI (OpenAI) to extract action items from transcripts Integration Execution: Action items are sent to Slack and Jira based on your approval

Permissions Explained

storage Why we need it: To save your API endpoint and authentication token locally in your browser.

What we do: Store configuration settings so you don't have to reenter them every time.

activeTab Why we need it: To interact with the current Google Meet tab when you click the extension.

What we do: Access the active tab to capture meeting captions and display the popup interface.

host_permissions (meet.google.com) Why we need it: To access Google Meet pages and capture meeting transcripts.

What we do: Monitor Google Meet captions and extract transcript data during meetings.

ThirdParty Services

Meeting Copilot integrates with the following services (based on your configuration):

  1. Your Backend Server: All meeting data is sent to your selfhosted Rails application
  2. OpenAI: Your backend may use OpenAI's API to process transcripts (subject to OpenAI's privacy policy)
  3. Slack: If configured, action items are sent to your Slack workspace (subject to Slack's privacy policy)
  4. Jira: If configured, tickets are created in your Jira instance (subject to Atlassian's privacy policy)

Data Sharing

We do not sell your data to anyone We do not share your data with third parties except as necessary for the services you've configured (Slack, Jira) You control the data: All data flows through your own backend server

Data Security

API tokens are stored securely using Chrome's storage API All communication with your backend uses HTTPS You control access to your backend server and integrations

Your Rights

You have the right to: Access: View all data stored by the extension in Chrome's storage Delete: Remove the extension to delete all locally stored data Control: Configure or disconnect integrations at any time

Data Retention Local Storage: Data remains until you uninstall the extension or clear browser data Backend Storage: Controlled by your backend server configuration

Children's Privacy Meeting Copilot is not intended for users under 13 years of age. We do not knowingly collect data from children.

Changes to This Policy

We may update this privacy policy from time to time. We will notify you of any changes by updating the "Last updated" date.

Contact Us If you have questions about this privacy policy, please contact us at: Email: zainulhassan1018@gmail.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment