biltia

Biltia · Legal

Privacy policy

Lire cette politique en français

Data controller

Biltia. Contact: contact@biltia.com.

Visiting the website

Audience measurement works without cookies: when you request a call, listen to a recording, start signing up or reach a section, your browser sends the name of the event, the page and the language. For this measurement we store neither your IP address, nor any identifier, nor any cookie.

Demo call

  • Data: your phone number, the exact text of the consent you ticked, and the time and IP address of the request. They are recorded before the call, as proof of your consent.
  • The call is made by an artificial intelligence agent, which says so in its first sentence and announces that the call is recorded. You can refuse the recording or hang up at any time.
  • Limits: one call per number every 24 hours, three per IP address, three minutes at most.
  • Legal basis: your consent, which you can withdraw at any time.

Use of the application by client businesses

For the calls and messages of a subscribed business's customers, that business is the data controller and we act on its behalf (processor). Each business's data is isolated from the others'.

Call recordings: kept 180 days by default; the business can choose 30, 90, 180 or 365 days in its settings. Every night, links to older recordings are removed from the application.

Connecting a Google or Outlook calendar (Google API Services disclosure)

A subscribed business (the owner or one of its technicians) can connect its Google (or Outlook) calendar in Biltia's settings, so that appointments booked by the agent appear in it. This is what Biltia does with that access, and nothing else.

  • Data accessed: free/busy time ranges of the selected calendar and of the primary calendar (scope calendar.events.freebusy); the names of the user's calendars (scope calendar.calendarlist.readonly); the events that Biltia itself creates (scope calendar.events); the account email address (scopes openid, email). Biltia never reads the title, description, attendees or location of the user's own events.
  • How it is used: only to provide the booking feature the user turned on. Busy times are used so that the AI receptionist offers callers free slots only. The calendar list lets the user choose which calendar receives appointments. Biltia creates one event per appointment booked by its agent (date, time, customer name, address and reason for the visit) and updates or deletes that same event when the appointment is moved, reassigned or cancelled. The email address is shown in settings so the user knows which account is connected.
  • Storage and retention: Biltia stores the OAuth access and refresh tokens, the account email address, the identifier of the chosen calendar and the identifiers of the events it created, in a database hosted in the European Union (Frankfurt), isolated per business, for as long as the calendar stays connected. Busy times and calendar names are read when needed and are not stored.
  • Deletion: when the user clicks "Disconnect" in settings, Biltia revokes its access with Google and deletes the stored tokens and email address immediately; they are also deleted when the business account is deleted. Users can also revoke access at any time at myaccount.google.com/permissions, or ask us to delete their data at contact@biltia.com.
  • Protection: Google user data is encrypted in transit (HTTPS/TLS) and at rest in the database. OAuth tokens are readable only by Biltia's servers: they are never sent to the browser, and each business can only access its own data (row-level isolation). Access to production systems is limited to the founder.
  • AI: data obtained through Google Workspace APIs (including Google Calendar) is not used to develop, improve, or train generalized AI and/or ML models, ours or anyone else's. Free/busy information is never sent to an AI model: Biltia computes the open time slots itself, and only those slots (for example "Thursday 9:00") are given to the AI receptionist during the conversation, so it can offer them to the caller. Calendar names, event identifiers and OAuth tokens are never sent to an AI service.
  • AI service providers: the AI receptionist uses (1) ElevenLabs Agents for phone and web calls, with the language model provided through ElevenLabs, whose agreements with its model providers prohibit training on customer content, and with the use of our data for model training turned off in our ElevenLabs account; and (2) OpenRouter for written messages (WhatsApp, SMS), where every request is sent with data_collection: "deny" and Zero Data Retention (zdr: true), so it is only routed to model providers that neither train on nor retain the data. These providers receive only the open time slots computed by Biltia, never raw Google user data.
  • Sharing: Google user data is not sold, not used for advertising, and not shared with third parties, except the hosting providers that run the service on our behalf (in the European Union) and where required by law. No human reads it, except with the user's explicit consent for support, for security, or to comply with the law.

Biltia'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.

Hosting

The application runs in the European Union (Frankfurt region) and its database is hosted in the European Union.

Your rights

You can request access to your data, its correction or deletion, the restriction of or objection to its processing, and its portability, by writing to contact@biltia.com. You can also lodge a complaint with the Belgian Data Protection Authority or the CNIL (France).

Your turn

The next call?It's got it.

Create your account: in 5 minutes, it answers for you.

7 days free · no commitment · ready in 5 minutes

See pricing