Your data stays yours: what LIA keeps, shows and erases

The problem

To help you, LIA needs to know you: your calendar, your e-mails, your memories, sometimes your location. That's what makes an assistant useful, and what makes it sensitive. Personal data can leak through a place nobody thinks about: a technical log, a backup, a third-party service, an incomplete export.

What I wanted

I wanted three things. That LIA keeps only what the features you turn on actually need. That you can see, take away and have erased what she knows about you. And that the limits are written down clearly, with no promise the system doesn't keep.

Where your data goes

On your instance: your profile, your conversations, your memories and your documents stay on the server of the LIA instance you use, isolated from other accounts.
Encrypted, in part: the credentials of your connected services, your home address and, if you turn it on, your last known location are encrypted. Your location has no history: each update replaces the previous one, and turning the option off erases it.
With providers, only what's needed: the AI model receives your question and the useful context, for example a few memories or a document excerpt. Voice, image or Live mode receive what their function requires. Their own retention rules, and sometimes training rules, apply.

Take your SMS. If you relay them from your iPhone, they arrive encrypted in an archive of your own. Recognized sign-in codes are removed before anything is stored, and the notification announcing a new message doesn't contain its text. Above all, receiving your SMS and letting the assistant read them are two separate consents: until you've given the second one, LIA doesn't read them.

Traces without your words

To run and to be repaired, a server writes technical logs. LIA's logs carry facts: numbers, lengths, identifiers, error codes. Your searches, your interests, the names of your contacts or your files don't go into them. A test reads every log line in the code and rejects one that would write a person's text. And when a database rejects a value by quoting it in its error message, LIA removes the quote before writing the line.

The registers follow the same idea. They say what LIA did for you, what she consulted and what she undertook on her own. A consultation records the capability used, “your calendar” for example, without what was searched in it: writing that down would mean copying the very data the register is meant to protect.

Take it with you, erase it

In Settings › Security, the data export prepares a complete archive: profile, settings, conversations, memories, journal and files, in readable Markdown and in JSON. Secrets aren't included, such as your service credentials or your security keys. It's a sensitive action, so LIA first asks you to confirm your identity. From the Registers page, you can also download the record of everything LIA did and consulted for you, complete whatever its size, with the exact number of lines at the top. You can also export your own usage as CSV: tokens, costs, calls to Google services and voice usage.

To leave LIA, you ask your instance's administrator to delete your account. This purges your personal content: conversations, memories, access to services, documents, health data, saved places. Even if the account is reactivated, they don't come back. Signing out of a device also erases what the browser kept for you: the notification subscription, the last location, the draft in progress.

What I can't promise

Your messages are stored in plain text in the database, and the person who operates your instance may have technical access to them. After a deletion, billing records remain, and audit logs may keep identity details depending on their retention period. Backups follow the policy chosen by the operator. What an AI provider does with the data it receives depends on its contract and its settings. These mechanisms help a deployment comply with the GDPR; they aren't enough to certify it.

Common questions on the subject are answered in the privacy FAQ.