Skip to main content
Desktop capture handles sensitive data. Nothing records without explicit user consent. This page covers permission patterns, storage controls, and privacy-first design.
Desktop capture currently supports macOS and Windows.

Quick Example


Trust Model

Two-Component Architecture

Security is built into the architecture:
  • API key never leaves your backend
  • Desktop client uses short-lived tokens (10-15 min expiry recommended)
  • Compromised tokens have limited blast radius

Token Pattern


Permission Handling

Request Before Capture

Required UX Elements

Your desktop client must include:
  • Recording indicator - Visual cue that capture is active
  • Pause button - Let users temporarily stop
  • Stop button - Let users end the session

Storage Control

Ephemeral Mode

Process in real-time without persisting media:
Use ephemeral mode when:
  • Processing sensitive content
  • Storage isn’t needed
  • Privacy regulations require it
  • Building real-time assistants only

Selective Storage

Store only what you need:

Data Retention

Default Behavior

  • Media stored until explicitly deleted
  • No automatic expiration
  • Indexes and transcripts stored with media

Manual Deletion

Implement Data Subject Access


Compliance Patterns

GDPR

  • Implement data access endpoints
  • Implement deletion endpoints
  • Document processing purposes
  • Use ephemeral mode when storage isn’t needed

HIPAA

  • Use ephemeral mode for PHI
  • Implement strict access controls
  • Audit all data access
  • Consider data minimization

General Best Practices


Summary

Key principles:
  • Nothing records without explicit user permission
  • Storage is optional per-channel (store: false)
  • Visible recording indicators are required
  • API key never leaves backend
  • Tokens are short-lived and limited scope

Next Steps

Capture Overview

Architecture and quickstart

Real-time Context

Events you receive