Security and privacy approach

Warp is built for users who need speed and trust. We keep controls understandable, minimize hidden behavior, and provide clear explanations of where audio and text are processed.

Activation control

Warp listens only when you explicitly trigger dictation. No always-on passive recording mode is required for core usage.

Provider transparency

When external speech/AI providers are used, the route is explicit in app settings so users understand processing paths.

Optional workspace links (V1)

Experimental integrations such as Notion use a Warp backend relay: your Mac can store a short-lived Warp session, while third-party OAuth tokens remain on the server and can be revoked if a device is lost.

Local preference storage

Shortcuts and preference metadata are stored locally on the device. Configuration should be user-visible and reversible.

Team governance roadmap

Planned team controls include policy presets, centralized billing, and model access rules for managed deployments.

Need security details for procurement?

Contact us through the waitlist form and mention your security requirements. We can provide current architecture notes and roadmap details for team rollouts.

Contact via waitlist

If insertion fails, recover in under 30 seconds

  • Retry dictation once in the same field.
  • Copy captured text and use paste fallback.
  • Keep writing with manual paste fallback if direct insertion still fails.
  • Save as draft so no content is lost.
  • Report issue with app name, field type, and timestamp.
  • Restore last-good output and continue.

For the full recovery guide, see recovery steps. For processing details, see privacy flow. For field coverage, see supported apps.