Where your audio goes
A recording in Sessa, followed from the microphone to the exported file: what happens on your device, what leaves it and when, and how you can check this without taking our word for it.
Last updated:
In short
- Everything is transcribed on your own devices. Your recordings and transcripts stay on the device unless you turn on iCloud sync. If you do, they are encrypted on your device before they are stored in your iCloud, with a key that only your devices hold. Codonic never receives them, and Apple cannot read them.
- The app goes online in three cases only: to download a language pack, to send a diagnostics report if you choose to, and to sync through your own iCloud if you turn that on.
- There is no account, no advertising, no tracking and no analytics.
- Sessa is closed source, so this page ends with things you can check yourself, and with the limits of what we can show.
1. You record, or bring a recording
On an iPhone, Sessa records from the microphone when you start a recording, and stops when you stop it. On a Mac it can also record the sound the Mac plays together with your microphone, so both sides of a call in any app on your Mac are captured, as two tracks. It records sound only, never the screen, and never starts by itself.
You can also import an audio file, or a video file for its sound. Sessa keeps its own copy, stored like any other recording.
Telling the people you record, and getting their consent, is your responsibility. The rules differ by place and profession, and Sessa gives no legal advice.
2. The device transcribes it
The speech models run on your iPhone or Mac. The recording is not sent to a transcription service, to us or to anyone else to be processed. That is why transcription works with no network at all once a language pack is installed.
Telling the speakers apart also happens on the device. If you record a short sample of your own voice, so that Sessa can mark which speaker is you, the sample is kept on your devices like the rest of your library, and you can delete it at any time. It is the only voice sample Sessa keeps.
The result is a draft. Sessa marks the parts it is unsure of; you listen, correct and name the speakers. It writes no summaries and no notes.
3. It is stored encrypted, behind a lock
Recordings, transcripts, names and folders are stored encrypted on the device. Each device keeps its own key on that device only. On an iPhone the key exists only while the phone has a passcode, and the app opens with Face ID or that passcode. On a Mac it opens with Touch ID or your password.
We do not have the key. We cannot read, copy or restore what is on your device.
Without iCloud sync, Sessa’s data is not part of iCloud or computer backups of the device. If the device is lost or the app is deleted, what was in it is gone unless you exported it.
4. iCloud sync, only if you turn it on
Sync is off until you turn it on. If you do, your library is encrypted on your device before it is stored in your iCloud, with a key that only your devices hold. Codonic never receives it, and Apple cannot read it.
The key travels between your devices through iCloud Keychain, which Apple cannot read, and through a recovery key that Sessa shows you when you turn sync on, for you to keep. Anyone who has your recovery key and access to your Apple Account could read your library, so keep it private.
What Apple can see with sync on: that a Sessa library exists in your iCloud, how large it is, and when it changes. Not what is in it.
You can choose to sync transcripts only and keep the sound on the device that recorded it.
5. You export what you choose
A transcript leaves Sessa only when you export or share it. The exported file is an ordinary file: it is no longer encrypted by Sessa, and it goes wherever you send it. From that point its safety depends on where you put it.
Every network connection the app makes
- Language packs. Each language pack (about 1.1 to 1.6 GB) is downloaded once from our own server, models.codonic.dev. Before sending a file, the server uses Apple’s App Attest service to check that the request comes from a genuine copy of Sessa. It keeps no log of requests and receives nothing you record or type.
- A diagnostics report, if you send one. Nothing is sent automatically. If you choose to send a report from the settings, the app shows you the exact report first. It holds technical details and any note you add, never recordings, transcripts or names.
- iCloud, if sync is on. The app talks to your own iCloud to keep your devices in step. What it sends is encrypted on the device first.
That is the whole list. The app has no account system to contact, and carries no advertising, tracking or analytics code. The app also has links to this website and to the App Store, which open only when you tap them.
How to check this yourself
- Read the App Store privacy label. On Sessa’s App Store page, the App Privacy section shows what we have declared to Apple about the data the app collects.
- Turn on airplane mode. After the language pack has downloaded, switch on airplane mode, record something and let it transcribe. It works the same, because nothing is sent.
- Look at the connections. On an iPhone, turn on App Privacy Report in Settings, under Privacy & Security, use Sessa for a while, and read which addresses it contacted. On a Mac, a network monitor shows the same. You should find the items in the list above and nothing else.
The limits of this page
- Sessa is closed source. You cannot read the code, so the checks above are the evidence we can offer.
- With sync on, your library is held by Apple’s iCloud, under your own Apple Account and Apple’s terms. Apple cannot read it, but can see that it exists, its size and when it changes.
- Sessa protects what is inside the app. It cannot protect a file after you export it, a device with no passcode, or a recovery key that someone else has seen.
- A transcript is a draft made by software. It can have wrong words and wrong speakers until you have checked it.
- Nothing here is legal advice, and Sessa makes no claim about the rules of your country or profession. Those remain yours to check.
The full detail is in the privacy policy. Questions: support@codonic.dev.