Privacy Policy
Last updated: June 2, 2026
Overview
Microdash builds Stream Deck plugins for Elgato. This policy covers all current plugins: NextUp, LinearNotify, Gmailo, PeekStripe, HowManyLeft, WhatsLeft, and OpenBalance. None of our plugins transmit data to Microdash servers. All data stays on your device and travels only between your device and the relevant third-party service.
Data We Access
NextUp (Google Calendar)
NextUp uses Google OAuth 2.0 (calendar.readonly scope) to read your upcoming calendar events — title, time, location, and conference links. It does not modify, create, or delete any calendar data. Subject to Google's Privacy Policy.
LinearNotify (Linear)
LinearNotify uses Linear OAuth 2.0 to read your inbox notification count, grouping metadata, and issue URLs. Read-only. Subject to Linear's Privacy Policy.
Gmailo (Gmail)
Gmailo connects to Gmail via IMAP using a Google App Password (a 16-character password you generate in your Google Account). It reads your unread message count and the subject and sender of your most recent message. It does not read message bodies or attachments and does not modify, send, or delete messages. Your email address and App Password are stored locally in Stream Deck's settings. Subject to Google's Privacy Policy.
PeekStripe (Stripe)
PeekStripe uses a Stripe restricted API key that you create and paste into the plugin. It reads balance transactions and your current balance from Stripe's API to display recent earnings. It does not initiate charges, issue refunds, or access customer personal data. Your API key is stored locally in Stream Deck's settings. Subject to Stripe's Privacy Policy.
HowManyLeft (Claude / Anthropic)
HowManyLeft reads usage and credit data from Anthropic's API (api.anthropic.com). It uses the OAuth token already stored on your device by the Claude Code CLI — it does not create a new auth session or store additional credentials. Subject to Anthropic's Privacy Policy.
WhatsLeft (OpenAI Codex)
WhatsLeft reads usage data from OpenAI's API and the OpenAI status page. It uses the token already stored on your device by the Codex CLI (~/.codex/auth.json) — it does not create a new auth session or store additional credentials. Subject to OpenAI's Privacy Policy.
OpenBalance (OpenRouter)
OpenBalance uses an OpenRouter Management API key that you paste into the plugin. It reads your credit balance and 30-day activity data from OpenRouter's API. A Management key cannot make AI inference requests or spend credits. Your key is stored locally in Stream Deck's settings. Subject to OpenRouter's Privacy Policy.
Data Storage
Plugins store credentials and preferences locally on your device only, within Stream Deck's settings storage:
- OAuth tokens (NextUp, LinearNotify): access token, refresh token, expiry
- API keys (PeekStripe, OpenBalance): the restricted/management key you provide
- IMAP credentials (Gmailo): your email address and App Password
- Display preferences: theme, format, and other UI settings
HowManyLeft and WhatsLeft read credentials from existing CLI tool files on your device and store nothing additional. No data is stored on Microdash servers. We do not operate any backend.
Data Sharing
We do not share, sell, or disclose your data to any third parties. Data is exchanged only between your device and the service you connected.
Data Retention & Deletion
Data is retained locally only while the plugin is configured. To delete it:
- Any plugin: click Disconnect in the Property Inspector, or uninstall the plugin from Stream Deck
- NextUp: revoke access at myaccount.google.com/permissions
- LinearNotify: revoke access in your Linear account settings
- Gmailo: delete the App Password at myaccount.google.com/apppasswords
- PeekStripe: revoke the key in your Stripe Dashboard
- OpenBalance: revoke the key in your OpenRouter Management Keys
Analytics & Tracking
We do not use analytics, tracking, telemetry, or any form of usage monitoring in any of our plugins.
Children's Privacy
Our plugins are not directed at children under the age of 13. We do not knowingly collect information from children.
Changes to This Policy
We may update this policy from time to time. Changes will be reflected on this page with an updated date. If we make material changes to how we handle Google user data, we will notify users and obtain consent before applying the new practices.
Website Analytics
This website uses a privacy-focused analytics service to understand how visitors use our site. The service is designed to collect the minimum data necessary and does not use cookies or track individuals across sessions or websites.
The analytics service collects the following information when you visit the site:
- Pages visited and time spent on each page
- Referring website or search engine (the page you came from)
- Browser type and operating system
- Screen size (to understand device types)
- Country of origin, derived from your IP address — your IP address itself is not stored
This data is aggregated and anonymous. It cannot be used to identify you personally. No cookies are set. No persistent identifiers are assigned. No data is shared with advertisers or third parties for marketing purposes.
You can decline analytics collection at any time using the consent notice displayed at the bottom of each page. If you decline, no data will be collected during your visit. Your preference is stored locally in your browser and respected on future visits.
Contact
If you have questions about this privacy policy, please contact us at support@microdash.sbs or open an issue on our GitHub repository.