Privacy by architecture

Privacy-First Transcription: Keep Sensitive Audio on Your Device

A privacy statement is strongest when the product architecture supports it. SonWeave does not require an account or operate its own transcription backend, so supported recordings do not need an upload-first workflow.

What stays local

Recordings, transcripts, speaker analysis and supported local AI results are processed and stored on the device by default. This reduces exposure to additional accounts, dashboards and third-party transcription servers.

  • No SonWeave account
  • No SonWeave transcription server
  • Local speaker diarization
  • Local transcript chat on compatible devices

What can leave the device

Optional iCloud Sync stores chosen content in the user's Apple account. Exporting, sharing or opening content in an external AI service sends that selected content according to the destination provider's terms. SonWeave makes these user-initiated actions rather than silent defaults.

Privacy still needs responsible use

Local processing does not replace consent, workplace policy or recording law. Users remain responsible for having permission to record and process a conversation.

FAQ

Frequently asked questions

Does SonWeave upload recordings for transcription?

No. SonWeave does not operate a transcription backend; supported processing is local.

Is iCloud Sync mandatory?

No. It is an optional feature using the user's private Apple iCloud account.

What happens when I share with an AI app?

The chosen external provider receives the shared content under its own privacy policy. This happens only when you initiate it.