Privacy & data handling

Scribe0 is built for clinical work, so this page is precise about what leaves your device. The short version: on the native apps, consult audio never leaves your device. The nuances are below.

Audio

Platform	Where audio is processed
Windows	On your PC — never uploaded
macOS	On your Mac — never uploaded
iOS	On your iPhone — never uploaded
Android (in development)	On your phone — never uploaded
Web	Uploaded to a cloud transcription service (US-based)

Transcript text and note drafting (Enhance)

Transcription itself produces text locally on the native apps. The optional Enhance step — turning a raw transcript into a structured note — uses a large language model, and this is where platforms differ:

• macOS and iOS can draft notes fully on-device using Apple’s on-device model (macOS 26 / iOS 26 with Apple Intelligence), meaning nothing — not even text — leaves the device. Both also offer cloud options.
• Windows sends the transcript text (not audio) to a cloud model. The default route is an Australian-sovereign Amazon Bedrock endpoint: inference runs in AWS Sydney/Melbourne and does not leave Australia. An OpenRouter route is available as an alternative.
• Web drafts notes via cloud models.

Know your obligations

If you use a cloud enhance route, the transcript text — which may contain patient details — is processed by that cloud provider. Choose the route that matches your local privacy obligations. On macOS, an on-device PII redaction pass can mask identifying details before any cloud call; this is currently a macOS-only capability.

Storage

All apps store transcripts and notes locally on the device (the web app stores them in your account). Nothing is synced between native apps. There is no analytics or telemetry service — diagnostic metrics stay in local logs on your device.

Accounts

The native apps require no account and no sign-in. Only the web app uses accounts (for sync and access from any browser).