Privacy
Castalie is a conversational strategy coach: you describe your company, it builds a tree of objectives with you. This page says what that means for your data.
What we keep
- Your conversations and your objectives. The messages you write and the tree they produce are stored so that you find them again from one visit to the next.
- Your sign-in identity. Depending on the method you choose: your email address, and the name that Google or Microsoft passes on to us; or, if you sign in with a password, a salted digest of it, never the password itself.
- A session. A technical cookie carries your session once you are signed in. Nothing is recorded before you sign in: the coach only speaks inside a workspace.
Who else sees your data
- Anthropic processes the written content of your conversations: it is the model that answers.
- OpenAI receives your voice — the recording when you dictate a message, and the audio stream in voice mode — to transcribe it and answer.
- Microsoft (Azure Communication Services) receives your email address to send you a sign-in link.
- Google or Microsoft, if you choose to sign in through them.
Your data is neither sold nor handed over for advertising purposes.
Your rights
You may ask for access to your data, its correction, its deletion, or object to its processing. Write to us through the contact form, quoting the email address tied to your account.
What Ben keeps, and what it does with it.
Ben answers the phone calls and the messages of an agency that uses Castalie, and books appointments in its advisors' calendars. This part is for the people who call or write to such an agency, and for the advisors who connect their calendar.
What Ben keeps
- Calls. The caller's number, the time and length of the call, and its transcript, sentence by sentence. The call is recorded, and Ben says so when it picks up. The recording stays with the telephony provider: Castalie keeps only its reference, to play it back when a member of the agency asks for it. A voicemail left when nobody can answer is kept the same way.
- Messages. For an e-mail received in the agency's mailbox: its sender, its subject and its date. Its text is read when the e-mail is sorted, and is not stored. For an SMS or a WhatsApp message, when the agency uses those channels: its text, and Ben's reply.
- Contacts. The name, phone number and e-mail address of the person, as they give them or as the agency already knows them.
- Requests and appointments. What each request is about, its category and its urgency, the notes of the agency's team, and the appointments taken: their kind, time, place and advisor.
All of it is kept in the agency's own workspace database, with the host named in the Legal notice.
Who else sees this data
- Twilio (United States) carries the phone calls — and the SMS, when the agency uses them — and keeps the call recordings.
- OpenAI (United States) hears the caller and gives Ben its voice: the audio of the call goes through OpenAI while the call lasts, with the agency's name, what the agency wrote for Ben to know, and the caller's name when the agency knows it. OpenAI also transcribes the call.
- Anthropic (United States) reads a call's transcript, an e-mail or a message to sort it — its category, its urgency, the next step — and to draft Ben's written replies.
- Meta (WhatsApp) carries the WhatsApp messages, when the agency uses that channel.
- Google or Microsoft hold the calendar of the advisors who connect it, and the agency's Gmail or Outlook mailbox when the agency connects it: see below.
- The agency's business software, when the agency connects it (today, Lojii): Ben looks up the client's file there, writes there the tasks the agency validates or lets Ben validate on its own, and files there an e-mail's sender, subject and date.
The advisors' calendars
An advisor can connect their own Google or Outlook calendar from Ben's Calendar screen, so that appointments are only booked when they are free. Castalie then has access to:
- When you are busy. The busy periods of your calendar, read when a slot is being looked for, and not stored. Never the title, the guests or the content of your events.
- The events Castalie writes. For each appointment taken: its title, time and place, the request's reference, the agency, and the name, phone number and e-mail address of the person to meet. Nobody is invited: your calendar sends nothing to that person. Castalie deletes the event if the appointment is cancelled, and touches no other event.
- Your address. The e-mail address of the Google or Microsoft account you connect, to show which calendar is connected.
Nothing else from your account: not your e-mails, not your contacts, not your files. Ben tells the person the free slots it found, on the phone or in writing: on the phone they go through OpenAI, in writing through Anthropic, like the rest of the conversation.
How the access is kept. The authorisation your calendar provider gives Castalie is encrypted by the application before it is stored in the workspace's database. The short-lived access keys it yields stay in the server's memory and are never written down.
Disconnecting. The Disconnect button of the Calendar screen erases the stored authorisation at once: Castalie can then neither read nor write your calendar. The appointments already written stay in your calendar, where you can delete them. To also withdraw the authorisation at Google or Microsoft, remove Castalie from your account's third-party access: Google, Microsoft personal account, Microsoft work or school account.
The agency's mailbox
When an agency connects its mailbox — Outlook by its director, from the e-mails' settings, or Gmail through its Castalie consultant — Castalie reads, read-only, the e-mails that arrive in its inbox, to turn each one into a request:
- What is kept. The sender, the subject and the date of each e-mail, on the request it became.
- What is read and not kept. An e-mail's text, read when it is sorted — it then goes through Anthropic — and never stored.
Castalie reads the e-mails, and sends replies from the agency's own address only once its director allows it — a reply written and sent by the AI says so in its signature. It never moves, deletes nor marks an e-mail as read; the only thing it adds to a mailbox is the copy of its reply in the sent folder, when the provider does not file it. The access asked is reading, and sending once allowed (Outlook: Mail.Read, and Mail.Send once allowed; another mailbox: IMAP and SMTP with an application password). The authorisation is encrypted before it is stored, like a calendar's, and the Disconnect button of the e-mails' settings erases it at once.
Google user data
Castalie's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
In practice: this data serves only the features described above. It is not sold, not used for advertising, and not used by Castalie to train artificial intelligence models.
What Castalie receives from Google. Only what the features above need:
- Google sign-in. Your e-mail address, your name and the address of your profile picture, to open your account and show your workspace who you are.
- Google Calendar. For an advisor who connects it: the busy periods of their primary calendar, the address of the connected account, and the identifier of each event Castalie creates in it.
- Gmail. For an agency that connects its mailbox: the e-mails that arrive in its inbox, read-only.
Who it is shared with. Castalie does not sell Google user data, and does not share, transfer or disclose it for advertising or for any purpose other than the features described above. Only the following receive it, each for the part it needs:
- OVH (France) hosts the servers and the databases of Castalie, where this data is stored.
- OpenAI carries the voice of a call, in which Ben tells the caller the advisor's name and free slots, worked out from the busy periods. The names of a workspace's members also help OpenAI transcribe the messages they dictate.
- Anthropic reads a call's transcript, which may name the slot booked, the text of an e-mail received in a connected Gmail mailbox, and the advisor's free slots, worked out from the busy periods, when Ben offers them in writing: to sort the request and write the reply.
- The channel of the reply, when Ben offers slots in writing: Twilio carries an SMS, Meta a WhatsApp message. The person who wrote receives the free slots offered and the time of the appointment booked, never the rest of the calendar.
- Microsoft (Azure Communication Services, Europe) receives your e-mail address to send you Castalie's e-mails, such as a sign-in link.
- The agency's business software, when the agency connects it (today, Lojii): the sender, subject and date of an e-mail received in a connected mailbox are filed there.
- The members of the agency see which calendar an advisor connected and the appointments booked in it, on the screen or through Castalie's agent access (MCP), within the rights of their own account.
- Public authorities, only when the law requires it.
Nobody else receives it. No one at Castalie reads it, except at the user's request to solve a problem, for security, or when the law requires it.
Artificial intelligence. Castalie does not use Google user data, including data obtained through Google Workspace APIs, to develop, improve or train generalized artificial intelligence or machine learning models, and does not retain it for that purpose. OpenAI and Anthropic process it only to provide the features above, under API terms that exclude using it to train their models.
How Google user data is protected. It only travels over encrypted connections (HTTPS). The authorisation is encrypted before it is stored, busy intervals are never stored, and the appointments written are seen only by the members of the advisor's agency.
How long Google user data is kept. Busy intervals are read when a slot is looked for and never stored. The identifier of each event Castalie writes is kept with its appointment, so that the event can be deleted if the appointment is cancelled. The authorisation is deleted as soon as the advisor disconnects their calendar. An advisor or an agency can ask at any time for this data to be deleted, through the contact form. The name, address and picture given by Google sign-in are kept as long as the account exists in the workspace, and deleted with the workspace or sooner on request.
How long
Ben deletes a call's recording at Twilio 90 days after the call. A contact is erased three years after their last exchange with the agency, with the transcripts of their calls, their messages, their requests and their appointments. An agency's workspace may choose shorter periods, never more than a year for a recording and three years for the rest. Both are applied automatically every night. A person can ask for erasure sooner, as described below.
An advisor's call from the softphone is not recorded: Twilio transcribes it live, Ben writes its notes, and the words are deleted as soon as the notes are written. Only the notes are kept, on the contact's file.
Your rights, with Ben
For the people who call or write to an agency, the agency decides how it uses Ben; Castalie processes their data on its behalf. You can ask the agency, or us through the contact form, to access what Ben keeps about you, to correct it or to erase it. An advisor can disconnect their calendar at any time, as described above.
Updated 29 October 2026.
What you may do with Castalie
What the product does and does not do, what we ask of you, and what we do not promise: Terms of use.
Back to home