Castalie is a conversational strategy coach: you describe your company, and it builds a tree of objectives with you. This page says what that means for your data.
Your data is neither sold nor passed on for advertising purposes. This site uses no advertising trackers and no analytics cookies.
You can ask for access to your data, for it to be corrected or deleted, or object to its processing. Write to us through the contact form , quoting the email address linked to your account. A workspace we delete is deleted entirely, with its conversations, its objectives and its key results.
Green Acres SAS, 100 boulevard du Montparnasse, 75014 Paris (RCS Paris 453 785 156), the publisher of this site. See the Legal notice.
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.
All of it is kept in the agency's own workspace database, with the host named in the Legal notice.
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:
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.
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:
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.
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:
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:
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.
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.
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.
We start when you like!