Data Security — SyncBrief
Effective date: 30 August 2026
SyncBrief, published by AiDigiApps, records, transcribes and summarizes meetings on iPhone, Mac and Apple Watch. This page describes the technical measures that protect your data. For what data the app handles and why, see the Privacy Policy.
No servers, no accounts
SyncBrief has no backend. There is no account to create, no password to store, and no copy of your recordings, transcripts, summaries or keys anywhere but your device. The only hosts the app ever contacts are the AI providers you configure, the public model host for optional on-device model downloads, and aidigiapps.com for a small model-and-pricing list that carries no personal data. A system with no server-side data has no server-side data to lose.
Encryption at rest
- Library database: recordings' transcripts, summaries, speaker names, notes and tags are stored in a SQLCipher-encrypted SQLite database (AES-256).
- Database key: generated on the device and held in the Keychain, protected by the operating system and your device passcode. It is never written to disk in plain form and never leaves the device.
- Audio files: stored in the app's private, sandboxed container, inaccessible to other apps and additionally covered by Apple's built-in device encryption when your device has a passcode.
API key handling
Provider API keys are stored only in the Keychain — never in the database, never in preferences, never in exports or backups of app data we control. A key is read at the moment a request is made and sent only to its matching provider over TLS to authenticate your own job. We never see or receive your keys.
Encryption in transit
Every network request the app makes — cloud transcription, cloud summarizing, model downloads, the pricing list — uses HTTPS with TLS, enforced by Apple's App Transport Security. Audio and transcripts sent to a cloud provider go directly from your device to that provider, with no intermediary and no relay through us.
Offline by choice
The on-device transcribers (Whisper on-device, Apple speech recognition) and the Apple on-device summarizer process everything locally. Used together, the app sends nothing anywhere — the strongest security measure available is not transmitting the data at all.
Platform protections
- App sandbox: the app runs sandboxed on iOS and macOS; other apps cannot read its container.
- System consent: microphone, system-audio capture (Mac), and calendar access all sit behind the operating system's own permission prompts and can be revoked in Settings at any time.
- Code signing: builds are signed and distributed through the App Store (and notarized by Apple for the Mac direct download), so the code you run is the code we shipped.
- Watch transfers: recordings made on Apple Watch reach your iPhone over Apple's encrypted WatchConnectivity channel, device to device.
What you control
- Nothing is uploaded until you explicitly start a cloud transcription or summary; importing and recording are always local.
- Delete a recording, purge its audio, or remove a saved API key in the app at any time; deleting the app removes everything.
- The app keeps a per-recording log of which provider received what, visible in the app, so you can always see where data went.
Limits
No method of storage or transmission is 100% secure. Data you send to a cloud provider is protected in transit, but its handling at rest on their side is governed by that provider's own security practices and your account settings with them. Device-level protections such as the database key depend on your device having a passcode set.
Reporting a vulnerability
If you believe you have found a security issue in SyncBrief, please email support@aidigiapps.com with the details. We will acknowledge your report and work to address confirmed issues promptly.
Contact
Questions: support@aidigiapps.com