MeetLink
Privacy Policy
Effective date: February 27, 2026
Developer: nicemohawk
Overview
MeetLink is a macOS application that adds Google Meet and Zoom as video call options in Apple Calendar. This policy explains what data MeetLink accesses, how it is stored, and how you can control it.
The short version: MeetLink stores your credentials locally on your Mac and communicates directly with Google's and Zoom's servers. We never see, collect, or transmit your data to any server other than those operated by Google and Zoom.
Data we access
Google account information
When you sign in with Google, MeetLink receives:
- Email address — displayed in the app so you know which account is connected. Stored locally in your Mac's Keychain.
- OAuth access token — a short-lived credential used to create Google Meet links on your behalf. Stored locally in your Mac's Keychain. Expires automatically (typically within 1 hour).
- OAuth refresh token — a long-lived credential used to obtain new access tokens without re-signing in. Stored locally in your Mac's Keychain.
MeetLink requests a single Google OAuth scope:
https://www.googleapis.com/auth/meetings.space.created— allows creating new Google Meet meeting spaces. This is the minimum scope required.
MeetLink does not read, modify, or delete your existing meetings, calendar events, or contacts. It does not access any Google data beyond the scope listed above.
Zoom account information
When you sign in with Zoom, MeetLink receives:
- Email address — displayed in the app so you know which account is connected. Stored locally in your Mac's Keychain.
- OAuth access token — a short-lived credential used to create Zoom meetings on your behalf. Stored locally in your Mac's Keychain. Expires automatically (typically within 1 hour).
- OAuth refresh token — a long-lived credential used to obtain new access tokens without re-signing in. Stored locally in your Mac's Keychain.
MeetLink requests the following Zoom OAuth scopes:
meeting:write— allows creating new Zoom meetings.user:read— allows reading your email address for display purposes.
MeetLink does not access your existing Zoom meetings, recordings, chat messages, or any other Zoom data beyond the scopes listed above.
Meeting creation
When you add a video call to a calendar event, MeetLink makes a single API request to the selected provider to create a new meeting. It may also make a token-refresh request to obtain a valid access token beforehand. No other API calls are made.
How data is stored
All data is stored locally on your Mac using the macOS Keychain (data protection keychain):
- Credentials are stored in a shared Keychain access group so the MeetLink app and its Calendar extension can both access them.
- The Keychain is protected by your Mac's login password and, on Apple Silicon Macs, by the Secure Enclave.
- No data is stored on any external server, cloud service, or database operated by us.
- No data is written to disk outside of the Keychain.
How data is transmitted
MeetLink communicates only with Google's and Zoom's servers, using HTTPS:
| Destination | Purpose | When |
|---|---|---|
accounts.google.com | Sign in with Google (OAuth) | When you tap "Sign in with Google" |
oauth2.googleapis.com | Refresh expired Google access tokens | When the Calendar extension needs a fresh token |
meet.googleapis.com | Create a new Google Meet space | When you select "Google Meet" in Calendar |
zoom.us | Sign in with Zoom (OAuth) | When you tap "Sign in with Zoom" |
zoom.us/oauth/token | Refresh expired Zoom access tokens | When the Calendar extension needs a fresh token |
api.zoom.us | Create a new Zoom meeting | When you select "Zoom" in Calendar |
MeetLink does not communicate with any other server. There is no analytics, crash reporting, telemetry, or tracking of any kind.
Third-party services
MeetLink uses Google's OAuth 2.0 and Google Meet REST API. When you sign in, you authenticate directly with Google. Google's use of your data is governed by Google's Privacy Policy.
MeetLink's use of Google user data complies with the Google API Services User Data Policy, including the Limited Use requirements. MeetLink only uses Google user data to provide the meeting-creation functionality described in this policy. Google user data is not used for advertising, transferred to third parties, or used for any purpose unrelated to MeetLink's core functionality.
Zoom
MeetLink uses Zoom's OAuth 2.0 and Zoom Meeting REST API. When you sign in, you authenticate directly with Zoom. Zoom's use of your data is governed by Zoom's Privacy Statement.
Apple
MeetLink is distributed through the Mac App Store. Apple may collect data related to your purchase and app usage as described in Apple's Privacy Policy. MeetLink itself does not share any data with Apple beyond what the operating system provides automatically.
Data retention
- While signed in: Your credentials remain in the Keychain until you sign out or delete the app.
- After signing out: All credentials for the signed-out provider are immediately deleted from the Keychain.
- After deleting the app: Keychain items may persist after app deletion. To remove them manually, open Keychain Access.app and search for
com.nicemohawk.MeetLink.tokens.
Your choices
- Sign out at any time in the MeetLink app to delete all stored credentials for that provider.
- Revoke Google access at myaccount.google.com/permissions.
- Revoke Zoom access in your Zoom account under installed apps.
- Delete the app to stop all MeetLink functionality.
Children's privacy
MeetLink is not directed at children under 13 and does not knowingly collect personal information from children.
Changes to this policy
If this privacy policy changes, the updated version will be posted at this URL with a new effective date. Continued use of MeetLink after changes constitutes acceptance of the updated policy.
Contact
If you have questions about this policy or MeetLink's data practices:
Email: ben@nicemohawk.com
GitHub: github.com/nicemohawk/meetlink