Privacy policy
Version alpha-15 — 20 November 2026
ilo is an assistant for families, on iPhone and Android, in a free alpha for invited testers. This page explains what we do with your data, as plainly as we can. The words that matter are in bold.
Who we are
The controller is Dany Agostinho, who publishes ilo as an individual (there is no company yet). On this page, “we” means Dany Agostinho.
Contact: hello@withilo.com. Security: security@withilo.com. We have not appointed a data protection officer: write to hello@withilo.com with any question.
ilo is an artificial intelligence
When you write to ilo, an AI answers you, not a person. ilo relies on AI models from providers (Anthropic, Google, Mistral: see below).
La Matinale, ilo’s daily audio show (in testing), is read by a synthetic voice.
ilo can be wrong. Check what matters. ilo makes no decision that has legal effects on you based solely on automated processing.
The data we process, and why
| Data | Why | Legal basis |
|---|---|---|
| Account: your email and name as given by Google or Apple at sign-in, the address of your profile picture, your language and settings, your statement that you are 18 or older, the version of these texts you accepted. | To create and run your account. | Performance of the contract. |
| Family and household: the adults of the household (two at most during the alpha), the people you add, children included (name, birth date, phone, email, relationship), what ilo remembers about them, the people you add to your contacts (picked one by one from your phone or from Google, or added with one tap when you write to or invite them), the details ilo adds to people already in your contacts (see “What ilo learns from your accounts”), the household’s city (found from your phone’s location if you allow it, or from the name you type) and, if you save it, its address. | So ilo knows your family and can help; the weather for your city. | Performance of the contract; for the people you talk about, our legitimate interest in helping you organise your family’s life. |
| Conversations: your messages, ilo’s replies, titles, reactions; notes and tasks, parcels, trips and dates to celebrate. | The service itself; to remember what you tell ilo about yourself and your people (see “What ilo learns from your conversations”). | Performance of the contract. |
| Calendar: Google Calendar and, on iPhone, Apple Calendar; on Android, Google Calendar only (see “Calendars, mailboxes, Drive and contacts”). | To show your day; to add, move or delete an event when you ask; to share an event with the other adult. | Performance of the contract; for automatic additions from your emails, your consent, which you can withdraw. |
| Google Drive and contacts (if you connect them): the Drive files you ask ilo about, the files it writes for you, and the people it looks up for you in your contacts, your emails’ senders and recipients and your iPhone (see “Calendars, mailboxes, Drive and contacts”). | To find and read a file, put one in your Drive, find the address or number of someone you want to reach, when you ask; to complete the people already in your contacts with what it found (see “What ilo learns from your accounts”). | Performance of the contract; for the people you look up and those ilo learns about, our legitimate interest in helping you reach them and organise your family’s life. |
| Emails forwarded to ilo’s address: the email (often written by someone else: a school, a club, a shop) and its attachments. | To add the appointment, task, birthday or document you sent; to remember what it learns about your people (see “What ilo learns from your documents”). | Performance of the contract: it is your request. |
| What you show ilo: photos, screenshots, PDFs, text, links and messages shared with ilo or attached to a conversation. The original is not kept; we keep what ilo read in it. In the latest version of the app, what you send to ilo becomes your message in its conversation: your note, and what describes what you sent (its kind, the file’s name and page count, a link’s site, the number of messages and who wrote them, an email’s sender and subject, never for a health document), followed by ilo’s first reply. | To read what you show and suggest the next step (an event, a task, a birthday, a contact); to remember what it learns about your people. | Performance of the contract. |
| Documents and forms: the documents you keep (the file and what ilo read in it), including a form’s filled copy. To fill in a form, ilo reads it on your phone and sends only the fields’ labels and, for a form about a child of the household, the child’s first name and what ilo knows about them, excluding health and private memories. A form attached to a conversation is first handled like any attached photo or PDF. If you ask ilo to fill in or keep the attachment of an email in your mailbox (Gmail, Outlook), that one file is read and kept in your Coffre; a Drive file you add to the Coffre is kept as a linked entry, a copy only if you ask (see “Calendars, mailboxes, Drive and contacts”). | To find your papers again; to pre-fill a form, which you check. | Performance of the contract; your explicit consent to keep a document that contains health information. |
| Voice: the audio of your dictation. | To transcribe what you say. The audio is not kept. | Performance of the contract. |
| La Matinale (in testing): the text of your show (your day in ilo’s words) and its audio. | To read your day to you. | Performance of the contract. |
| Bookings by ilo (in testing, off by default): your request, the details you leave ticked, the merchant’s web pages, your login session on that site. | To book a table or an appointment, or fill a basket, when you ask. | Performance of the contract; your explicit consent, task by task, to pass on an allergy. |
| Price tracking (in testing): the product’s link, its name, the prices seen. | To tell you when the price drops. | Performance of the contract. |
| ilo’s research around an item (“Insights”): what ilo took from the item (an email, a booking, an event, a parcel…) or read again in it, the earlier emails it found in your mailbox about the same thing (not kept: only where the ones it cites are), what it already knows about your family (the city, the children’s ages, the shared memories of the people concerned, without names), your family’s other items around the same dates, what it already told you, the web pages and documents it read, the short card and the page it writes from them. | To point out what can help you around that item (see “What ilo looks up for you” below). | Performance of the contract. |
| Watched pages (“Let me know when…”, in testing, off by default): the link of the page you ask ilo to watch, what you are waiting for, the page’s text read at each check; for a place freeing up, the day, the time, the number of people and the path followed on the site. | To let you know when what you are waiting for shows up on the page (see “Let me know when…” below). | Performance of the contract. |
| Notifications: your phone’s notification token (on Android, the installation ID that Firebase, Google’s service, gives the app), your permission, the text of each notification. | To let you know. | Performance of the contract. |
| Tester feedback: your text, a screenshot if you keep it, the screen, the app version, the device and its system version. | To fix and improve ilo during the alpha. | Our legitimate interest; you choose to send feedback. |
| Crash and error reports (from our servers and the iPhone and Android apps): the type of error, the screen, the last steps without content, the app version, the platform (iPhone or Android), the device model and the iOS or Android version. No name, IP address, screenshot or content. | To find and fix failures. | Our legitimate interest. |
| Usage measures: a few app events (opening, onboarding steps), ilo’s reply time with your country (two letters, never the IP address), AI consumption per family (no content). | To run ilo, measure its speed and control its costs. | Our legitimate interest. |
| Logs: a record of what you authorised (type of action, ids, recipients’ domains, never the content), a security log, and the requests we refused (no or an invalid sign-in, access not allowed, a limit reached), with the IP address turned into a scrambled code, never the address itself. | To prove what you authorised; to protect the service. | Our legitimate interest; our accountability obligation. |
Health. During the alpha, ilo keeps no health information as a memory (an allergy, a treatment, an illness): if it hears one, it does not save it. A medical appointment or a health-related task can be in your calendar or your notes: they stay visible to you alone and are never shared. When you talk about them with ilo, they go through our AI providers like everything else.
A health document you keep. ilo keeps a document that contains health information only with your explicit consent. It then stays private: visible to you alone, never shared, never in a shared conversation. In the app it shows under its real title; notifications stay discreet (“A health document”), since a locked screen can be seen by others. With that same consent, ilo may look up practical information about it for you (validity, renewal, steps to take, reimbursement), never a diagnosis or medical advice. These web searches never contain your name, your family’s or your doctor’s, an address, a phone number, an email or a reference: our code refuses them before anything reaches the search provider. They are never sent as notifications, never read in La Matinale and never shared with other families.
What ilo learns from your documents. When you hand ilo a document (an email forwarded to its address, the share sheet, an attachment in a conversation, a document added to the Coffre, a file of your Google Drive you add to the Coffre, the attachment of an email in your mailbox you ask ilo to keep or fill in), and when you answer its questions while filling in a form, ilo may remember new facts about people already in your contacts: a full name, a child’s school or nursery and class, a postal address, a phone number or an email address. To do so it reads its own transcription of the document (never the file) with an AI model (Anthropic). It never creates a contact from a document, never keeps health information (from a health document it may keep a name or a nursery, never the illness) From your Google or Microsoft accounts, it learns only from what you open with it in a conversation (see “What ilo learns from your accounts”), never from your mailbox on its own. Each fact it keeps appears in your Journal, where you can confirm or forget it.
What ilo learns from your accounts. When you ask ilo, in a conversation, to read an email of your mailbox (Gmail, Outlook) or to answer one, to read a file of your Google Drive, or to find someone in your Google contacts, “Other contacts” or emails, ilo may keep a few facts about people already in your contacts: from an email or a Drive file, a full name, a child’s school or nursery and class, a postal address, a phone number or an email address, read with an AI model (Anthropic) from what it read for you; from your Google contacts, the email addresses, numbers, birthday and postal address it was missing. Importing someone from Google also brings their company and job title, kept as a memory (“Works at …”). Never health, a code, a password or money matters, and never a new contact: someone new is only offered (see “When someone enters your ilo contacts”). An email or a file it only found with a search (its subject, a name, an excerpt) teaches it nothing. What ilo learns this way is visible only to you, even on a contact the other adult sees, until you share it from the contact’s page; each fact appears in your Journal, where you can confirm or forget it, and what ilo added to a contact while answering you can be undone with “Undo”. The automatic reading of your mailbox never teaches ilo anything about people: it only makes the items you see (parcels, trips, appointments, emails to handle). From your calendar, ilo never learns on its own: when an event’s title is the birthday of someone in your contacts whose birth date ilo does not know, it offers “Keep Victoria’s birthday?” and keeps it only if you tap, visible only to you. If you disconnect an account, what ilo learned from it stays in your contacts, visible only to you, until you forget it. During the alpha, this learning is turned on family by family.
What ilo learns from your conversations. After a reply, in the background, ilo reads your latest message again to find what is worth remembering about you and your people for the long run: a taste or a passion, a routine (an activity on Wednesdays), a child’s school or club, a nickname, a birthday, a milestone (a new job, a move), a pet, a place you loved, a plan (“we’re going skiing in February”). It keeps only what you said or confirmed yourself, never what only its reply says, five facts at most, and only about people already in your contacts: it never creates a contact, and keeps nothing about a child outside your close family. It never keeps health information, a code, a password or an ID number, money matters (income, debts, a bank), religion, politics, someone’s private or love life, a conflict between people, a phone number or an email or postal address; on top of that instruction, our code drops, before anything is saved, what looks like health information, a code or one of these topics, and what ilo already knows. To do so, your message, ilo’s reply and the one before it (to understand a short answer to its question), with what it already knows about the people concerned (health excluded), are sent to an AI model (Anthropic). In a conversation where ilo read an email from your mailbox (Gmail, Outlook, or an item that may come from one, such as a parcel, a trip or a kept document), a file of your Google Drive, your Google contacts or your calendar, only your message is sent, never ilo’s replies, which may quote what it read: ilo learns nothing from them, and a short answer that needs its question is not read. In such a conversation, what ilo saves about your people, even what you said yourself, is visible only to you until you share it. In a shared conversation, it keeps only what the person writing says about themselves or the family’s children, and reads only their shared memories. These memories are saved like the ones you dictate to ilo, visible under the same rules (see “Within your family”); each one appears in your Journal, where you can confirm it (“That’s right”) or forget it (“Forget”).
Within your family. The people you add as family (children, close family) are visible to the household’s adults, with what ilo knows about them, except private memories. Your calendar, emails, Drive, notes, documents and conversations stay yours until you share them. What ilo learns from your mailbox, your Drive, your Google contacts or your calendar stays visible only to you until you share it.
What ilo looks up for you (“Insights”). When an item lands in ilo (an email, a booking, an event, a parcel…), ilo may look a few things up around it to help you: a cheaper option, a missing document, a deadline. To do so it may search the web (through Tavily, or through Anthropic when Tavily is unavailable and always for an item from your mailbox or your calendar, or once the research has read your mailbox, your calendar or your documents), read public web pages, and check the weather (Open-Meteo), your calendar around the event and the documents you kept, never those that came from your mailbox (Gmail, Outlook) or your Google Drive nor, except for you alone and with your consent, health ones (see “A health document you keep”); no search is about a diagnosis or a treatment. To make the research yours, it may also read again the item it is about: the email it came from (read again from your mailbox, for you alone, its access codes removed, and not stored; never a health-related email), the description of the calendar event, or what you shared with ilo. When the item refers to earlier emails (an invoice you are asked for again, a reminder, the other half of a booking), it may also search your mailbox (Gmail, Outlook) and read up to three that match, for you alone. It never looks in spam or the trash, never reads a health-related email as ilo’s mail sorting judges it (a hospital’s invoice counts as paperwork, and the research never names a treatment, a department or a condition), and never opens attachments. It does not keep these emails: only where the ones it cites are (the mailbox, the sender’s public name, the day), kept with the research so that you can attach them to a reply in your conversation about the item. Research that read your mailbox is deleted as soon as you disconnect it. It may also look at your family’s other items around the same dates (trips, parcels on their way, tasks, events, the documents you kept), the people it knows (their role and the memories it keeps about them) and what it already told you: to spot, for instance, a parcel arriving while you are away or an identity card that expires before a trip. A date clash between two of your items is spotted by our code, not guessed. Research seen by several people never searches your mailbox, never reads an email or an event’s description again, and never builds on research that read a mailbox. To judge whether research is worth it and to make it useful, ilo also uses what it already knows about your family: the city, the children’s ages and, for an item about a person, the memories it keeps about them (their tastes, for instance). In this information, names are replaced by roles (“the child”); nothing about health and no private memory is used, and research seen by several people uses only what each of them can see. This is never sent with a web search. Web search queries never contain the name of anyone in your family or your contacts, an email address, a phone number, a booking reference, a street address or your employer’s name: our code checks this before anything is sent. Like a conversation, this research goes through our AI providers. The result is kept encrypted, seen only by the people who see the item (it quotes nothing from a document they cannot all see), and deleted 30 days after the item ends. ilo sends nothing and books nothing: it suggests, you decide.
Let me know when…
(Watched pages, in testing, off by default during the alpha.) You can ask ilo to watch a public web page: a course opening for registration, a date added, a table, a court or a class freeing up. Nothing is watched until you tap “Watch”.
How ilo reads it. A page is read twice a day, as a plain visitor would: no cookie, no login, following the rules the site sets for robots. A page that only shows in a browser, and a place on a booking site, are opened in a browser on our servers (Browserbase, Frankfurt), still with no cookie and no login; a place is checked about every 3 hours, from 8 am to 10 pm, until its day. When the page has changed, an AI model (Anthropic) reads its text and what you are waiting for to judge whether it has happened, without your name or the page’s link. For a place, the first time (and if the site has changed), an AI model (Anthropic) goes through the site to the day’s times; after that, ilo retraces that path without AI.
What is kept. The link, what you are waiting for, the page’s text and, for a place, the day, the time, the number of people and the path followed are kept encrypted with your family’s key; only the site’s name, the watch’s state and its dates stay in the clear. A watch is visible to you alone, not to the household’s other adult.
Limits. A family has 5 active watches at most. Each one ends on the date chosen (60 days at most) or the first time ilo sees what you were waiting for: you then get a single notification. ilo never acts for you: it does not register or book; opening the page is up to you.
“Autour de toi”: the public facts ilo keeps
While helping you, ilo finds public facts on the web: a strike, a closure, an event, registrations opening. It finds them in two ways: in its research around an item (see “What ilo looks up for you”) and in the results of the web searches it runs during a conversation. It may keep some of them and read them again before searching again, for families near the same place. A search Anthropic runs gives none.
From a conversation. After a reply for which ilo searched the web, an AI model (Google Gemini) reads only the search results (their titles, links and snippets), with your household’s town and today’s date: never your message, the query sent to the search engine or ilo’s reply. It draws three facts at most from them, checked like the others (the quote must be in its result’s snippet). A reply you stopped adds nothing.
What a fact is. One or two sentences, with its public page, a short quote from that page, a town and dates. Our code checks that the quote is on the page, and sets aside a fact that holds the name of someone in your family or your contacts, an email address, a phone number, a street address, a booking reference, your employer’s name or health information.
A fact holds no person, no family, no message and no question from a parent: nothing in a fact says which family it was found for. To measure the service, we count per family how many facts were kept or read again, without their content.
Never from your mailbox. A fact is never taken from your mailbox (Gmail or Outlook): research around an email in your mailbox, or research that searched your mailbox, may read the kept facts, never add to them. A conversation that read an email from your mailbox (or an item that may come from one, such as a parcel, a trip or a kept document, or an item whose research searched your mailbox), your Google Drive or your Google contacts never adds a fact again.
How long. A fact expires the day after its end date, or 30 days after it was last found when it has no date; it is deleted 30 days after it expires. We can withdraw a wrong fact: it is then never used again.
ilo never asks you to share anything with other families.
The waitlist
On withilo.com, you can sign up to try ilo. You don’t need an account, or an iPhone, to sign up. This section covers that form only.
- About you: first and last name, email (where we send your invitation to try ilo), type of phone (iPhone, Android, other), calendar (Google, Apple, Outlook, other), country and city.
- Your Google address, only if your calendar is Google: during the test, Google requires testers’ addresses to be on a list before they can connect Google Calendar.
- Your partner, if you add them: first name, type of phone, email, calendar and, for Google, their Google address. These are used only to invite them: they choose whether to join, and get nothing else from us unless they say yes.
- What you would love ilo to do for you, if you write it.
- Whether you want news on what’s next for ilo (beta, launch): the box is unticked unless you tick it.
- The version of the notice shown next to the button, and the time you signed up.
Why. To choose the testers and send them their invitation; then, during the test, emails about it only: new versions, short surveys. News on what’s next for ilo only if you ticked the box. No email is sent when you sign up: the first one is your invitation.
Legal basis. Choosing testers and inviting you (and the person you add): steps taken at your request before you join the test, and our legitimate interest in running it. News on what’s next: your consent, which you can withdraw at any time by writing to us.
Who sees it, and where. It is stored in our database in Frankfurt (Supabase), reachable only by our servers. Dany Agostinho and the people we invite to help run the test read it in our admin console; every view and every export is logged. It is not shared with anyone else, not sold and not used for advertising.
Against spam, the form has a hidden field that only robots fill in, and a limit on sign-ups per connection. To count them, your IP address is turned into a scrambled code (a hash), kept next to a counter: the address itself is never stored or written to our logs, and the code is not linked to your sign-up. The site sets no cookie and loads nothing from other sites.
How long. Until 12 months after the beta ends, or earlier if you ask. Your partner’s details are deleted when they decline or don’t answer. Signing up again with the same email updates your answers. To correct or delete your sign-up, write to hello@withilo.com.
Visits to this site
On the withilo.com home page (not on these legal pages, and not in the apps), we count visits with our host’s measurement tool, Vercel (Web Analytics). No cookie is set and nothing is loaded from another site.
What is recorded for each visit. The page viewed and the parameters of its link (such as ?ref=…), the site you came from, the country, region and city worked out from your connection, the system and browser, the type of device and the time. So that one person isn’t counted twice, Vercel works out a hash from the request: it is discarded after 24 hours and cannot follow you from one site to another. We only look at totals.
Why, and legal basis. To know how many people discover ilo and where they come from: our legitimate interest.
Calendars, mailboxes, Drive and contacts
Google Calendar. If you sign in with Google, ilo asks for access to your calendar’s events (calendar.events): it reads, creates, updates and deletes events on your primary calendar, when you ask or when you accept a suggestion. It never touches your calendars’ settings or sharing. Events are read when needed and are not copied to our servers; a reply from ilo that mentions one is kept with the conversation.
Apple Calendar. It is read on your iPhone. We only receive an event if you share it with another adult or, for the time of one reply, if ilo needs it to answer you; it is not kept separately. What ilo adds to your Apple Calendar is written by your iPhone. On Android, ilo uses Google Calendar only: the app does not read the phone’s calendar.
Gmail (if you connect it; during the alpha, only the testers we add at Google can connect it). ilo asks for two permissions: read your email (gmail.readonly), to recognise parcels, trips, appointments and emails that need you, to spot where a rental’s access code is, and to find an email when you ask; manage drafts and send them (gmail.compose), to write a draft when you ask, sent only after you tap “Send”, with a few seconds to cancel. When you connect, ilo reads the emails of the last 30 days, then new ones once a day and when you open the app. Promotions, social notifications, newsletters, codes and spam are recognised from their headers and not opened. When ilo looks something up around an item (see “What ilo looks up for you”), it may read again the email the item came from and search your mailbox for earlier emails about the same thing, for you alone and never a health-related one; it keeps only where the emails it cites are, not the emails. Attachments are not opened, except calendar invitations (.ics), those you ask ilo to attach to a draft, and the one you ask ilo to fill in or keep in a conversation (“look at the school’s email and fill in the form”): that one file is then read and kept in your Coffre, private, like a document you add there. ilo does not look for documents to keep in your mailbox on its own; it only notes where a rental’s access code is, never the code (see “A rental’s access codes” below). It never learns from it on its own: from an email you open with ilo in a conversation, it may keep a few facts about people you know (see “What ilo learns from your accounts”); when you ask ilo to write to someone, it may look up their address in your emails’ senders and recipients (the “From”, “To” and “Cc” lines of the emails that name them, never their subject or text; see “Google Contacts” below). The same Google screen also offers Google Contacts, which you can leave unticked.
To sort an email, ilo sends an AI provider its sender, subject and the beginning of its text; to extract a parcel, a trip or an appointment, the relevant part (in both cases, with a rental’s access codes removed, see below); when you ask ilo to read an email, the email; to fill in or keep its attachment, that file. We don’t keep your emails: an email is read while it is processed, then only what ilo extracted is kept (parcels, trips, appointments, short summaries of emails that need you, where an access code is), and the attachment you asked ilo to keep.
A rental’s access codes. In an email of your mailbox (Gmail, Outlook) sent by a travel or accommodation site (Airbnb, Booking…) or recognised as a trip, whose sender is authenticated (a forged email offers nothing), our code spots while reading it, without AI, a key box, door, gate, garage, alarm or Wi‑Fi code. Such a code is removed from the email’s text before ilo’s automatic reading passes it to an AI model (to sort the email, read the trip, or look things up around it), and ilo’s research points to your Vault instead of repeating it. ilo never keeps the code, nor a fingerprint of it: only where it is (the email and the code’s rank in it) and the trip that goes with it. On iPhone, it offers “Keep the code in the Vault?”; if you tap “Keep”, it reads that email again in your mailbox, finds the code there and sends it to your phone alone, in that one response, without saving it, writing it in our logs or caching it; your phone writes it to the Vault. Only the mailbox’s owner sees the offer, never the other adult. It is no longer offered once the trip is over (14 days after the email when there is no trip) and is deleted with its email’s processing data. No notification from ilo contains a code. An email forwarded to ilo’s address or shared with it is not covered: its original is not kept, so ilo could not read it again.
When you turn off Gmail (Settings › Connectors › Google), ilo stops reading and deletes the summaries and processing data at once, and ilo’s research about its emails or that read your mailbox (“Insights”) too; its access at Google is revoked when Gmail was the last Google permission you used with ilo (see “One Google connection” below). Parcels, trips, appointments and documents already added stay until you delete them. Your “every time” choices (a sender’s domain name and your answer, no email content) stay too, so ilo does not ask again if you reconnect your mailbox; write to hello@withilo.com to remove them. What ilo learned from emails you opened with it stays, visible only to you, until you forget it (see “What ilo learns from your accounts”).
Outlook / Hotmail (if you connect it): ilo asks to read your email (Mail.Read), handled like Gmail, and to write drafts and send them (Mail.ReadWrite, Mail.Send), to write a draft in your Outlook drafts when you ask, sent only after you tap “Send”, with a few seconds to cancel. If you connected Outlook before these two permissions, ilo only reads until you allow sending. When you disconnect it, we delete the access, the processing data and ilo’s research about its emails or that read your mailbox (“Insights”); the permission stays listed at Microsoft until you remove it in your Microsoft account.
Google Drive (if you connect it; ilo asks in a conversation the first time you need it, after a short explanation). ilo asks for two permissions: see and download your Drive files (drive.readonly), to find and read a file when you ask (“find Léo’s vaccination certificate in my Drive”, “what does the supply list say?”); files ilo creates (drive.file), to put in your Drive a file you ask for. A file is searched and read only when you ask, in memory, for that answer: ilo does not index your Drive, and never reads it in the background. To answer, the file’s text goes to our AI provider; ilo’s reply is kept with the conversation. From a file it read for you, ilo may keep a few facts about people you know (see “What ilo learns from your accounts”).
When you ask ilo to add a Drive file to your Coffre (in the latest app, after you confirm with one tap on a card), it keeps a linked entry: the file’s title and what ilo read in it (its kind, who issued it, key dates such as an expiry, a one-line summary) with a link to the file, which stays in your Drive. ilo fetches the file from Drive again only when it needs it (to fill it in, attach it to a draft or read a page). It keeps a copy only if you ask (“keep a copy”), when you share it with the other adult, who cannot see your Drive, or when you keep a filled-in copy of a form. Like any document you keep, it may teach ilo a few facts about people you know (see “What ilo learns from your documents”). A file that contains health information is kept only with your explicit consent (see “A health document you keep”).
What ilo writes in your Drive. Only files it creates at your request (a filled-in form, a PDF, a Google Doc or Sheet it writes for you, such as a packing list or a babysitting schedule), in a folder named “ilo”, and only after you confirm with one tap on a card that shows what it will write. To change an existing file, ilo makes an edited copy in its “ilo” folder (“… (edited by ilo)”) and leaves the original untouched. ilo never deletes your files: right after a write, “Undo” moves only the file ilo has just created to your Drive’s trash. The files ilo creates are yours and stay in your Drive, even if you turn off Drive or delete your ilo account.
Without any Drive permission, you can also attach a Drive file to a conversation through your iPhone’s Files app: ilo then receives it like any other attachment.
Google Contacts (if you allow it; it is offered on the same Google screen as Gmail, and can be allowed on its own). ilo asks for two permissions: see your contacts (contacts.readonly) and see your “Other contacts” (contacts.other.readonly), the people Google saves by itself from your emails (people you wrote to or who wrote to you) without you adding them to your contacts; ilo reads their name, email address and phone number. When you ask ilo to write to, invite or call someone (“email Léo’s teacher”, “invite Marie”), or ask for their number, birthday or address, ilo looks that person up: in your ilo contacts, then your Google contacts, your Other contacts, your emails’ senders and recipients (Gmail, Outlook) and your iPhone’s contacts. It shows you who it found; if several people match, you choose. Only the matching entries are read, at the time of your request, in memory: ilo never copies your address book; it keeps only what is described below. Lookups are never made in a shared conversation.
When someone enters your ilo contacts. When the person ilo finds is already in your ilo contacts, it adds the details it was missing (an email address, a number, a birthday, a postal address), visible only to you, with “Undo” and a line in your Journal. Someone new is only offered: under ilo’s reply, “+ Add to my contacts”, and the contact is created only if you tap. In Contacts, “Import from Google” lets you search and tick the people to add, 25 at most at a time (there is no “select all”): ilo reads each ticked person again from Google and adds their name, emails, numbers, birthday, postal address, company and job title, or completes the ilo contact they already are with what it was missing, visible only to you.
iPhone contacts. If you allow it, ilo reads your iPhone’s contacts on the phone, at the time of a request, for the name you asked about (if you shared only some contacts with ilo, only those), and the phone sends at most ten matching people for that one answer. They are not kept, unless you add the person as above. The app asks for this permission the first time it needs it. On Android, ilo does not read the phone’s contacts for these lookups.
One Google connection. Gmail, Google Contacts and Google Drive share one connection to your Google account: Google lists ilo once. In Settings › Connectors › Google, each one has its own switch, and turning one off stops ilo using it at once. Turning off Gmail also deletes the summaries and processing data, as described above. Turning off Drive cancels the Drive cards waiting for your tap and removes the Coffre’s entries linked to your Drive (the copies you asked for stay, and so do the files ilo created in your Drive). Turning off Contacts stops the lookups (the people already in your ilo contacts stay, with what ilo learned). The permission stays listed in your Google account until you turn off the last one or tap “Disconnect everything”, which revokes ilo’s access at Google. Deleting your account revokes it too. You can also remove ilo from your Google account at any time.
Google API Services — Limited Use. ilo’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In other words: data received from Google (calendar, email, Drive files, contacts) is used only for the features you see in ilo. It is never used for advertising, never sold, not used to train generalised AI models, and only passed to the providers those features need. No one reads it, except with your permission (for example to look into a problem you report), for security, or where the law requires it.
Who processes your data, and where
ilo is hosted in the European Union: server in Frankfurt (Vercel) and database in Frankfurt (Supabase, Central EU). To work, ilo uses the following providers, who act on our behalf:
| Provider | What it does | Where |
|---|---|---|
| Vercel | Hosts ilo’s server and this site: every request goes through it. Also counts visits to the home page. | Frankfurt (EU); US company. Visit counts: location to be confirmed |
| Supabase | Database, sign-in, files (documents, La Matinale audio, feedback screenshots). | Frankfurt (EU) |
| Anthropic | AI model (Claude): conversations with your family’s context, titles, reading emails, bookings by ilo, ilo’s research around an item, watched pages; web searches when Tavily is unavailable, and every web search made in a conversation or a research that has read your mailbox, your calendar, your Google Drive or your Google contacts (the query, with your household’s time zone, never your city or country); in a conversation, the text of a Drive file you ask about and the people ilo finds for you (name, the address or number needed); what ilo learns from a document you hand it, from an email or a Drive file you open with it, or from a conversation. | United States |
| Google (Gemini API) | AI model: sorting and summarising emails (with access codes removed), reading what you share, documents and forms, a scanned Drive file or one you add to the Coffre; choosing the items ilo looks things up around; the public facts drawn from a web search’s results in a conversation (“Autour de toi”). | Global, no commitment to process in the EU |
| Mistral AI | Voice dictation (Voxtral); conversation model when we choose it. | Global endpoint, no location commitment |
| Gradium | La Matinale’s synthetic voice: the show’s text. | EU |
| Tavily | Web search, first: the queries ilo writes, in a conversation or for its research around an item (they can name a place, a date, an activity); never a query made after reading your mailbox, your calendar, your Google Drive or your Google contacts. | To be confirmed |
| Browserbase | Browser for bookings by ilo and some watched pages (in testing). | Frankfurt (EU); US company |
| Cloudflare | Domain name and ilo’s address: the emails you forward pass through it, not kept there by us. | Global network |
| Apple | Sign in with Apple; notifications on iPhone (the title and text of each, your iPhone’s token). | Apple |
| Google (Firebase Cloud Messaging) | Notifications on Android (the title and text of each, the app’s installation ID). | |
| Apple (TestFlight) and Google (Firebase App Distribution) | Test builds of the iPhone and Android apps: each tester’s email address, to invite them to install the app. | Apple; Google |
| Resend | Emails sent by ilo: invitations, event shares (.ics), the welcome email for ilo’s address. | United States (to be confirmed) |
| Sentry | Error and crash reports from our servers and the iPhone and Android apps, with no name, IP address or content. | Frankfurt (EU) |
| Open-Meteo | Weather: your city’s coordinates or postal code, your trips’ destinations, the place of an item ilo looks things up around, the town of a public fact ilo keeps. | To be confirmed |
Google, Apple and Microsoft are also involved as your own accounts, when you sign in with them or link them to ilo (your Google calendar, mailbox, Drive and contacts are read from Google, and what ilo writes in your Drive is stored by Google). A merchant where ilo books for you receives the details you approved and handles them under its own policy. Once ilo is published on the App Store or Google Play, the store will deliver the app and its updates with your own Apple or Google account, under its own terms.
Your city. To find your household’s city, the app uses your phone’s location service, which receives your position or the city name you type: Apple’s on iPhone; on Android, the system’s, with your approximate position only (it is Google’s service on phones that have Google services).
Training. We do not train any AI model with your data. Anthropic does not use data received through its API to train its models; it keeps it under its standard commercial terms (we have no zero-retention agreement). Google does not use what ilo sends to the paid Gemini API to improve its products. Mistral AI says it does not use what is sent to its API to train its models. Gradium says it does not use the content it processes to train or improve its models. Tavily’s policy lets it use the queries it receives to improve its service: so a web search made in a conversation or a research that has read your mailbox, your calendar, your Google Drive or your Google contacts never goes to Tavily; Anthropic runs it. We are still checking how long Google, Mistral, Gradium and Tavily keep what they receive, and will state it here.
Transfers outside the EU. Some providers are in the United States or process data outside the EU. These transfers must rely on the EU–US Data Privacy Framework or on the European Commission’s standard contractual clauses; we are checking each provider’s mechanism during the alpha and will state it here. The data processing agreements with Browserbase and Gradium are not signed yet.
To show some images, the app loads them directly from the website that publishes them, which then sees your phone’s IP address: the picture of a product whose price you track (on iPhone and Android) and, on iPhone, the icon of a website ilo mentions and a Google account’s profile picture.
How long we keep it
| Data | How long |
|---|---|
| Account, family, contacts and memories, notes and tasks, parcels, trips, dates, kept documents, shared events | Until you delete them, or delete your account. |
| Conversations | Until you delete them (erased 7 days later). A conversation with no activity for 12 months is deleted. |
| A forgotten memory, erased private contacts | 7 days in a bin, then deleted. |
| What ilo read in a share, a forwarded email, a photo or a PDF attached to a conversation | 30 days. The original is never kept. An email from an unknown sender: 7 days unless you confirm it is you. |
| In the conversation of what you send to ilo: your message, what describes what you sent, and ilo’s first reply | With the conversation, beyond the 30 days of what ilo read. “Delete what I sent” erases what describes it at once; ilo’s reply stays until you delete the conversation. An email from an unknown sender you turn down (“No”): its conversation is deleted with it. |
| Suggestions from your emails (add an appointment, a task) | 7 days after the event’s date. |
| Google Drive files ilo reads, emails it reads for you in a conversation or finds in your mailbox while looking things up around an item, people it looks up for you (Google, emails, iPhone) | Not kept: read for the answer only. What is kept is ilo’s reply (or its research, with where the emails it cites are), a file you add to the Coffre, a person you add to your contacts and the few facts ilo learned (visible only to you, until you forget them). |
| A Drive write waiting for your tap (a file to save, a new Doc or Sheet, an edited copy) | 7 days, then deleted (a photo or PDF from the conversation to save is kept encrypted until then). |
| Offers to keep a document | 7 days for a file received at ilo’s address (30 days for those made from Gmail or Outlook before 24 October 2026). |
| Email summaries and processing data (Gmail, Outlook) | 30 days after the email’s date; deleted as soon as you disconnect. Technical log without content: 180 days. |
| An offer to keep a rental’s access code (where the code is in the email, never the code) | With its email’s processing data: 30 days after the email’s date, or as soon as you disconnect the mailbox. No longer offered once the trip is over (14 days after the email without a trip). |
| A code offered to the Vault in a conversation | Our servers do not keep the code. To mask it, its length and a fingerprint encrypted with your family’s key: erased as soon as you answer (“Keep” or “No thanks”), otherwise with the conversation. |
| Titles of the Vault’s entries sent with your messages (iPhone) | Not kept: read for the answer only. |
| La Matinale (text and audio) | 7 days. |
| Bookings by ilo | Result: 30 days after the end. Login session on the site: 30 days at most. A login released from the Vault: 10 minutes at most. |
| A stopped price tracking | 30 days after it stopped. |
| ilo’s research around an item (“Insights”) | 30 days after the item ends (30 days after the research when the item has no end). Research that read your mailbox, with where the emails it cites are: deleted as soon as you disconnect that mailbox. |
| Watched pages | Until the watch ends (60 days at most), then 30 days. A watch offered and never confirmed: 7 days. |
| “Autour de toi” public facts (no person, no family) | 30 days after they expire (the day after their end date, or 30 days after they were last found when they have no date). |
| “Undo” on one of ilo’s actions | 24 hours at most. |
| Tester feedback | 180 days. |
| Crash and error reports | As per Sentry’s plan (30 days on the free plan, to be confirmed). |
| Usage measures | App events: 25 months. Reply times: 90 days. Detailed AI consumption: 30 days, then monthly totals, detached from you when you delete your account. |
| Security log | 12 months. |
| Refused requests (no content, IP address scrambled) | 30 days. |
| Record of what you authorised (no content) | 3 years. When you delete your account, it is detached from your identity (pseudonymised). |
| Notification token | Until you sign out of the app or delete your account. |
| Waitlist sign-ups (withilo.com) | Until 12 months after the beta ends, or earlier if you ask. A partner’s details: deleted when they decline or don’t answer. |
| Hosting logs | As per Vercel’s plan (to be confirmed). |
| Visits to the home page | Visit hash: 24 hours. Totals: at least 12 months (the period our Vercel plan guarantees); Vercel may keep them longer. |
| A few technical records: the team’s access to admin tools, a record that a member left a family (their email and the date) | No period set yet: we will set one before the end of the alpha. |
Security
Traffic between the app and our servers is encrypted (HTTPS). In the database, most content (messages, contacts and memories, notes, documents, email summaries…) is encrypted with a key specific to your family (AES-256-GCM), itself protected by a master key. Some data is not yet encrypted at that level, for example birth dates, times, settings and the text of the parcel and trip cards on the home screen (a destination, an item’s name).
Our servers hold these keys: they need them to run ilo. Encryption protects your data if the database alone were to leak; it does not technically prevent us from accessing it. We do not look at your content, unless you ask us to (for example to look into a problem you report) or the law requires it. The team reads the feedback you send; each opening is logged.
The Vault stays on your phone (your site logins, your official numbers, your signature). On iPhone, it is kept in the device’s keychain, opens with Face ID, Touch ID or your passcode, and is not synced with iCloud; it stays in the keychain, even after you sign out or delete your account, until you erase it in the app (“Erase my vault”). On Android, it is encrypted with Android Keystore keys, which never leave the phone, opens with your fingerprint, your face or your phone’s PIN, and is excluded from backups; it is erased when you sign out or delete your account. Our servers do not receive what the Vault holds (on iPhone, only its entries’ titles go with your messages, see below). The one exception, while bookings are being tested: a login you release for a booking (with Face ID, Touch ID or your passcode on iPhone; your fingerprint, face or PIN on Android) is sent for that single use, kept encrypted for 10 minutes at most, then erased; it is never shown to the AI model.
Codes you give ilo (on iPhone). If you write a code or a password to ilo (the door code at your parents’ place, the Wi‑Fi, a site’s login, a social security number), or if an email it reads for you contains one, it offers to keep it in your Vault. The code then goes only to your phone, which writes it to the Vault if you tap “Keep”; our servers record it nowhere else, neither in a log nor in a measurement. Like any message, yours went through our AI provider for ilo to answer. Once the code is kept, it is replaced with “•••• (in the Vault)” in the stored conversation and its title: to find it without keeping it, ilo noted only its length and a fingerprint encrypted with your family’s key, erased as soon as you answer. If you don’t keep it, your message stays as it is in the conversation, like the others. ilo never saves a code as a note or a memory, and never makes these offers in a shared conversation.
When you ask ilo for a code (“what’s the code at Grandma’s?”), it never gives it to you: it opens the entry in your Vault, on your phone, behind Face ID. To do so, with each of your messages in a private conversation, the app sends the titles of your Vault’s entries (“Door code at Grandma’s”, a login’s site, the person a number belongs to), never a code, a login or a number. These titles are shown to the AI model only when ilo looks for an entry, and are never saved or written in our logs.
The login sessions ilo keeps for bookings (“Connected sites”, which the Vault also shows) are not in the Vault: they are on our servers, encrypted with your family’s key, for 30 days at most, and never hold a password.
No protection is perfect. If you find a vulnerability, write to security@withilo.com.
What we don’t do
- No advertising, and no sale of your data.
- No advertising trackers or third-party audience measurement in the apps. On Android, the app includes Google’s notification service (Firebase Cloud Messaging, with what it needs to work), without Google Analytics: to send you notifications, it creates an installation ID for the app at Google.
- This site sets no cookies and loads nothing from other sites.
- No training of AI models with your data.
Your rights
You have the right to access your data, correct it, erase it, restrict its use, object to processing based on our legitimate interest, receive it in a readable format (portability), withdraw a consent at any time, and give instructions about it after your death.
- A copy of your data: Settings, export as JSON. It contains your main data, including your documents (their title, what ilo read in them and each page’s text; the files themselves stay in the app); some is not included yet (for example parcels, trips, dates to celebrate, price tracking and watched pages): write to us to get it.
- Corrections: in the app, or by asking ilo.
- Deleting your account: Settings › Account › Data and privacy › Delete account, confirming with Face ID, Touch ID or your passcode on iPhone (or your email if the iPhone has no passcode), typing your email on Android; or without the app, by email. It is all explained at withilo.com/delete-account. Your account, your private data and your Google access are deleted; Outlook access too. The files ilo created in your Drive stay there: they are yours. If another adult stays in the family, the messages you wrote in your shared conversations and what you had shared (lists, memories about the family) stay for them. The record of what you authorised is kept for 3 years, detached from your identity.
- By email: hello@withilo.com, for anything else. We answer within one month.
You can lodge a complaint with the CNIL (cnil.fr), the French data protection authority, or with the authority of your country.
Children and minimum age
ilo is for adults only: you must be 18 or older to create an account, and you confirm it when you sign up. Children have no account. What you tell ilo about your children is part of your family’s memory and gets the same protection as everything else. If you believe a minor has created an account, write to us: we will delete it.
Changes
This policy will change as ilo does. Each version has a number and a date, at the top of this page. When it changes, the app asks you to accept the new version. If we ever add audience measurement to the app, it will be cookieless and run by us, and this page will say so before it starts.
Contact
Dany Agostinho — hello@withilo.com. Alpha terms: withilo.com/terms. Legal notice: withilo.com/legal-notice.