Privacy Policy
Next Meeting — Google Calendar Plugin for Elgato Stream Deck
Introduction
This Privacy Policy explains how Next Meeting ("the plugin," "we," "us") handles information when you use it. Next Meeting is an Elgato Stream Deck plugin, developed by Maksym Aharkov, that shows your upcoming meetings, counts down to the next one, and lets you join with a single key press. It supports Google Calendar (with Microsoft Outlook Calendar support planned).
Next Meeting runs locally on your computer. It has no backend server, collects no analytics, and shows no advertising. This policy describes, in full, everything the plugin accesses and why.
Information we access
When you connect a Google account, Next Meeting requests exactly three Google OAuth scopes:
- openid — used to authenticate you with Google.
- email — used to display the name of the connected account, so you can tell multiple accounts apart.
- https://www.googleapis.com/auth/calendar.readonly — used to read your calendar: event titles, start and end times, your response status (RSVP) for each event, and the event's meeting/video-call link and web link. This scope is read-only; it does not allow the plugin to create, edit, or delete anything in your calendar.
Next Meeting also stores the OAuth tokens Google issues after you sign in, so it can keep reading your calendar without asking you to sign in again every time.
Next Meeting does not request access to any other Google data — not your Drive, Gmail, contacts, or any calendar beyond what's needed to read event data.
How we use this information
Information accessed through your Google account is used strictly to operate the plugin's features:
- Displaying your upcoming meetings and the countdown to the next one.
- Opening a meeting's join link when you press the corresponding Stream Deck key.
- Authenticating you and showing which account is currently connected.
We do not use your calendar data or account information for any other purpose — not for advertising, not for analytics, not for profiling, and not to train any model.
How information is stored
Next Meeting has no backend and no cloud storage. All data it accesses — cached event details and OAuth tokens — is stored locally on your computer, in the plugin's local configuration storage. Nothing is transmitted to any server operated by the developer, because no such server exists.
The only network connections Next Meeting makes are directly to Google's own APIs (for authentication and calendar reads) and, once support ships, to Microsoft's Outlook Calendar API.
Data protection
Because calendar data can include sensitive scheduling and meeting-link information, Next Meeting applies the following protections:
- Encryption in transit: Every connection to Google's APIs (authentication and calendar reads) uses HTTPS/TLS. Calendar data and tokens are never sent over an unencrypted connection.
- Local-only storage, no backend: OAuth tokens and cached event data are stored exclusively on your computer, in the plugin's local configuration storage, protected by your operating system's standard file and user-account permissions. This data is never transmitted to or stored on any server operated by vo1dee, because no such server exists.
- No third-party access: With no backend in the data path, no third party — including vo1dee — can access, intercept, or process your calendar data or tokens. Data leaves your device only in direct, encrypted requests to Google's own APIs.
- Minimal retention: As described below in "Data retention and deletion," tokens and cached data are kept only as long as needed to operate the plugin and are removed when you disconnect the account, uninstall the plugin, or clear its local storage.
- User-controlled revocation: You can revoke access at any time (see "How to revoke access" below), which immediately and permanently cuts off the plugin's ability to read your calendar.
No sharing, no selling, no advertising, no analytics
We do not sell, rent, or share your calendar data or account information with any third party. We do not run analytics or telemetry of any kind, and we do not use your data for advertising. Nobody at vo1dee sees your calendar data — it never leaves your device.
Google API Services User Data Policy
Next Meeting's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Data retention and deletion
Cached calendar data and OAuth tokens are retained locally only for as long as the plugin needs them to function — that is, until you disconnect the account, uninstall the plugin, or clear its local storage. Removing the plugin removes this data from your computer along with it.
How to revoke access
You can disconnect your Google account from Next Meeting at any time in two ways:
- Disconnect the account directly from within the plugin's settings.
- Revoke Next Meeting's access entirely from your Google Account permissions page.
Revoking access immediately invalidates the plugin's locally stored tokens, cutting off its ability to read your calendar. The plugin detects this and prompts you to reconnect the account rather than failing with an error.
Children's privacy
Next Meeting is not directed at children and is not intended for use by anyone under the age of 13 (or the minimum age required by your jurisdiction). We do not knowingly collect information from children.
Changes to this policy
If this policy changes, the "Last updated" date above will be revised accordingly. Material changes will be reflected here before they take effect.
Contact
Questions about this policy or how Next Meeting handles your data can be sent to support@vo1dee.com.