Privacy Policy.

1. Local Processing

When using Wisptype Local, all audio processing and text generation occur on your device. No audio data is ever transmitted to our servers or third-party providers. This keeps sensitive professional conversations local by default.

2. Cloud Integration (Optional)

If you choose to use Wisptype cloud features, audio may be transmitted via encrypted channels through Wisptype's control plane to our current Deepgram-backed cloud transcription stack. These requests are optional and only occur when you explicitly use cloud-enabled workflows.

3. Meeting Transcript Sync

Meeting transcript sync, when available and enabled by you, is an account feature. The desktop app saves meetings locally first. If you opt in, Wisptype stores meeting transcript artifacts in account-scoped cloud storage and stores only non-content metadata, such as meeting IDs, title, timestamps, duration, word count, sync version, retention policy, and content hashes, in the control plane. Raw meeting audio is not uploaded by default. Admin, support, analytics, and request tracing systems are not designed to expose transcript text, segment text, summaries, or audio. You can delete synced meeting metadata through the account sync flow, and deleted meetings are represented as tombstones so other signed-in devices can remove their synced copy.

4. AI Actions

AI Actions are optional, account-linked features on eligible plans (for example Pro). They include selection transforms (rewrite, summarize, or otherwise transform selected text) and computer-use style steps that help automate on-screen work. AI Actions only run when you explicitly start them; everyday local dictation does not send content for AI Actions by default.

Depending on the action type and your plan, the desktop app may send selected text, natural-language instructions, UI context, and/or screenshots (or similar visual context) to the Wisptype control plane and onward to model providers that perform the transform or step planning. We process this content only to fulfill the action you requested, enforce entitlements, and operate the service. We avoid using these payloads for unrelated analytics, and admin dashboards are not designed to surface action content such as selected text, screenshots, or model outputs.

5. Action Credits

AI Actions consumption is metered with Action Credits. Eligible plans may include a monthly allotment of credits; additional top-ups may be available for purchase on plans that support them. Credit balances, usage events, and related billing metadata are stored in the control plane to enforce quotas and show usage in your account. Metering records focus on operational counts and plan state rather than retaining full action content.

6. Cloud AI Workspaces (Box)

On plans or beta programs that include them, Cloud AI workspaces (Box) can run heavier automation in a cloud VM environment subject to plan guardrails (for example concurrent workspace limits, TTL, and idle timeouts). When you use a Cloud AI workspace, session metadata, runtime metering, and any content you deliberately send into that workspace may be processed by Wisptype infrastructure and associated providers solely to operate the workspace and your requested actions. Local-first dictation remains available without using Cloud AI workspaces.

7. Analytics & Telemetry

We may collect operational usage and diagnostic data to provide account features, enforce entitlements, measure usage, and improve reliability. We avoid storing transcript content for these operational events, and cloud workflows are account-linked when you choose to use them.

8. Account Information

We store account information needed for authentication, subscriptions, entitlement checks, usage reporting, device sessions, and support. We will never sell your personal information to third parties.