Privacy Policy

Last updated: September 21, 2026

This Privacy Policy explains how Instant Meet ("we", "us") accesses, uses, stores, shares, protects, retains and deletes information when you use our Slack app (listed in the Slack App Directory as "Instant Google Meet") and our website slackmeet.com (together, the "Service").

Instant Meet lets you create a Google Meet meeting from Slack with the /meet, /meeting or /event commands or the "Create a meet" shortcut. It creates the event in your Google Calendar, invites the members of the Slack conversation, and posts the meeting link in that conversation.

1. Google user data

1.1 What Google user data we access

When you connect your Google account, Instant Meet requests a single OAuth scope:

• https://www.googleapis.com/auth/calendar.events.owned: lets the app create and manage events on the Google calendars you own.

We use this permission only for the following actions:

• Create a meeting event in your primary Google Calendar each time you run /meet (or /meeting, /event) or use the "Create a meet" shortcut. The event contains the meeting title, start and end time, color, visibility, a Google Meet conference, and the email addresses of the Slack conversation members as attendees.
• Read and update attendee responses on an event that Instant Meet created. When a member of the conversation answers "Will you attend?" on the meeting message in Slack, we read that event's attendee list and update that person's response (yes, no or maybe).

We do not list, read or modify any other events in your calendar. We do not access your Gmail, Google Contacts, Google Drive or any other Google service, and we do not request your Google profile information.

1.2 How we use Google user data

Google user data is used only to provide the features you request inside Slack: creating the meeting event with its Google Meet link, sharing that link in the conversation where you requested it, and recording attendee responses. We do not use Google user data for any other purpose.

1.3 What Google user data we store

• Google OAuth refresh token. We store it in our database so the app can create events for you without asking you to sign in every time.
• Event details are not stored in our database. The event ID and Google Meet link returned by Google are only included in the Slack message posted to the conversation where you created the meeting.
• Error reports. If a request to Google fails, our error monitoring may record the error message returned by Google and the ID of the related event so we can fix the problem. Tokens are removed from these reports.

1.4 How we share Google user data

We share Google user data only in these cases:

• With the Slack conversation you choose. The meeting title, start time, duration and Google Meet link are posted in the Slack channel, group or direct message where you create the meeting, and are visible to its members. Google Calendar sends the event invitation to the attendees.
• With service providers that host and operate the Service on our behalf (see section 6). They process data only to provide their services to us.
• For legal reasons, if required by law, or to protect the security of the Service and its users.

We do not sell Google user data, transfer it to data brokers or information resellers, or use it for advertising (including personalized, retargeted or interest-based advertising), to determine creditworthiness, for lending purposes, or to build databases. People do not read Google user data unless you give us explicit permission (for example, in a support request), it is necessary for security purposes or to comply with the law.

1.5 Compliance with the Google API Services User Data Policy

Instant Meet's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Instant Meet does not use Google Workspace API data, or any other Google user data, to develop, improve or train generalized or non-personalized AI and/or machine learning models.

1.6 Retention and deletion of Google user data

We keep your Google refresh token only while your Google account is connected. It is deleted from our database when any of the following happens:

• You click Disconnect in the Google Calendar section of the Instant Meet App Home in Slack.
• Instant Meet is uninstalled from your Slack workspace.
• Google reports that the token has been revoked or has expired, for example because you removed access from your Google Account.
• You ask us to delete your data (see section 7).

You can also revoke Instant Meet's access to your Google account at any time from your Google Account permissions page. Disconnecting in Slack deletes our copy of the token; revoking access in your Google Account also invalidates the permission on Google's side.

Events that Instant Meet created are part of your Google Calendar and stay there after you disconnect. You can delete them from Google Calendar at any time.

2. Slack data

2.1 What we store

• Your Slack user ID, workspace ID and workspace name.
• If your workspace belongs to a Slack Enterprise Grid organization, the organization ID and name.
• The Slack user token and bot token issued when you install or authorize the app.
• Your Slack locale, used to offer the app in your language.

2.2 What we read when you create a meeting (not stored)

• The list of members of the conversation where you create the meeting.
• Those members' email addresses, which are sent to Google Calendar as event attendees. They are not stored in our database.
• Members' locale and time zone, used to show the meeting time correctly.
• The conversation's name and type (public channel, private channel, group or direct message), used to apply your visibility settings and, if you enable it, to generate an automatic meeting title.
• The meeting title you type and your Slack display name, used in the event and in the Slack message.

Instant Meet does not collect or have access to the content of your Slack messages.

2.3 Slack permissions and why we need them

• commands: add the /meet, /meeting and /event commands and the "Create a meet" shortcut.
• users:read: view people in the workspace. Required by Slack in order to use users:read.email, and used to read members' locale and time zone.
• users:read.email: view email addresses of people in the workspace, needed to invite conversation members to the Google Calendar event.
• channels:read: view basic information about public channels, needed to identify the members you share the meeting with.
• groups:read: view basic information about your private channels, needed to identify the members you share the meeting with.
• im:read: view basic information about your direct messages, needed to identify the person you share the meeting with.
• mpim:read: view basic information about your group direct messages, needed to identify the members you share the meeting with.

3. Settings, usage and feedback data

• Settings you choose in the App Home: meeting duration, start delay, event color, event visibility per conversation type, automatic title, app language, and which feature announcements you have already seen.
• Usage records for each meeting you create: the date, whether you used a command or the shortcut, and the number of people invited (not who they are), plus a running count of meetings you have created. We use them to operate and improve the Service and to decide when to show the feedback survey.
• Feedback you choose to give in the in-app survey: the option you select and an optional comment of up to 280 characters.

None of this data includes Google Calendar content.

4. Website data

When you visit slackmeet.com we use Cookiebot to ask for your cookie consent, and, if you accept, Google Analytics to understand how the website is used. The website also stores a small value in your browser to show you a consistent version of the page, and loads a Ko-fi widget for optional donations. Website analytics are not linked to your Slack or Google account data. You can change your cookie preferences at any time through the Cookiebot banner.

5. How we protect your data

• All communication between Slack, Google, our servers and our database uses encrypted connections (HTTPS/TLS).
• Data is stored in a managed database with access restricted to the Service and its maintainer.
• Access tokens, secrets and request bodies are removed from application logs and error reports.
• Every request from Slack is verified with Slack's request signature before it is processed.
• The Google authorization flow uses a signed, time-limited state parameter, so a Google account can only be linked to the Slack user who started the flow.
• We only request the minimum Google and Slack permissions needed for the features described in this policy.

No method of transmission or storage is completely secure. If a data breach affects your personal information, we will notify you and the relevant authorities as required by applicable law.

6. Service providers

We use the following providers to run the Service:

• DigitalOcean: hosting of the application servers.
• MongoDB Atlas: database hosting.
• Sentry: error monitoring.
• Cookiebot and Google Analytics: cookie consent and analytics on the website only.

Slack and Google are the platforms Instant Meet integrates with. Your use of them is governed by their own privacy policies.

7. Data retention and deletion

• Google refresh token: retained only while your Google account is connected, as described in section 1.6.
• Slack tokens: deleted immediately when the app is uninstalled from your workspace or when Slack notifies us that they have been revoked.
• Account record, settings, usage records and feedback: retained while you use the Service. When the app is uninstalled, your account is marked as inactive and all tokens are deleted. The remaining records are kept until you ask us to delete them.
• Error reports: kept for up to 90 days and then deleted automatically.

To delete all of your data, email contact@slackmeet.com with the name of your Slack workspace and the email address of your Slack account. We will delete your account record, tokens, settings, usage records and feedback within 30 days, unless we are required by law to keep some of it.

8. Your rights

Depending on where you live, you may have the right to:

• Access the personal information we hold about you.
• Correct inaccurate personal information.
• Delete your personal information.
• Withdraw your consent, for example by disconnecting your Google account or uninstalling the app.
• Object to or restrict the processing of your personal information.
• Complain to your data protection authority, for example under the European Union's General Data Protection Regulation (GDPR).

To exercise these rights, contact us at contact@slackmeet.com. We may ask you to verify your identity before fulfilling your request.

9. Children

The Service is intended for use in work and team Slack workspaces and is not directed to children under 16. We do not knowingly collect personal information from children.

10. Changes to this policy

We update this policy whenever our data practices change, and we change the "Last updated" date at the top of this page. If we make material changes to how we use Google user data, we will notify you in the app before the change takes effect and, where required, ask for your consent again.

11. Contact

If you have any questions about this Privacy Policy or about your data, contact us at contact@slackmeet.com.