Privacy Policy

This policy explains what Cue processes, where the data goes, and how you can manage it. Cue is local first, but local first does not mean that all content always stays on your device.

Data we process

• Account data: email, name, and avatar received through Google sign-in for authentication, access control, admin roles, and usage attribution.
• Audio: while recording, Cue securely relays audio to a third-party speech-processing service for recognition and translation. Cue does not store audio files on its own servers.
• Usage and session metadata: start/end time, duration, language mode, line count, and usage counters are stored in the configured data backend for quotas, administration, and product analytics.
• Transcripts and recaps: completed transcripts are stored in the current browser by default, up to the newest 100 sessions. A full transcript is written to Cue cloud storage only when you choose an upload, create a static share, or take another explicit cloud action from History.
• AI processing: when a meeting is substantial (at least 6 lines, 90 seconds, or 400 characters), Cue automatically sends transcript text securely to a third-party text-processing service for a recap when text processing is enabled. Manual cleanup, Cue cards, and glossary suggestions also send the relevant text.
• Live sharing: when you explicitly start remote live captions, recent subtitle snapshots pass through Cue to managed cloud storage. The system temporarily holds the owner and latest snapshot; viewers who have the link retrieve newer revisions through Cue.
• Preferences and diagnostics: language, theme, subtitle size, and some completion state remain in the browser. If the deployment enables error monitoring, client/server error details may be sent to a third-party monitoring service.

Third-party services

Depending on deployment settings and the features you use, Cue may use:

• Google for account sign-in.
• A speech-processing service for live recognition, translation, and usage logs.
• A text-processing service for automatic/manual recaps and other AI text features.
• Cloud infrastructure services for the website, API, application data, and platform logs.
• An optional error-monitoring service for client and server diagnostics.

Each provider processes received data under its own terms and privacy policy.

Share links

Static transcript and live-caption links are public bearer links: anyone who obtains a link may be able to view its content. Share only with people who should have access. After live sharing stops, the ended snapshot normally remains for about two minutes. Active clients renew a short lease, so an abandoned live session also expires after roughly two minutes.

Retention, deletion, and your choices

• History lets you delete a local item, remove its cloud copy, or disable public sharing.
• “Delete my data” clears browser History and deletes transcript/session content from the active server-side backend.
• Monthly usage counters are retained to keep quotas accurate and prevent quota resets.
• Short-lived quota reservations awaiting service verification are deleted once they no longer affect quota integrity.
• Data already processed by a provider may remain under that provider’s retention policy.

Contact

For privacy questions or data requests, contact jacksonyang0315@gmail.com.