What AI sees. What stays on your iPhone.
Two features run on your iPhone; chat and large imports still use the cloud.

Private mode on iPhone
Two features, nothing more
Suggested category for an expense you add
Processed on your iPhoneThe description is classified inside the iPhone.
Monthly summary
Processed on your iPhoneThe narrative is written inside the iPhone.
Chat and large imports still use the cloud.

Two features stay on your iPhone
Chat and large batches still use the cloud. Aurio tells you every time.
Suggested category for an expense you add
The description is classified inside the iPhone.
Monthly summary
The narrative is written inside the iPhone.
“Ask your finances” chat
Uses aggregated, sanitised data.
Large imports
Batches are classified on the server.
What leaves. What is protected. What stays.
Eight AI paths, summarised. Open any detail to read the full treatment.


How a piece of data travels
Two examples of how Aurio hides and stores a sensitive value.
An IBAN becomes a label
- The real value
- ES9121000418450200051332
- What the AI sees
- [IBAN]
- What Aurio stores
- The last four digits (1332), the token ACCT_9b4e17c02d5a and the full IBAN encrypted (AES-256) in your token vault, so it can be handed back to you when you export your data.
A merchant is stored as a token
- The real value
- COMPRA TARJ. 5402 MERCADONA MADRID 12/03
- What the AI sees
- Mercadona Madrid
- What Aurio stores
- The token MERCH_a3f2c1d4e5b6 and that cleaned-up name, which is what you see in your lists; the bank's original description stays encrypted (AES-256) and never leaves your account.
The raw bank description never leaves for the classifier; Bizum and P2P never create a merchant
The uncomfortable row: reading an invoice uploads the whole image
Chat conversations live only on your device
The limits of private mode
The device and data type determine where each task is processed.

Before turning on private mode
Check before you trust
Your data, its limits and every AI path, always in plain view.