Trust
Trust, privacy, receipts
Aegiscribe centers on local-first processing: core note generation is designed to run on your machine so sensitive audio does not need to ship to a remote service for that step.
From import to audit trail
Import a recording, generate notes locally, and read the session trail in one place—timestamped review, where processing ran, and events from input through outputs.
Import → Transcribe → Summarize → Review → Copy → Audit
How your data is handled
- Capture: Record outside Aegiscribe; import when ready.
- Processing: Core transcription and summary on-device; status visible in the app.
- Storage: Local session data on your machine; you control retention and export.
- Network: Core workflow designed offline-capable; optional services labeled when present.
- Audit: Session receipt from import through generated outputs.
If optional cloud LLM features are offered in the future, they would require explicit opt-in, your provider, and your API key, not the default path.
Language we use (and avoid)
We avoid absolute claims unless every feature, update path, and optional service supports them. Prefer phrasing like “core note generation runs locally” and “optional network-dependent features are labeled when present.”
- Audit receipts provide processing visibility; they are not a legal or compliance certification.
- We do not claim HIPAA, GDPR, or other compliance outcomes until validated for your deployment.