Skip to main content

Privacy Policy

Last updated: October 31, 2026

This policy explains what data CommandGlows processes, why, with which providers, and how you can access or delete it. It covers the commandglows.com website and the CommandGlows Android app (keyboard, dictation, clipboard, snippets).

1. Data we process

Depending on the products and features you use, we may process the following categories:

  • Email address, user ID (Clerk ID) and, if you sign in with Google, the name and email of your Google account, to manage your account
  • If you turn on app sync: clipboard items, dictation transcriptions, snippets, dictionary entries, custom action buttons, keyboard configuration, settings and theme background images, stored in Convex under your account. Without an account, this data stays on your device
  • Crash reports and technical diagnostics (see Sentry in the Providers section)
  • Order and access-right records needed to deliver purchases made on the website. Payment details are entered with Stripe and do not pass through our servers
  • When you connect Gmail: messages and metadata requested by mailbox features, plus an encrypted refresh credential linked to your verified account
  • For a dispatch you confirm: the approved summary, contribution type, justification, confidence, risks, and opaque identifiers needed for recovery

2. Android app: permissions and access

The app requests sensitive access. Each one is tied to a specific feature, and you can refuse or remove it in Android settings.

  • Keyboard: as a keyboard, the app sees the text you type in the fields where it is active. That text is used for typing and its features (suggestions, snippets). Sensitive fields (for example passwords) are excluded from clipboard history
  • Microphone: used only for dictation, started by you. The app does not keep the audio recording. Speech recognition is provided by your device's recognition engine (Android); depending on that engine, audio may be processed online by its provider under its own policy. The dictated text may be saved as a transcription (see sync)
  • Clipboard: the keyboard reads the clipboard when you ask (paste) and keeps a local history. That history is sent to Convex only if sync is on
  • Accessibility service (optional): if enabled, it is used only to insert dictated text at the cursor in the app of your choice, and to detect password fields so it does not write into them. It does not collect, store or transmit any screen content. Without it, dictated text is copied to the clipboard. You can turn it off at any time in Android accessibility settings
  • Floating bubble and foreground service: the dictation bubble appears over other apps through a foreground service, shown by a persistent notification. You turn it on and it can be stopped at any time
  • Notification access (media): used only to show the title of the current media and to send play, pause or next from the keyboard. No notification is read or kept
  • Vibration: haptic feedback on keys

2. Data Usage

Your data is used for:

  • Account management and authentication
  • Syncing between your devices, if you turn it on
  • Delivery of products and web purchases
  • Customer support
  • Crash analysis to fix the app
  • At your explicit request, reading Gmail messages and changing their labels, archive state or trash state
  • Optional email triage after visible consent: the selected email's text and limited project context are sent through your OpenRouter account to the model provider you chose. Retention and training rules vary by endpoint and account settings. The product does not offer an email-sending action
  • We do not sell your data and the app uses no advertising or usage-analytics tools

3. Data Protection

We implement security measures including:

  • Encryption in transit (HTTPS) for exchanges with Clerk, Convex, Sentry and Stripe
  • Server-side access checks: synced data is stored under your account and is readable only with a valid sign-in and active access
  • Sensitive tokens and credentials kept in the device's secure storage
  • Mailbox credentials are encrypted in account server storage and are accessible in ContentGlows and ShipGlows.app only through a verified identity link
  • Access controls

4. Providers

We use the following providers, who process data on our behalf:

  • Clerk: sign-in, sessions and account management
  • Google: signing in with your Google account through Clerk, if you choose it
  • Sentry: crash reports and diagnostics. Active only if the app build was made with Sentry configured. Default personal information is not sent and screenshots are disabled
  • Stripe: payment for web purchases (card and other methods offered), under its own privacy policy
  • Convex: account, order and access-right data, and app sync data and files
  • Website hosting and email delivery
  • Google Gmail for connected mailboxes
  • OpenRouter and the model provider you chose, if you consent to AI triage

5. Your rights

You have the right to:

  • Access your data
  • Request corrections
  • Unsubscribe from communications
  • Request deletion of your data and account

6. Deleting your account

You can request deletion of your CommandGlows account and associated data (including data synced in Convex) from the account deletion page. Purchase records subject to legal or accounting obligations are kept for the required period.

Delete my account

7. Cookies

We use essential cookies for:

  • Session management
  • Authentication
  • User preferences

8. Retention

When the inactive-account retention process is activated, inactivity for a CommandGlows website or app account will be measured from the last sign-in verified by our services. After 24 months without a verified sign-in, we will send a warning and allow 90 days to sign in again. A reminder is planned 30 days before the deadline. If the person does not sign in within that period, the CommandGlows profile and the account-linked cloud data covered by this process will be deleted. Accounts with an active paid CommandGlows right or a link to another product are excluded. Purchase, entitlement and evidence records subject to legal or accounting obligations are not deleted by this process and remain subject to their own retention periods. Separately, private email review payloads in the primary application stores are deleted after 90 days. A minimal dispatch fingerprint and opaque identifiers remain to block a delayed duplicate. Provider backups may retain older snapshots under their own schedules; Convex documents up to 14 days for weekly backups, while

9. Updates

This policy may be updated periodically. Users will be notified of significant changes.

10. Contact

The data controller is Diane Defores, sole proprietor operating CommandGlows. For privacy questions or to exercise your rights, contact: privacy@commandglows.com