Instant Meet
Trust and permissions
A plain summary for Slack and Google Workspace admins who want to review Instant Meet before installing it: what it asks for, why, what it stores, and what happens when you remove it.
In short
- One Google permission: create and manage the calendar events Instant Meet creates for you.
- Seven Slack permissions, none of which read message content.
- We store tokens, workspace and user IDs, your settings and basic usage counts. We do not store event details or attendee emails.
- We never sell data, use it for advertising or use Google user data to train AI models.
- Uninstalling the app deletes all tokens right away. You can request full deletion at any time.
1. Permissions
| Scope | Why we need it |
|---|---|
calendar.events.owned |
Create the meeting event with its Google Meet link on your primary calendar, and record "Will you attend?" answers on events Instant Meet created. It does not list or read your other events, and it gives no access to Gmail, Contacts or Drive. |
Slack
| Scope | Type | Why we need it |
|---|---|---|
commands | Bot | Adds the /meet, /meeting and /event commands and the "Create a meet" shortcut. |
users:read | Bot | Read members' locale and time zone so the meeting time is shown correctly. Slack requires it to use users:read.email. |
users:read.email | Bot | Get member emails to invite them to the Google Calendar event. |
channels:read | User | Identify the members of a public channel you share the meeting with. |
groups:read | User | Identify the members of a private channel you share the meeting with. |
im:read | User | Identify the person in a direct message you share the meeting with. |
mpim:read | User | Identify the members of a group direct message you share the meeting with. |
Instant Meet does not request any scope that reads the content of your messages or files.
2. Data we handle
| Category | Stored? | Details |
|---|---|---|
| Workspace and user | Yes | Slack user ID, workspace ID and name, Enterprise Grid organization ID and name if applicable, and your Slack locale. |
| Tokens | Yes | Slack bot and user tokens, and your Google refresh token while your Google account is connected. |
| Settings | Yes | Meeting duration, start delay, event color, visibility, automatic title, language and seen announcements. |
| Usage and feedback | Yes | Date, command or shortcut, number of people invited (not who they are), a meeting counter, and optional survey feedback. |
| Created events | No | Events live in your Google Calendar, not in our database. |
| Attendee emails and members | No | Read from Slack when you create a meeting and sent to Google Calendar. Not saved in our database. |
| Slack message content | No | Never collected or accessed. |
| Other Google data | No | Other calendar events, email, contacts, Drive and profile information are never accessed. |
3. Retention and deletion
- Google refresh token: deleted when you click Disconnect in the App Home, when the app is uninstalled, or when Google reports it revoked or expired.
- Slack tokens: deleted immediately when the app is uninstalled or Slack notifies us they were revoked.
- Account record, settings, usage and feedback: kept while you use the app. After uninstall the account is marked inactive and these records are kept until you ask us to delete them.
- Error reports: deleted automatically after 90 days.
- Full deletion on request: email us the workspace name and your Slack email and we delete everything within 30 days.
Events already created stay in your Google Calendar after you disconnect, since they belong to you. You can also revoke access from your Google Account permissions page.
4. Security
- All traffic uses HTTPS/TLS and data is stored in a managed database with restricted access.
- Every Slack request is verified with Slack's request signature.
- The Google authorization flow uses a signed, time-limited state parameter tied to the Slack user who started it.
- Tokens, secrets and request bodies are removed from logs and error reports.
For the full legal detail, including service providers and your rights, read the Privacy Policy and the Terms.
5. Ready to try it?
Now that you know what it asks for and what it keeps, getting started takes three steps:
- Add it to Slack. You review the permissions above on Slack's own approval screen before anything is installed.
- Connect Google. Approve the single calendar permission from the App Home.
- Run
/meetin any channel or direct message and share a Google Meet link.
Add Instant Meet to your Slack workspace
- Free to install
- No access to your messages
- Disconnect Google or uninstall at any time, and tokens are deleted right away
