Legal
Privacy, terms, who we are, and every third party that can touch your data. Written to be read rather than to be survived.
The English version of these pages is the authoritative one. The German, French, Spanish, Portuguese and Italian versions are convenience translations; where they differ, the English text governs.
Provider identification (Impressum)
Oraklo has not launched and the operating entity is still being registered. The registered name, address and commercial register entry will be published here before the service is offered commercially. Until then the contact point is support@oraklo.app, and a person answers it. Oraklo is not registered for VAT.
Privacy
This website. No advertising cookies and no third-party analytics. We do not track you across other sites. Fonts are served from our own origin rather than a font CDN, so loading a page does not tell anyone else you were here. If you choose a light or dark display, one cookie called oraklo_theme remembers your choice on this device for a year. It holds only the word light or dark, is set only when you choose, and is removed when you choose “Follow my device”. It is not used to recognise or track you.
How we count visits. We measure which pages are opened and how far people get through the demo, on our own server in Frankfurt. Nothing is sent to anyone else. There is no cookie and no fingerprint: a random number is kept in your browser tab and thrown away when you close it, so we can tell that one visit went through several steps without knowing who you are. We do not store your IP address, and we never put anything you type — your business name, your email — into those counts. If your browser sends a Do Not Track signal, we record nothing at all.
If you ask us to follow up. When you give us your email address after a demo, we keep it, along with the business name and the kind of business you chose, so we can send you the setup steps and answer you. That is all it is used for. Ask us at support@oraklo.app and we delete it.
If you start a setup. We keep your business email, your website and the answers you give for your assistant, and we delete them 24 hours after the start if you never enter the code we send, otherwise 30 days after your last change, unless you become a customer.
The demo. The business name and assistant name you type are sent to our demo assistant so it can greet you by name. They are personalisation, never treated as proof of identity. Do not type anything into the demo you would not want processed by the providers listed below.
If you become a customer. We process your account details to run the service, and your assistant’s call records for three purposes: running the assistant for your business (answering calls, taking messages and booking requests), showing you those records in your console, and checking the quality of its answers for you. The lawful basis is performance of our contract with you. For the people who call your business, you are the controller and we are your processor.
Retention. Call records — the transcript, the time, the caller's number and the message taken — are deleted automatically 30 days after the call. Website chat records are deleted 30 days after the last message. Calls are not recorded as audio. When you close your account, we stop your assistant at once, and its call records are gone at the latest 30 days later. We delete them earlier if you ask. Encrypted backups can keep a copy for up to 35 more days. Your account and billing records are kept as long as accounting law requires.
Your rights. Under the GDPR and the Swiss FADP you may request a copy of your data, correction, deletion, restriction, portability, and you may complain to your supervisory authority. In Switzerland the authority is the Federal Data Protection and Information Commissioner (FDPIC); in Liechtenstein it is the Data Protection Authority (Datenschutzstelle); in a country of the EU it is the data protection authority of that country. Write to support@oraklo.app. We answer within 30 days and we do not require a particular form of words.
Messages to you after a call (optional). In the setup we offer you a short message after each real call, by e-mail or, where it is offered, on Telegram. E-mail is chosen by default, and goes to the address you confirmed at the start of the setup, or to another address that you confirm with a code we send to it. In the setup you can choose no messages instead, or Telegram where it is offered, and you can change this at any time on your page. Your choice starts when you complete your sign-up; until your assistant has calls nothing is sent, and after that you get one short message after each real call. By default it holds only the caller’s number, the time of the call, and whether the caller wants a call back and whether it is urgent (yes, no or not said). It holds nothing of what was said. You can choose to add a short reason or a short summary of the call; this choice is not offered to health businesses. If a summary is translated into your language, Microsoft Azure does this (region: Switzerland or the EU); according to Microsoft, the text is not stored there when the text translation API is used. If you choose e-mail, the message is sent by Amazon SES in Frankfurt (see the list of sub-processors). E-mails are not end-to-end encrypted, and the copy in your mailbox stays there after we delete the call record (30 days). We store the address and whether each message was delivered, and we delete the address when you turn the messages off or your account is closed. When the sending service tells us that an e-mail to an address bounced or was reported as unwanted, we keep a one-way code of that address, not the address itself, for 24 months, so that we do not write to it again. Every e-mail has a link to stop the e-mails, and you can turn them off at any time with Turn off e-mail messages on your page. If you choose Telegram, the message is delivered by Telegram Messenger Inc., which is established outside the EU and Switzerland and is responsible for its own service under its own privacy policy. Telegram messages are not end-to-end encrypted, and the copy in your chat stays there under Telegram’s rules after we delete the call record (30 days). Telegram is a channel you choose, and we have no data processing agreement with Telegram for these messages. We store only your chat ID and whether each message was delivered. Switch it off at any time with Disconnect on your page, or send /stop to the bot. We also use Telegram to alert our own operator, for example when a new business signs up or a problem occurs. These alerts hold your business name, plan, country, trial end date and our record numbers; they never hold your e-mail address, your phone number or the content of a call.
If you call a business that uses Oraklo. The business you called uses Oraklo’s automated assistant to answer its phone, and the assistant tells you at the start of the call that it is an automated assistant. Your voice is converted to text while you speak, and the assistant answers with a synthetic voice. The call is not recorded as audio. What is kept is the transcript of the call, your phone number, the time and length of the call, and the message or booking request you leave. The business you called is responsible for these data (the controller); Oraklo processes them on its behalf (the processor). The providers that carry and process the call receive them too, some of them in the United States; each is listed with its country in our list of sub-processors. The business can receive a short message about your call; by default it shows only your number, the time, and whether you want a call back or said it is urgent. The record is deleted automatically 30 days after the call; encrypted backups can hold a copy for up to 35 more days. To ask for access, correction or deletion, contact the business you called. You may also write to us at support@oraklo.app, and we pass your request on to the business. The assistant is not an emergency service: in an emergency, call 144, 117, 118 or 112.
If we offer your business a demo. Oraklo (Daniel) is responsible for these data; the business address is in every letter, card and e-mail we send, and you can write to us at support@oraklo.app. Your right to object. You may object at any time, free and without a reason: press “Not us / stop” on the demo page, reply to us or write to support@oraklo.app. We then delete the details about your business at once and put one-way codes of your website, name, e-mail address and telephone number on a do-not-contact list, so that we do not contact you again; the list holds no readable name or address. We use the name, town, website, postal address and public contact details (e-mail address and telephone number) of your business, and the facts that its own website shows (opening hours, services and prices, answers to common questions), whether it is a company or a sole trader, and its type of business. We also record the steps of the demo: when it was built, sent, opened and tried, and whether it was stopped. We take no data from Google. The source is open map data (Overture Maps and OpenStreetMap) and the website of your business. The purpose is to offer your business a demo of our phone assistant, by letter, card, visit, a call from a person or, where the law of your country allows it, an e-mail that we write by hand, with at most one reminder the same way, at least 7 days later. If you ask for the link on a call, we e-mail it to the address you give us and keep that address and the date you asked. We also count, for each version of our texts, how many demos are opened and tried, to improve our texts. The legal basis is our legitimate interest in offering our service to businesses (GDPR art. 6(1)(f); under the Swiss FADP, our overriding interest). How long: a demo that has not been sent is deleted after 30 days; the demo of a letter or a visit after 60 days, and of an e-mail or a call after 30 days; each time the page is opened it is extended by 30 days, never beyond 90 days after the last visit. A reminder sent the same way gives it the same period again, counted from the reminder. On that date the facts we read from your website are deleted. The record of your business (name, address, contact details, legal form and the steps) is kept at most 6 months after we made it, and the note that we wrote to you (business name, town, website, channel, date and text version) for 12 months, as proof. The do-not-contact list is kept without an end, because it is what stops us from contacting you again. Who receives these data: our hosting provider in Frankfurt stores them; to read the facts from your website, its public text goes once to the language-model providers that read websites for us, and the facts to the provider that checks them; when you talk to the demo, the providers that run it process what you say. Some of these providers are in the United States; each is listed with its country in the list of sub-processors; the text of the talk is kept in our dashboard under the same rule as the other chat records in 2.7. Your other rights, including the right to complain to a data protection authority, are in 2.8.
This text is written to be accurate and is checked by us against the Swiss Data Protection Act and the GDPR. It has not been reviewed by a lawyer. The translations are for convenience; the English version governs.
Terms
A subscription is governed by our customer terms and our data processing agreement, which you accept before you store a card. The points below do not replace them.
The demo is provided as-is. It is a shared assistant with a daily cap. The demo on this website is not connected to a phone number, and it will never contact your customers. Oraklo keeps one test phone number for its own testing, which reaches the same demo assistant; it is not offered to the public and carries no call from our customers. The demo invents plausible example times on purpose and says so; do not rely on anything it tells you about real availability or prices.
Pilot pricing means that plans for new customers may differ later. We intend early customers to keep their price for as long as their subscription runs without interruption, as clause 5.6 of the customer terms says.
Limits. The assistant is a machine and will sometimes be wrong. It is not a medical, legal or emergency service and must not be used as one. Emergency calls must go to the emergency services.
Your number stays yours. Forwarding is set up and cancelled by you, on your own phone, with a dial code. We never take control of your line.
Data processing agreement
You are the controller of your customers’ personal data; we are your processor. We act on your instructions, for the purpose of running the assistant you configured, and for nothing else. We do not use your customers’ conversations to train models.
The agreement covers subject matter and duration, categories of data and data subjects, confidentiality and security obligations, the authorised sub-processors below, assistance with data subject requests, breach notification timelines, transfer mechanisms for providers outside the EU, and deletion or return of data when you leave.
Our data processing agreement is part of the customer terms you accept at signup, and you can read it in full before you commit. If you have questions about it, write to support@oraklo.app.
Sub-processors
Every third party that can process personal data on our behalf, what it does, and where it runs. This list is derived from the stack we actually operate.
At least 10 of these process data outside the EU. Each row shows where.
8 of these process data in the United States. That is a real transfer and we will not bury it. If your organisation cannot accept it, write to support@oraklo.app before you buy — for some languages there are EU-hosted alternatives we can configure, and for others there are not yet.
5 of these have a processing region we have not confirmed yet. Until we have, treat them as outside the EU.
| Provider | What it does | Where it runs | Data |
|---|---|---|---|
| Amazon Web Services (AWS) | Hosting and storage | Frankfurt, Germany (eu-central-1) | Everything the service stores: account data, assistant configuration, call and chat records, and the records of businesses we offer a demo to. |
| Amazon SES (AWS) | Sending the emails the service owes you | Frankfurt, Germany (eu-central-1) | Your email address, your business name, and the single-use link that signs you in to your own page. That link IS the credential, which is why this entry matters more than its size suggests. Only if you choose call messages by e-mail: for each real call, the caller’s phone number, the time, whether the caller wants a call back and whether it is urgent, and a link to your dashboard; never the transcript. Only if you choose it, and never for health businesses: also a short reason, or a short summary of the call, which can name the caller. |
| LiveKit | Real-time audio transport | Self-hosted on the AWS instance above | Live call audio in transit. Not stored by this component. |
| OpenAI | Language model that composes the assistant’s replies | United States | The conversation text of a call or chat, plus the assistant’s instructions. |
| Microsoft Azure OpenAI | Backup language model, used when OpenAI does not answer in time | Region not confirmed | The conversation text of a call or chat, plus the assistant’s instructions — only when the backup is used. |
| Microsoft Azure Speech | Speech to text | Switzerland North | Caller audio, converted to text. |
| Microsoft Azure Speech (text to speech) | Voice of German and Portuguese assistants, and backup voice of English assistants | Switzerland North | The text the assistant is about to speak. For an English assistant, only while the backup voice is on. During the setup of a German or Portuguese assistant, also the greeting preview: your business name and your assistant's name. |
| Deepgram | Backup speech recognition, used when Azure Speech stalls; being removed before the first client | United States | Caller audio, converted to text — only when the backup is used. |
| Cartesia | Voice of English assistants, and backup voice of German and Portuguese assistants | United States | The text the assistant is about to speak. For a German or Portuguese assistant, only while the backup voice is on. |
| Twilio | The phone line that carries calls to the assistant: the assistant’s number (a number from the client’s own country, for a business in Liechtenstein a Swiss number), and the SIP trunk to our server (contracting entity: Twilio Ireland Limited) | Ireland (IE1) for call routing; account data in the United States (Twilio's default region US1) unless the IE1 data region is enabled | Call audio in transit, and the caller’s and the called number. |
| Telnyx | Legacy test line: the phone line of our one US test number, which reaches the demo assistant | Region not confirmed | Call audio in transit, and the caller’s and the called number — only for calls to that test number. No client call and no client’s number goes through Telnyx. |
| Stripe | Payments | United States (Stripe Payments Europe is the contracting entity) | Your name, email, business name, VAT or UID number if you give one, and your card — which Stripe holds; we never see it. |
| OpenRouter | Routes the onboarding reader of your website, and of the files you add, to its language model, and when we build a demo for a business we offer one to | United States | The public text of your own website, read once during onboarding, and any price list, menu or flyer you add during the setup, to fill in your assistant’s facts. For a business we offer a demo to: the public text of its website, once. |
| Anthropic | Language model that reads your public website, and the files you add, during onboarding, and when we build a demo for a business we offer one to | United States | The public text of your own website and the files you add during the setup (price list, menu, flyer), once, during onboarding. For a business we offer a demo to: the public text of its website, once. |
| Google (Places API) | Looks up your business’s public listing during onboarding | United States | Your business name and town, once, during onboarding. |
| TypeSafe | Checks whether the facts read from your website look plausible and complete, during onboarding or when we build a demo for a business we offer one to, while this check is switched on | Region not confirmed | Your business name and country, and the opening hours, services, phone number, address and description read from your website — once per website read, during onboarding. |
| Telegram | Alerts to the operator; and, only if you connect it, the message to you after a call | Not stated by Telegram (Telegram Messenger Inc., established outside the EEA) | Operator alerts: your business name, plan, country, trial end date and our record number; for a demo visitor, the business name, business type and language. Operator alerts never carry your email address, your phone number or the content of a call. Only if you connect Telegram for call messages (off until you do): for each real call, the caller’s phone number, the time, whether the caller wants a call back and whether it is urgent, and a link to your dashboard; never the transcript. Only if you choose it, and never for health businesses: also a short reason, or a short summary of the call, which can name the caller. These messages are not end-to-end encrypted, and the copy in your chat stays there under Telegram’s rules after we delete the call record. Telegram offers no data processing agreement for these messages; you choose this channel. |
| Microsoft Azure AI Translator | Translates the short call summary in the message to you, only if you choose the summary level (never offered to health businesses) | Switzerland or the EU (region set by AZURE_TRANSLATOR_REGION) | The short call summary (up to 600 characters; it can name the caller and what was said), once per real call, only for a client who chose the summary level and whose language is not English; never the transcript. According to Microsoft’s documentation, text sent for translation is not stored. |
If we add or replace a sub-processor we update this page, and we tell affected customers before the change takes effect. See also Data and security.