Skip to content

Privacy policy

This policy explains what personal data Lianas collects, why, where it is processed, and what rights you have over it.

Last updated: October 22, 2026

Who we are

Lianas is operated by Aurioa Tech, the data controller for the personal data described in this policy. For any privacy-related question or request, contact info@lianas.app.

What data we collect

  • Account: email address, display name, a hashed password (bcrypt), when you turn on two-step verification its encrypted key (Fernet) and your hashed recovery codes, language, time zone, the date you accepted the terms, and your settings (voice, notifications, custom instructions, provider choices, the business details used on your invoices and letters).
  • Conversations: the messages you exchange with Lianas, their titles and timestamps, and the draft you have not sent yet.
  • Memory: what Lianas keeps about you and your contacts (people, places, projects and how they relate) and your messages, to find them again, drawn from your conversations and from what she looked up for you, plus your calendar appointments and the summary of your sorted mail (never newsletters or low-importance mail), so she links what you talk about to them by herself.
  • Voice: if you speak to Lianas, the audio is transcribed then deleted; only the text is kept, as a message.
  • Mailbox, if you connect one: the server address and username, and the password encrypted (Fernet). Lianas reads your new mail, the unread mail of the last 3 days when you connect the mailbox (10 at most) and, to follow up, the mail you sent recently. For each mail she sorts, she keeps the sender, subject, date, category, a short summary and the reply she drafted or sent, not the full message; for a message received on another platform, also its name, the sender, the start of the message and the link to the conversation. When you open a mail in Lianas, she reads it whole to show it to you without keeping it, and hands you an attachment only once the antivirus has checked it. If you keep only the mail that matters, she sets the rest aside in Lianas, without touching your mailbox, and remembers the senders you judged important or not. When you change how a mail is sorted, she remembers the new category for its sender (the last 300 senders), to sort their next mail and that of similar senders the same way. With each mail she sorts, the AI model also gets what she knows of its sender when its address is verified (whether you answered or pinned them, how you judged or re-sorted their mail before), and your last 10 re-sorted senders with their category. In automatic mode, which you turn on per mailbox, she reads the whole mail and answers some of them without asking you. What she does on her own with each mail (filing it into a folder, suggesting reminders and events, drafting replies, suggesting follow-ups) can be turned off in Settings, Email tab. Replies go out through your own mail server. Only when you ask, she archives a mail or moves it to the trash or to another folder of the same mailbox; nothing is erased for good.
  • Calendar, if you connect one: the server address and username, and the password encrypted (Fernet). Lianas keeps a copy of your events for the next three weeks (title, place, address, times) to prepare your day.
  • Files, notes and folders: the files you upload, ask her to keep from a mail or ask her to write as a PDF, their extracted text and a short description, your notes, and the folders you organise them in. Every file is scanned by an antivirus before it is kept, and images are checked by a moderation model.
  • To-dos, reminders and scheduled tasks: their titles, dates and repetitions.
  • Devices and notifications: for each device you sign in on: a name such as "Chrome (Windows)", the platform, when it was last seen and, if you allow notifications, its push subscription. The notifications sent to you are kept in a history.
  • Desktop app and agent: on the Big plan, the commands Lianas runs for you on the machine you connect (the desktop app or a server) and their output. The desktop app's wake word is detected on the device itself.
  • Your feedback: the remarks you send us, from the app or the chat, and your answers to the satisfaction question, with the page and app version they came from.
  • AI usage: for each request to a model: the model, the number of tokens or seconds, and the date, used for your credits and for the energy estimate you see in your settings and we follow.
  • Paid offer waiting list: if you ask to hear about a paid offer, from the pricing section or from the app, your address and language.
  • Technical data: IP addresses, used for rate limiting and abuse prevention and never stored in our database, and server logs (IP address, page requested). When an error occurs, a technical report is emailed to our team; it only says where in the code the error happened and its type, never your content.
  • Audience measurement: on our website and app: the pages visited (without their parameters), the referring site, browser, system, screen size, language, the country and city deduced from the IP address (the address itself is not kept), load times, and a few steps such as signing up, confirming your email, sending a first message or connecting a mailbox, and whether you are signed in, have confirmed your email or have used up your credits. No cookie is used and you are never identified. Some visits are also recorded, with all their text hidden, as described below.

We do not sell your data, use it for advertising, or use it to train AI models.

Why we process it

  • Providing the service (performance of contract): answering your messages, keeping your memory and history, sorting your mail and drafting replies, preparing your day from your calendar, keeping your files, notes and to-dos, reminding you, and running the tasks you ask for.
  • Emails about your account (performance of contract): confirming your address and its reminders, password resets, inactivity and deletion notices, a single help message a few days after sign-up if you have barely used Lianas yet, and any notification that reached none of your devices.
  • What's new in Lianas (legitimate interest): at most one email a month presenting new features, only when there are some. You can unsubscribe at any time, from the link in every email or in Settings, Notifications tab.
  • Security (legitimate interest): login lockout and rate limiting based on IP addresses, antivirus and moderation, and a security audit log to detect abuse.
  • Improving the service (legitimate interest): reading your feedback and satisfaction answers, measuring the audience of our pages without identifying you, and recording visits without their content to see where people get stuck.
  • Optional external providers (consent): only when you configure your own key.

Where your data is processed

Your account, conversations, memory, mail and calendar data, files and notes are stored and processed in Switzerland, on Infomaniak's infrastructure, under the Swiss Federal Act on Data Protection. Speech-to-text, voice synthesis, web search, embeddings, the antivirus and audience measurement run on our own servers.

Some data goes to other services, only as far as needed:

  • Infomaniak, Switzerland: hosting, the language models, speech-to-text when our own server is unavailable or hears nothing, and, even when you use your own key, the extraction of your memory and the moderation of your messages and images.
  • When Lianas looks into things on her own: if you turn it on (it is off by default), for each mail you receive except newsletters and before your meetings, Lianas looks up who the sender or the attendees are, their company and the topic. Their names and their companies' names then go into web searches, through the same engine as below. While searching, she only sees that mail or meeting, never your memory or your other mails. She never acts on her own from what she finds.
  • Web search: your queries go to our own search engine (SearXNG), which passes them on without your IP address to public search engines: Bing (Microsoft), Seznam, Wikipedia and Wikidata, and DuckDuckGo for currency conversions. Some of them are in the United States. The results of a search are kept in the server memory for up to an hour, so the same search does not go out twice, and are never written to disk.
  • Web pages: when Lianas reads a page for you, our server fetches it: the site sees our server, not you.
  • Places: to find the address of an event's location, its place name is sent to OpenStreetMap's geocoding service (Nominatim).
  • Push notifications: they pass through the push service of your browser or system (Google, Apple, Mozilla or Microsoft, some in the United States). Their content is encrypted for your device: the push service only sees that a notification passes, when, and its size.
  • Your mail and calendar providers: the mail Lianas sends and the events she creates go through the servers you connected.
  • Newsletter senders: when you ask Lianas to unsubscribe you, she contacts the sender through the address or link it gives in its email. It only learns that your address unsubscribes.
  • Your own keys: if you use your own key for the language model (OpenAI, Anthropic, Gemini, OpenRouter, Mistral, Scaleway, OVHcloud, Albert, IONOS, Nebius or Regolo), transcription (OpenAI, Mistral, Scaleway, OVHcloud, Albert or Regolo), voice (ElevenLabs or Mistral) or web search (Tavily or Staan), what that service needs goes to it under its own privacy policy, including the sorting of your mail and the filing of your notes and files when it is your language model. The app shows where each service sends your data.

See the transparency report for the full data flow.

How long we keep it

  • Conversations: until you delete them. Deleting a conversation does not remove what Lianas learned from it or the files sent in it: you manage those in your memory and your files.
  • Memory: until you delete the facts, or wipe the whole memory.
  • Mail and calendar: the sorted mail stays until you archive, delete or move it from Lianas, disconnect the mailbox or delete your account.To ask what came out of a meeting that just ended, Lianas keeps the title and description of the day's meetings, two days at most. The copy of each event goes a month after it ends, unless you filed it in a folder yourself, or when you disconnect the calendar.
  • Briefings prepared by Lianas: 30 days, then erased.
  • Files, notes, folders and to-dos: until you delete them. A file you asked Lianas to remember leaves its description and facts in memory until you delete them there.
  • Notifications: 30 days once read, 90 days at most.
  • Screenshots of web pages: 15 days.
  • Devices: until you remove them.
  • Security audit log: raw requests and answers, mail sent, archived, deleted or moved on your behalf,commands run by the desktop app or agent and blocked files. Removed with the conversation they belong to, or with your account for the rest.
  • Your feedback: until you delete your account.
  • AI usage: unlinked from you when your account is deleted, then kept for our statistics.
  • Paid offer waiting list: until you ask us to remove your address, or delete the account that uses it.
  • Technical data: rate-limiting counters expire after one minute to one day depending on the check. Server logs are erased at each update of the service.
  • Backups: every night, an encrypted copy of the account, conversations, memory and files is made on our server in Switzerland and kept 7 days. Data you delete, or a deleted account, leaves the backups within those 7 days.
  • Account: until you delete your account, which deletes the data above with it. We also delete inactive accounts automatically: after 3 months without use we email you a notice, after about 5 and a half months a deletion warning, and after 6 months of inactivity the account and its data are permanently deleted (never less than two weeks after the warning). Any use of the service resets this cycle. An account whose email address is never confirmed is deleted with its data 30 days after sign-up, whether or not it was used. We remind you by email the day after sign-up, then one last time three days before the deletion.

Cookies and local storage

We use a single cookie: the session cookie that keeps you signed in (httpOnly, 30 days). There is no advertising or tracking cookie. Your browser also keeps, in local storage on your device, a device identifier, the conversation you have open, your voice settings and display preferences; the desktop app keeps its session there too.

Visit recordings

To see where people get stuck, we record how visits unfold on the website and in the app: the pages, clicks, scrolling and time spent. All text, every field and every image are hidden in these recordings, so they never show what you write or read. They go to our own audience measurement server in Switzerland and are kept 30 days. No recording is made when your browser sends Global Privacy Control or Do Not Track, nor on a page opened from a link that carries a token (email confirmation, password reset).

Record my visits anonymously

Applies to this device, from the next page loaded. Also in Settings, Data tab.

Your rights

Under the GDPR and the Swiss FADP you can access, rectify, delete, and export your data, restrict or object to processing, and lodge a complaint with your supervisory authority. Most of these rights are exercisable directly in the app: view your memory and rename, pin or delete its facts, delete conversations, files, notes and to-dos, wipe all memory, disconnect a mailbox or calendar, turn off the news emails, and delete your account. In Settings, Data tab, "Export my data" downloads a JSON file with your account, settings, conversations, memory, folders, sorted mail, calendar events, file list, notes, to-dos, scheduled tasks, notifications, devices and feedback, and each conversation can be exported as markdown.

For anything else, write to info@lianas.app.

How we protect it

Passwords are hashed with bcrypt. Your own API keys and your mailbox and calendar passwords are encrypted at rest with Fernet. Transport is encrypted with TLS, the session cookie cannot be read by scripts, signing out ends the session on that device, sign-in is protected by per-account and per-IP rate limiting, and every file is scanned by an antivirus before it is kept.

Changes to this policy

We will update this page when our data practices change and revise the date at the top. Significant changes will be announced in the app.