Privacy policy
Pursuant to Art. 13, 14 of Regulation (EU) 2016/679 (GDPR)
As of: 3 November 2026
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) and the German Federal Data Protection Act (BDSG) is WBA Systems GmbH.
WBA Systems GmbH
Kienberger Allee 4
12529 Schönefeld, Germany
(see Legal notice for further details). fonella is operated by WBA Systems GmbH.
2. Data protection officer
Our data protection officer can be reached at:
Email: datenschutz@fonella.ai
or by post to the address above, marked “Attn. Data Protection Officer”.
3. Principles of processing personal data
We process personal data only insofar as this is necessary to fulfil a contract or pre-contractual measures (Art. 6(1)(b) GDPR), required by law (Art. 6(1)(c) GDPR), necessary for legitimate interests (Art. 6(1)(f) GDPR), or based on your consent (Art. 6(1)(a) GDPR).
We store data only for as long as necessary for the respective purpose or statutory retention obligations apply (e.g. tax retention periods of up to 10 years pursuant to § 147 AO, § 257 HGB). Afterwards, data is deleted or anonymised. We implement appropriate technical and organisational measures (TOM) to protect your data pursuant to Art. 32 GDPR, including encryption, access restrictions, and regular security reviews.
4. Collection and processing of personal data
4.1 When visiting the website (server log files)
When you access our website, the browser on your device automatically sends information to our website server. This information is temporarily stored in a log file and automatically deleted after a maximum of 7 days. Data collected includes the IP address of the requesting computer (anonymised), date and time of access, name and URL of the retrieved file, referring website (referrer URL), browser used and, where applicable, operating system, access provider name, HTTP status code, and amount of data transferred.
The data mentioned is processed to ensure smooth connection to the website, to evaluate system security and stability (e.g. to defend against attacks), and for other administrative purposes. The legal basis is Art. 6(1)(f) GDPR. We never use the collected data to draw conclusions about your identity. Data is not shared with third parties unless required by law.
4.2 When contacting us (form, email, or phone)
For questions of any kind, we offer the option to contact us via a form provided on the website. A valid email address is required so we know who the request comes from and can respond. Further details may be provided voluntarily (e.g. name, phone number, message, company). Processing for contact purposes is based on Art. 6(1)(a) GDPR (consent) or Art. 6(1)(b) GDPR (pre-contractual measures). Personal data collected is automatically deleted after the request is handled unless statutory retention obligations apply.
When contacting us by phone (e.g. for test calls), we use your phone number exclusively for a one-time contact as described in our offer. Processing is based on Art. 6(1)(b) GDPR (pre-contractual measures). Calls are not recorded unless explicitly agreed.
4.3 When using our services (inbound/outbound solutions)
In the context of our AI phone assistants, we process personal data such as names, contact details (e.g. phone number, email), conversation content, voice data, and system integrations (e.g. CRM, ERP, ticketing systems). This is done to provide the service (Art. 6(1)(b) GDPR). All data flows are encrypted (e.g. via TLS/SSL). Contractually relevant storage and metadata are kept in the EU; real-time AI processing may, as described in section 5, involve transfers to service providers in the USA. We conclude data processing agreements (DPAs) and carry out data protection impact assessments (DPIAs), especially for sensitive data. Retention is a maximum of 6 months after contract end unless longer periods are required (e.g. for billing).
4.4 Abuse prevention for test calls, callback and forwarding functions
Via our website, visitors can enter their own phone number for test purposes, on which our AI phone assistant calls them back (test call). In addition, customers can store, in the customer area, a destination number for forwarding incoming calls. To protect against abusive use of these functions, in particular to prevent calls to chargeable special-rate numbers or emergency numbers and to defend against automated mass or spam requests, we process the number provided, the IP address, timestamps and technical metadata of the respective trigger. For this purpose we employ technical safeguards (including block lists for impermissible destination numbers, frequency or rate limits, and the services listed under sections 6.2 and 6.12).
The legal basis is Art. 6 (1) (f) GDPR. Our legitimate interest lies in the security and functionality of our systems, the avoidance of damage and costs caused by abusive calls, and the prevention of the misuse of emergency numbers.
As a rule, this data is deleted after a short time (see section 4.1). However, if there is a concrete suspicion of abusive use (e.g. deliberate circumvention of the safeguards, dialling of chargeable numbers or emergency numbers, spam attacks), we additionally store the aforementioned data, in particular the IP address and connection data, for the period required to investigate, to assert, exercise or defend legal claims and to report the matter to the authorities. The legal basis for this is Art. 6 (1) (f) GDPR (enforcement of legal claims and abuse prevention) or Art. 6 (1) (c) GDPR insofar as a legal obligation exists. If a responsible party cannot be directly identified due to a lack of contact details, we reserve the right to establish their identity within the scope of the legal means available, in particular by court order via disclosure of the IP address.
4.5 Consent to being contacted and called back
On our forms (callback box on the home page, contact form, support form) you explicitly confirm with a checkbox, before submitting, that we may contact you about your enquiry, expressly including by phone. The box is not pre-ticked; without it the form is not submitted.
In the setup of your customer account, too, below the fields for company name, your name, phone number and email address, we ask with a checkbox whether we may contact you about fonella, including by phone and email, for example to help set up your assistant or about an offer. This box is optional and not pre-ticked; the setup works without it. If you tick it, we store the time of your consent and its wording in your customer account. The legal basis, proof and withdrawal described below apply accordingly.
The consent allows us to call you back on the number you provided, including through our AI phone assistant (see section 5), to contact you by phone or email in order to answer and handle your enquiry, and to come back to you about this very matter after the first contact, for instance to follow up on a quote, a trial access or a demonstration. It does not extend to advertising on other topics and not to our newsletter; we obtain separate consent for those.
The legal basis is Art. 6 (1) (a) GDPR (consent) and, for contacting you by phone for advertising purposes, additionally Section 7 (2) no. 1 of the German Act Against Unfair Competition (UWG). Where contacting you also serves pre-contractual measures taken at your request, we additionally rely on Art. 6 (1) (b) GDPR.
To be able to demonstrate the consent (Art. 7 (1) GDPR), we store the time of the consent and the verbatim wording of the consent text you were shown together with your enquiry. We keep this record for the duration of the statutory limitation periods, as a rule three years from the end of the year in which the contact took place, and delete it afterwards.
You can withdraw your consent at any time with effect for the future, informally by email to datenschutz@fonella.ai, by post to the address given in section 1, or directly during an ongoing call to our staff. The withdrawal does not affect the lawfulness of the processing carried out until then. After the withdrawal we will no longer contact you for advertising purposes; the handling of an enquiry you have already submitted may remain unaffected insofar as it is based on Art. 6 (1) (b) GDPR.
4.6 Our own usage analysis on the website, the web app and in our apps
To understand how our website, our customer area in the browser and our desktop and mobile apps are used, where visitors get stuck and where errors occur, we record the usage ourselves, without involving any third party. We record the pages and steps opened (for example in the account setup), clicks, entering and leaving form fields, the input in form fields including input that was deleted or changed again, submitted and abandoned forms, scroll depth, time spent, error messages shown and the opening and closing of the apps.
For this we store your IP address, an estimated location derived from it (city and country, determined from a database for assigning IP addresses stored with us, without transfer to third parties), the request headers sent by the browser or app (for example browser, language and referring page, without cookies and credentials), device, operating system and browser, screen and window size, language, time zone and connection type, campaign parameters as well as randomly generated identifiers for visitor, session and app installation and a device identifier. We keep these identifiers in the storage of your browser or the app. If you are signed in, we assign the recording to your user account. Through shared attributes such as user account, email address, app identifier, device identifier or IP address, we link visits to the website with the use of the apps.
The contents of password fields and payment card data are never recorded; at most we store the number of characters entered. The apps first collect the data on the device and transfer it at intervals. Every transfer is encrypted end to end on the device before it is sent. The data is stored at Amazon Web Services in Frankfurt am Main (see section 6.3) and evaluated exclusively by us. We automatically delete personal records after 180 days; after that only aggregated figures without personal reference remain.
The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is to improve our website and our apps, to identify and remove obstacles and errors in registration, setup and ordering, and to detect misuse. You can object to this processing at any time with effect for the future by email to datenschutz@fonella.ai.
4.7 Advertising to customers by email and SMS
If you have a user account with us, we occasionally send you personal messages about our own, similar services, such as help with the setup, offers and voucher codes, or the question whether you are satisfied. For this we use the email address of your user account, the phone number stored in the customer area, your name and your language setting. If you have chosen a language other than German, we have the text translated by an AI language model before sending (see section 5); only the message text and your name are transmitted. We send emails through our email service provider Mailgun and SMS through GatewayAPI (section 6.10). We log every message with time, channel, recipient and content.
The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is advertising to our existing customers (Section 7(3) of the German Act against Unfair Competition, UWG). You can object to this advertising at any time without incurring any costs other than the transmission costs at the basic rates: via the unsubscribe link at the end of every email and every SMS, via the settings in your customer area, or informally by email to info@fonella.ai. After that you will no longer receive advertising from us, neither by email nor by SMS. We store your objection with its time and channel so that we can respect and prove it permanently. You will still receive messages about your contract, such as invoices and security notices.
5. Processing in the context of AI telephony
(1) Incoming audio data is converted to text in real time by speech recognition systems (speech-to-text). This text is passed to an AI language model that generates a response based on the configuration provided by the customer. The generated text response is converted into spoken language via text-to-speech technology and played to the caller.
(2) Audio data is deleted after real-time processing is complete unless call recording is enabled by the customer. Transcripts and summaries are stored according to the customer's settings and the contractual agreement.
(3) Metadata, transcripts, and summaries are hosted on servers within the European Union (AWS, Frankfurt region) where processed or stored in our infrastructure. For real-time speech recognition, AI response generation, and speech synthesis we use the service providers listed in subsection (5) below (USA).
(4) Conversation data is not used to train AI models unless explicit and separate consent from the customer and affected callers is obtained.
(5) To provide the AI phone assistant we transfer personal data to external service providers and process it there. Processing takes place in four functions; each provider receives only the data required for its function (data minimization principle):
Speech recognition (STT)
Service provider: Deepgram, Inc.
Location: USA (San Francisco, CA)
Data transmitted: Live audio of the call; voice messages received on the chat channels (WhatsApp, Instagram, Facebook, Telegram); voice messages the customer records in the personal assistant of the customer area; voice messages visitors record in the chat widget of a website; glossary of correct spellings (company and assistant name, names of team members, forwarding targets and address book contacts, without contact details)
Basis for transfer: DPA + SCC / EU-US DPF
AI language model (LLM)
Service provider: Anthropic, PBC
Location: USA (San Francisco, CA)
Data transmitted: Conversation text, assistant configuration, knowledge base; name and further details as well as the logbook of exactly the contact currently writing or calling; files attached in the chat or sent through the connected channels (WhatsApp, Instagram, Facebook, Telegram, email): name, type, size, readable text of documents as well as images and the page images of scanned PDF files (at most three pages) for recognition of text and picture content by an image model (Google Gemini, alternatively OpenAI); for summary and translation: glossary of correct spellings (names of the company, team, forwarding targets and address book contacts); during initial setup: company description. Depending on availability, primary and fallback models from OpenAI, Anthropic, Google (Gemini/Gemma) and Meta (Llama) are used (provided in part via OpenRouter, Inc.)
Basis for transfer: DPA + SCC / EU-US DPF
AI language model (LLM): self-hosted when the Google Calendar integration is enabled
Service provider: Fonella (self-hosted): “Gemma” model (Google) via the Ollama runtime
Location: EU (AWS, Frankfurt region)
Data transmitted: Conversation text, assistant configuration and knowledge base, only when the calendar feature is enabled and a Google Calendar is connected. In this case the AI response generation runs on our own server in the EU and replaces the US LLM providers listed above; the model runs locally and no personal data is transmitted to Google in the process
Basis for transfer: Own processing within the EU (no third-country transfer)
Speech synthesis (TTS) and, on customer request, voice cloning (custom voice)
Service provider: ElevenLabs, Inc.
Location: USA (New York, NY)
Data transmitted: Response text; when using a custom voice, additionally the voice recording (audio sample) provided by the customer
Basis for transfer: DPA + SCC / EU-US DPF
Call log translation
Service provider: Google LLC (Alphabet Inc.)
Location: USA (Mountain View, CA)
Data transmitted: Call summary and transcript for multilingual display in the customer portal; text and recipient name of personal messages to customers that are translated into their language
Basis for transfer: DPA + SCC / EU-US DPF
The complete list of all sub-processors (including cloud hosting) is available on our Sub-processors page.
We reserve the right to continuously extend or change the AI models we use and the list of providers (sub-processors) used for them, in particular to ensure availability, quality and resilience (e.g. via primary and fallback models). We notify of the addition or replacement of sub-processors in accordance with the procedure set out in the data processing agreement; the current list is always available on our Sub-processors page.
Self-hosting when the Google Calendar integration is enabled: If you have enabled the calendar feature and connected a Google Calendar, the AI response generation (LLM) for the phone number concerned runs exclusively on a server operated by us within the European Union (AWS, Frankfurt region). As the language model we use the “Gemma” model (Google), which runs locally on our own infrastructure via the Ollama runtime. In this configuration the conversation text is not transmitted to the US AI providers named above (in particular Anthropic, OpenAI, Google, Meta or OpenRouter) but remains in the EU for the AI response generation; no third-country transfer takes place for this. The model runs locally and no personal data is transmitted to Google in the process. Real-time speech recognition (STT) and speech synthesis (TTS) continue to be provided by the service providers named above.
For AI language processing we also transmit your stored assistant configuration (company name, phone number, email address, website, address, company description, additional instructions, pronunciation entries, selected language and voice) and the contents of your knowledge base (uploaded files and stored URLs) in addition to the conversation text.
We update this overview whenever the service providers in use change.
Purpose of processing: Operation and provision of the AI phone assistant.
Legal basis: Operation of the AI phone assistant under your contract with us is based on Art. 6(1)(b) GDPR (contract performance). Before you first actively use the test assistant in the app, we also obtain your consent pursuant to Art. 6(1)(a) GDPR where transfer to the AI services listed above is not already covered by the contract.
Transfer to a third country: The providers listed above are based in the USA. Transfers are based on EU standard contractual clauses (Art. 46 GDPR) and/or, where the respective provider is certified, the EU-US Data Privacy Framework. The specific basis for each provider follows from the data processing agreement (DPA) concluded with that provider.
Processing on behalf: We have a data processing agreement pursuant to Art. 28 GDPR with each of these providers, ensuring an adequate level of data protection.
Retention period: Live audio is processed only for the duration of real-time processing of the respective call and is deleted afterwards unless you have enabled call recording. We store transcripts, summaries, and related metadata according to your settings and the contractual agreement; after the contract ends we delete them within 6 months at the latest unless statutory retention obligations apply.
Consent and withdrawal: Before you first actively use the test assistant in the app, we obtain your explicit consent to transfer data to the services listed above. You may withdraw this consent at any time under “Settings → AI processing & privacy”; withdrawal ends further use of the test assistant unless processing can be based on Art. 6(1)(b) GDPR.
(6) Custom voice (voice cloning) and biometric voice data
Optionally, you can store your own voice for the speech output of your AI phone assistant (“custom voice”). To do so, you upload an audio recording or record it via the app; a digital voice model (voice ID) is created from this recording and used to output text in the stored voice. This feature is optional and only active if you explicitly set it up.
Biometric data (special category): The voice recording used to create the voice model is biometric data within the meaning of Art. 9(1) GDPR, as it allows the unique identification of the speaking person. This applies irrespective of the subsequent sound or output quality of the generated voice model. We process this special category of personal data exclusively on the basis of your explicit consent pursuant to Art. 9(2)(a) in conjunction with Art. 6(1)(a) GDPR.
Your own voice only (self-cloning): The feature is intended exclusively for cloning your own voice. Before setting it up, you must expressly confirm and consent that the uploaded or recorded voice is your own voice and that you consent to its processing for the purpose of voice synthesis (enrollment verification). Uploading or using another person’s voice is not permitted. If you are not the speaking person yourself, you may only use the feature if you hold demonstrable, explicit consent from the person concerned and all required rights; you bear sole responsibility for this.
Transfer and processing: The creation of the voice model (voice cloning) and the speech synthesis are carried out by our service provider ElevenLabs, Inc. (USA). For this purpose we transmit the voice recording you provide to ElevenLabs. The transfer to the USA is safeguarded by EU standard contractual clauses (Art. 46 GDPR) and/or the EU-US Data Privacy Framework; a data processing agreement pursuant to Art. 28 GDPR is in place with ElevenLabs. Further information: https://elevenlabs.io/privacy.
Retention period: We store the voice recording and the voice model created from it only for as long as you have the “custom voice” feature activated. If you delete the custom voice, withdraw your consent, or the contract ends, we delete the voice recording and the voice model and arrange for their deletion at ElevenLabs.
Consent and withdrawal: You may withdraw your consent to the processing of your biometric voice data at any time with effect for the future by deleting the custom voice in the app or sending an email to info@fonella.ai. The lawfulness of processing carried out before withdrawal remains unaffected; after withdrawal, the “custom voice” feature is no longer available.
6. Use of third-party services
6.1 Google Analytics
We use Google Analytics, a web analytics service provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Google Analytics uses cookies to analyse website usage. Information generated by the cookie about your use of this website (including your anonymised IP address) is transmitted to a Google server in the USA and stored there. Processed data includes anonymised IP address, browser type, operating system, referrer URL, and time of request. Legal basis: Art. 6(1)(a) GDPR (your consent via the cookie banner). Data is transferred to the USA (EU-US Data Privacy Framework certified; standard contractual clauses as supplement). You can prevent collection by not accepting the cookie or installing an opt-out plugin. More information: https://policies.google.com/privacy.
6.2 Google reCAPTCHA
We use Google reCAPTCHA (version 3) to protect marketing forms (contact, callback, feedback) against automated attacks (bots). Provider: Google Ireland Limited. reCAPTCHA analyses visitor behaviour using various characteristics (e.g. mouse movements, IP address, browser information, keyboard input). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in protecting the website). Data is transferred to the USA (as with Google Analytics). More information: https://policies.google.com/privacy.
6.3 AWS als Hoster
Our website and services are hosted on servers of Amazon Web Services (AWS), offered by Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg. Servers are located in the EU (Frankfurt region); no transfer to third countries without adequate safeguards. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in reliable hosting). We have concluded a data processing agreement with AWS. More information: https://aws.amazon.com/privacy/.
6.4 CRM-System HubSpot
We use the CRM system HubSpot to handle enquiries, communicate with prospects and customers, and organise sales-related processes (HubSpot Ireland Limited, or depending on product configuration an affiliated company of the HubSpot group with offices including in the USA). Data is transmitted server-side only from our technical platform (API) to HubSpot via encrypted connections (TLS), not directly in the browser without your specific interaction with the services below.
When is data transferred and which data is transmitted?
We transfer personal data to HubSpot only in connection with an action you initiate. Only the data you provide in that context or that is technically required from the existing payment account or sign-in applies:
(1) Contact form on the website: immediately after your enquiry is submitted successfully: in particular name, email address, phone number, optional company/organisation, and your message.
(2) Public feedback form: immediately after successful submission: email address, subject, priority, and an excerpt or description of your feedback (content within the limits of technical parameters).
(3) Callback assistant (test call / callback via the offered function): immediately after the call is successfully triggered technically: phone number (if no further details are provided, possibly without email).
(4) Registration / sign-in: when you create a user account or sign in and our system triggers an internal notification: in particular email address, optionally name, and a technical user identifier (e.g. identity provider ID) where available for assignment.
(5) Existing customer subscription (payment / Stripe): for relevant automatic events in the billing system (e.g. completed checkout or subscription status changes): in particular the email address stored with the payment provider, identifiers for subscription and plan or price product, subscription status, and optionally a technical user identifier linked to the contract where available. Your full contract or call history is not transferred; only these core details typical for CRM and customer care are set or updated.
Processing serves to handle your enquiries, customer care, documentation of technical contact/support processes, and sales-related maintenance of existing customer relationships. Legal basis is Art. 6(1)(b) GDPR (pre-contractual measures or contract performance) where transfer serves to process your enquiry or a contract with us, and additionally Art. 6(1)(f) GDPR (legitimate interest in organised contact/customer management without overriding data subject interests). Where individual data is based on consent, Art. 6(1)(a) GDPR applies.
Transfer to a third country cannot be ruled out if parts of HubSpot are used outside the EU. HubSpot provides EU standard contractual clauses and documented additional safeguards; HubSpot's privacy policy at https://legal.hubspot.com/privacy-policy and standard contractual clause documents contain further information. A data processing agreement (DPA) with HubSpot is used/concluded where required.
6.5 Payment provider Stripe
To process paid subscriptions and payments we use Stripe (Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland, where applicable involving Stripe, Inc., USA). We process in particular your name, email address, billing address, and subscription and payment metadata. Payment and card data is entered directly with Stripe (PCI-DSS compliant); we do not store full card numbers. Legal basis is Art. 6(1)(b) GDPR (contract performance). Transfer to the USA may occur and is safeguarded by EU standard contractual clauses or the EU-US Data Privacy Framework. A data processing agreement with Stripe is in place. Further information: https://stripe.com/privacy.
6.6 User management and authentication (Auth0)
To manage user accounts and sign-in to the customer portal we use Auth0, a service of Okta, Inc. (Auth0). We process in particular your email address, name, authentication identifiers, sign-in metadata (e.g. IP address, timestamp), and, where social logins are used, the respective provider identifier. Legal basis is Art. 6(1)(b) GDPR (provision of the customer portal) and Art. 6(1)(f) GDPR (sign-in security). Transfer to the USA may occur and is safeguarded by EU standard contractual clauses or the EU-US Data Privacy Framework. A data processing agreement with the provider is in place. Further information: https://www.okta.com/privacy-policy/.
6.7 Mouseflow
We use Mouseflow for pseudonymous analysis of usage behaviour (session recording, click and movement heatmaps) to improve our website. The provider is Mouseflow ApS, Flæsketorvet 68, 1711 Copenhagen, Denmark. We process pseudonymous usage data such as mouse and scroll movements, clicks, page views, and the anonymised IP address; input fields are masked by default. Legal basis is Art. 6(1)(a) GDPR (your consent via the cookie banner). Mouseflow is loaded only after your consent. Further information: https://mouseflow.com/privacy/.
6.8 Chat widget on our website
The chat widget on our website is our own fonella chat widget. It runs without an external chat service on our servers within the European Union (AWS, Frankfurt region) and is only loaded if you consent to the Live Chat category in the cookie banner. Chat enquiries are answered by an AI assistant; for this the content is sent to our language model provider OpenRouter. We process the content you send in the chat, any email address or name you provide and technical metadata (e.g. time, browser data). The widget stores a random session identifier and the history of the current conversation in your browser storage. The legal basis is Art. 6(1)(a) GDPR (your consent via the cookie banner) and Art. 6(1)(b) GDPR (answering your enquiry). Processing by OpenRouter may involve a transfer to the USA, safeguarded by EU Standard Contractual Clauses. More information: https://openrouter.ai/privacy.
In the chat widget you can also attach files (images, PDF, Office documents and text files, at most 4 MB per file) and send voice messages. Attached files are stored on our servers in the EU (AWS, Frankfurt region) with the provider of the chat; the AI assistant receives the name, type and size of each file and the readable text of documents (PDF, Word, Excel, PowerPoint, OpenDocument, RTF, text and CSV files) as well as what an AI image model recognizes in images and scanned PDF files (text and a short description of the picture). For this we send the image or the page images of a scanned PDF (at most three pages) via OpenRouter, Inc. to a model from Google (Gemini), or alternatively from OpenAI (see section 5); the AI assistant itself only receives the result as text, not the image. A voice message is converted into an audio format in your browser and sent to our speech recognition provider Deepgram, Inc. (USA) to be turned into text; we do not store the recording, it only stays in your browser storage so you can play it again. The transfer to Deepgram is safeguarded by EU Standard Contractual Clauses (Art. 46 GDPR) or the EU-US Data Privacy Framework. The legal basis is Art. 6(1)(a) and (b) GDPR. More information: https://deepgram.com/privacy.
6.9 Server monitoring (UptimeRobot)
To monitor the availability of our servers and services we use UptimeRobot (UptimeRobot Service Provider Ltd.). The service polls technical endpoints at regular intervals and processes only technical data (e.g. URL, status code, response time); personal data of website visitors is not specifically collected in the process. Legal basis is Art. 6(1)(f) GDPR (legitimate interest in reliable operation). Further information: https://uptimerobot.com/privacyPolicy/.
6.10 Sending SMS notifications (GatewayAPI)
To send outgoing SMS notifications we use GatewayAPI, operated by ONLINECITY.IO ApS, Buchwaldsgade 50, 5000 Odense C, Denmark. We process the recipient's phone number and the content of the respective SMS (e.g. notifications as well as personal messages and offers to customers, see section 4.7). Legal basis is Art. 6(1)(b) GDPR (contract performance) or Art. 6(1)(f) GDPR (legitimate interest in reliable notification). The provider is based in the EU (Denmark). Further information: https://onlinecity.io/legal-documents/gatewayapi/privacy-policy.
6.11 Distribution of our apps via app stores
Our applications are available via the app stores of the respective platform operators: Google Play Store (Google Ireland Limited or Google LLC, USA), Apple App Store and Apple Mac App Store (Apple Distribution International Ltd., Ireland, or Apple Inc., USA), and Microsoft Store (Microsoft Ireland Operations Ltd. or Microsoft Corporation, USA). When downloading and using our app via these stores, the respective store operator processes personal data (e.g. account, device, and download data) under its own responsibility as an independent controller on the basis of its own privacy terms; we have no influence over this. The relevant policies are: Google (https://policies.google.com/privacy), Apple (https://www.apple.com/legal/privacy/), and Microsoft (https://privacy.microsoft.com/privacystatement). From the stores we ourselves receive at most aggregated or anonymised statistics and, for purchases via the stores, billing-related confirmations.
6.12 IPQualityScore (IP, phone and email reputation)
To protect our forms (contact, callback, feedback, support) and the sign-up against abuse, we server-side check the reputation of the sender via IPQualityScore (IPQualityScore LLC, USA). The IP address and, where provided in a form, the phone number and email address are transmitted for this purpose; for email addresses we additionally check whether they are disposable/throwaway addresses. We cache the check result in our database for as long as it remains valid to avoid repeated lookups. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in protecting against automated abuse). Data may be transferred to the USA; safeguarded by standard contractual clauses. More information: https://www.ipqualityscore.com/privacy-policy
6.13 Newsletter (Mailchimp)
For the optional delivery of product news and fonella updates by email, we use Mailchimp (Intuit Mailchimp, The Rocket Science Group LLC, USA). Data is transferred only if you actively tick the optional newsletter checkbox during onboarding and click “Continue”. We transmit the email address from your user account and, where available, your name. Legal basis: Art. 6(1)(a) GDPR (consent). You may withdraw consent at any time with effect for the future, e.g. via the unsubscribe link in each newsletter email or by email to info@fonella.ai. Data may be transferred to the USA; safeguarded by standard contractual clauses (Mailchimp DPA). More information: https://mailchimp.com/legal/privacy/
6.14 Customer reviews (Trustportal)
On our website we embed a review widget from Trustportal (trustportal.biz), a review portal operated by B A Media Group FZE LLC, Business Centre, Sharjah Publishing City Free Zone, Sharjah, United Arab Emirates. The widget is loaded only after you have consented to the "Marketing & reviews" category in our cookie banner. When it loads, your browser connects to trustportal.biz; for technical reasons your IP address, browser type and time of access may be transmitted. The widget sets no cookies and uses no local storage. Without your consent we only show a link to our review page at Trustportal; a connection to Trustportal is established only when you click it. Legal basis: Art. 6(1)(a) GDPR (consent). You may withdraw consent at any time via "Cookie settings" in the footer.
6.15 Google Ads conversion tracking
We use the conversion tracking feature of Google Ads, a service provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. It lets us measure the success of our ads by recording whether visitors carry out certain actions after clicking an ad (submitting a contact request, requesting a test call, booking a demo, or registering a user account). The required Google tag (gtag.js) is only loaded after you have consented to the "Marketing & reviews" category in our cookie banner; only then does it set the associated cookies (in particular _gcl_au) and store identifiers. Without your consent the tag is not loaded and no data is sent to Google (see section 6.19). Personal data (in particular IP address, browser and device information, conversion time) may be transmitted to Google. We do not transmit clear names or email addresses via this tag. Legal basis: Art. 6(1)(a) GDPR (your consent). Data is transferred to the USA (EU-US Data Privacy Framework certified; standard contractual clauses as supplement). You may withdraw consent at any time via "Cookie settings" in the footer. More information: https://policies.google.com/privacy.
6.16 Calendar integrations (appointment booking)
As a customer, you can optionally connect an external calendar or scheduling service per phone number so that the AI phone assistant can read availability and book appointments directly during the call. The connection is set up actively by you alone and can be disconnected at any time under “Appointments → Integrations”. Without a connection activated by you, no data is transmitted to these services.
Supported services and providers:
(1) Google Calendar: Google Ireland Limited or Google LLC, USA (https://policies.google.com/privacy).
When the calendar feature is enabled and a Google Calendar is connected, the AI response generation (LLM) does not run via the US AI providers but on a server operated by us in the EU (AWS, Frankfurt region) using the “Gemma” model (Google) executed locally via the Ollama runtime; the conversation text remains in the EU for this (see section 5 for details).
Limited Use of Google Workspace data: The use and transfer of raw or derived user data received from Google Workspace APIs (in particular the Google Calendar API) will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. We use this data solely to provide the appointment-booking feature you have activated and do not transfer or use it for any other purpose.
(2) Microsoft Outlook / Microsoft 365: Microsoft Ireland Operations Ltd. or Microsoft Corporation, USA (https://privacy.microsoft.com/privacystatement).
(3) Apple iCloud (connected via CalDAV): Apple Distribution International Ltd., Ireland, or Apple Inc., USA (https://www.apple.com/legal/privacy/).
(4) Other CalDAV servers: a provider of your choice; the place of processing and the applicable privacy terms depend on the provider you select.
(5) Calendly: Calendly LLC, USA (https://calendly.com/privacy).
(6) Cal.com: Cal.com, Inc., USA or the region you select (https://cal.com/privacy).
Which data is transmitted? To retrieve availability we read the busy and free times of your connected calendar. When booking an appointment we transmit the data provided by the caller during the call to the relevant service in order to create the appointment, in particular name, phone number, optionally email address and a note or request, as well as the date, time and title of the appointment. Only the data required for the booking is transmitted (data minimisation principle).
Credentials and tokens: For OAuth-based services (Google, Microsoft, Calendly) we store the access and refresh tokens you grant; for CalDAV/Apple iCloud and Cal.com the credentials you provide (e.g. app-specific password, API key). These secrets are stored encrypted (AES-256-GCM) and used solely to provide the integration you have activated.
Purpose: Retrieval of availability and booking of appointments by the AI phone assistant on behalf of the customer.
Legal basis: Art. 6(1)(b) GDPR (performance of the contract concluded with you or the feature you have activated). With regard to the callers’ data you act as the controller; in that respect we act as a processor on the basis of the data processing agreement (DPA).
Transfer to a third country: Google, Microsoft, Apple, Calendly and Cal.com are (also) based in the USA. The transfer takes place on the basis of EU standard contractual clauses (Art. 46 GDPR) or, where the respective provider is certified, on the basis of the EU-US Data Privacy Framework. For CalDAV servers you select yourself, the place of processing depends on the respective provider.
Retention period: The appointment data created remains in your connected calendar or with the respective service and is subject to its privacy terms. In our infrastructure we only store the connection and configuration data required for operation; after the integration is disconnected or the contract ends, we delete the stored credentials and tokens.
fonella Calendar: Every assistant also has the calendar built into fonella, with no external service involved. Appointments and blocked periods that you create or that the AI phone assistant books (title, date, time, duration and, optionally, the caller's name, phone number and note) are stored exclusively in our own infrastructure in the EU (AWS, Frankfurt region); no data is transmitted to third-party calendar or scheduling services. You receive a personal subscription link (iCal) that lets you add the calendar, read-only, to a calendar app of your choice. The link contains a random secret key and is visible only to you as the account owner. If you open the link in a third-party calendar app, that provider processes the appointment data under its own privacy policy. Canceled appointments remain stored in your account, marked as canceled; we delete all entries together with your user account or after the end of the contract.
A complete list of these services and the data transmitted can be found on the Sub-processors page.
6.17 Server-side revenue and conversion measurement (Google Analytics Measurement Protocol)
To measure the success of our offerings, after a successfully completed payment we transmit a purchase event to Google Analytics (Google Ireland Limited / Google LLC) on a server-to-server basis, i.e. independently of cookies and of the user's browser, via the so-called Measurement Protocol. We transmit only the transaction amount, the currency, a transaction identifier (invoice number), the name of the booked plan and a pseudonymous identifier. Where an analytics identifier was captured during the preceding website visit with your consent, that identifier is used; otherwise a pseudonymous identifier derived from the internal billing customer number is used. We do not transmit real names, email addresses or payment data via this channel. Through the link between Google Analytics and Google Ads, these purchase events may at the same time be imported as a conversion in Google Ads. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in the business measurement of the success and reach of our advertising and sales activities). Data is transferred to the USA (EU-US Data Privacy Framework certified; standard contractual clauses as a supplement). You may object to this processing at any time with effect for the future using the contact details provided in the legal notice. Further information: https://policies.google.com/privacy.
By the same route we additionally report events that evidence a business enquiry: requesting a test call, submitting a contact request, booking a demo appointment and registering a user account. This reporting also happens server side, that is, independently of cookies and of the user's browser, because the enquiry in question has already reached us at that point. All that is transmitted is the type of event, a transaction identifier to prevent double counting and a pseudonymous identifier; if an analytics identifier was captured with your consent during the preceding visit it is used, otherwise a pseudonymous identifier derived from the enquiry. We do not transmit names, email addresses, phone numbers or the content of your enquiry this way. Through the link between Google Analytics and Google Ads, these events may also feed into Google Ads as conversions. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in measuring the success of our advertising and sales activities). You may object to this processing at any time with effect for the future using the contact details in the imprint.
6.18 Identity verification / KYC when assigning phone numbers (SumSub)
For the assignment of business phone numbers, we are legally obliged to verify the customer's identity and to collect and verify the subscriber data of the connection holder (Know Your Customer, “KYC”; cf. Section 172 TKG). We are not ourselves a telecommunications provider within the meaning of the TKG, but for the provision of phone numbers we work directly with a telecommunications provider (carrier). We carry out the identity verification through the service provider SumSub (Sum and Substance Ltd., 30 St. Mary Axe, London EC3A 8BF, United Kingdom).
The data transmitted and processed here comprises the identity data of the customer or the natural person acting on their behalf (in particular name, address and, for natural persons, date of birth), the data and image of the identity document presented, a photo and, for fraud prevention, the result of a liveness check (liveness/face match) and the verification result. The legal basis is Art. 6(1)(c) GDPR (compliance with a legal obligation, in particular under Section 172 TKG) as well as Art. 6(1)(b) GDPR (performance of the contract). Insofar as biometric data are processed as part of the liveness check, we base this on Art. 9(2)(g) GDPR (substantial public interest) in conjunction with the obligations under telecommunications law and, where necessary, on your explicit consent pursuant to Art. 9(2)(a) GDPR.
SumSub is based in the United Kingdom; the transfer is safeguarded by the European Commission's adequacy decision for the United Kingdom (Art. 45 GDPR), supplemented by EU standard contractual clauses. A data processing agreement pursuant to Art. 28 GDPR is in place with SumSub. We, or the telecommunications provider (carrier) we use, are legally obliged to disclose the collected subscriber and connection-holder data, upon official order, to authorised authorities (in particular security, law-enforcement and regulatory authorities as well as courts) (in particular Sections 173, 174 TKG). The retention of connection-holder data is governed by Section 172(6) TKG; it is retained until the end of the calendar year following the end of the contractual relationship and deleted thereafter. Further information: https://sumsub.com/privacy-notice-service/.
6.19 Consent mode for Google services (Google Consent Mode v2)
For the Google services on this website (Google Analytics, Google Ads) we use the basic variant of consent mode ("Google Consent Mode v2"). When the page is opened, storage for advertising purposes, analytics, ad-related user data, personalised advertising as well as convenience and personalisation functions are all denied at first. Only the security area stays granted; it covers abuse prevention only (see section 6.2, Google reCAPTCHA). As long as you have not decided in the cookie banner, no Google tag is loaded and no data is sent to Google, not even cookieless signals. Google Analytics is only loaded once you consent to the "Statistics & session recording" category, Google Ads only once you consent to the "Marketing & reviews" category. At the same time we transmit a consent signal that matches your selection exactly. If you withdraw your consent later via "Cookie settings" in the footer, that signal is set to denied immediately, the associated cookies (e.g. _ga, _gcl_au) are deleted and the page is reloaded, so the tag concerned is no longer active. The legal basis for the processing by Google is Art. 6 (1) (a) GDPR (your consent) in conjunction with section 25 (1) TDDDG.
If Google Analytics is active with your consent while there is no consent for marketing, the "ads data redaction" feature is active as well: in that case Google strips ad click identifiers from the requests, so no attribution to an ad is possible. The legal basis for consent mode itself is Art. 6 (1) (f) GDPR (legitimate interest in a transparent and data-minimising handling of consent); the actual processing by Google takes place solely on the basis of your consent pursuant to Art. 6 (1) (a) GDPR. Further information: https://policies.google.com/privacy.
6.20 Customer service messages via WhatsApp, Instagram and Facebook (Meta)
Customers can connect their fonella assistant to their WhatsApp Business account, their Instagram account or their Facebook page so that the assistant answers messages from their contacts on their behalf. For users in the European Economic Area, these platforms are provided by Meta Platforms Ireland Ltd., Merrion Road, Dublin 4, D04 X2K5, Ireland. Only the customer establishes the connection, and the customer can disconnect it at any time.
In doing so, the content of the messages, the identifiers of the person writing (in particular phone number, user or page ID and display name) and timestamps are processed and exchanged with Meta. If the customer has the assistant take voice calls over WhatsApp Business, the audio of the call is additionally transmitted via Meta and processed like a phone call. When a WhatsApp account is connected, we take over the messages of the last 24 hours so that ongoing conversations can be continued. We store the conversations in our database so that the customer can view them in the customer area. The legal basis is Art. 6(1)(b) GDPR (provision of the service booked by the customer) and, with regard to the contacts who write, Art. 6(1)(f) GDPR (the customer's legitimate interest in answering enquiries promptly); towards these contacts we act as the customer's processor.
Meta may transfer data to Meta Platforms, Inc. in the USA. The transfer is safeguarded by the EU-US Data Privacy Framework and EU Standard Contractual Clauses (Art. 46 GDPR). Meta bills the delivery of WhatsApp messages directly to the customer. Further information: https://www.facebook.com/privacy/policy/ and https://www.whatsapp.com/legal/privacy-policy-eea.
6.21 Customer service messages via Telegram
Since October 2026 customers can additionally connect their own Telegram bot. Telegram is provided by Telegram FZ-LLC, Dubai, United Arab Emirates. We process the content of the messages sent to this bot, the Telegram identifier of the person writing, their display and user name and timestamps, and send the assistant's replies back via Telegram. We store the bot's access key encrypted. The United Arab Emirates have no adequacy decision of the EU Commission; the transfer takes place because the person writing uses Telegram and contacts the bot themselves (Art. 49(1)(b) GDPR). Legal bases and our role as the customer's processor apply as above. More information: https://telegram.org/privacy.
Images and documents a contact sends to the assistant via WhatsApp, Instagram, Facebook, Telegram or email (images, PDF, Office documents and text files, at most 10 MB per file) are handled like files attached in the chat widget: we download them from the respective provider, check them for harmful content and store them for 90 days on our servers in the EU (AWS, Frankfurt region). The readable text of documents and what an AI image model recognizes in images and scanned PDF files are passed to the AI assistant, together with the file's name, type and size, as part of the conversation (see section 5); for the recognition the image or the page images (at most three pages) are sent via OpenRouter, Inc. to a model from Google (Gemini), or alternatively from OpenAI. The legal bases and our role as the customer's processor apply as above.
6.22 Address book
In the customer area customers can keep an address book of their contacts. We store the details entered or imported by the customer, in particular salutation, title, first and last name, company, position, phone numbers, e-mail addresses, messenger handles, postal address, birthday, website, notes and the preferred form of address, as well as a logbook per contact with summaries of earlier conversations and the customer's own notes. The data is stored in our own infrastructure in the EU (AWS, Frankfurt region).
When a contact writes from a stored e-mail address, WhatsApp number or messenger handle, the assistant assigns them automatically and receives, for this conversation only, the details and logbook of exactly this contact; for this purpose they are transmitted, like the rest of the conversation, to the AI providers named in section 5. The assistant cannot search the address book or give information about other contacts. After the conversation the summary is written into the contact's logbook. When a contact calls from a stored phone number, the assistant on our own telephony infrastructure receives, for this call only, the name and the latest logbook entries of exactly this contact; on calls via Vapi it receives no address book data. After the call the summary is written into the logbook.
When a person who is not yet in the address book reaches an assistant by call or message, we automatically create a contact, solely from the identifier the channel transmits (the caller's phone number, WhatsApp number, e-mail address or messenger handle). If the person states their name or further contact details themselves during the conversation, we store this as their own statement on exactly this contact; nobody is recognised by a further phone number, e-mail address or handle stated in this way. The person can correct their name themselves during the conversation, and the previous name remains in the logbook. Contacts marked as private are not changed by this.
So that names are spelled correctly in transcripts, summaries and translations of conversations, we compile a spelling aid (glossary) for every assistant. It contains the name fonella, the company and assistant name, names of team members and forwarding targets, the pronunciation rules stored by the customer, distinctive proper names from the assistant's knowledge, and the first name, last name and company of the address book contacts with the most logbook entries (at most 30 entries, without contacts marked as private). Phone numbers, e-mail addresses, postal addresses and notes are not part of it. The glossary is passed as search terms to speech recognition (Deepgram, and for calls via Vapi also Vapi) and to the AI providers named in section 5 when they create the summary and translation of a conversation; the assistant itself does not receive it during the conversation. The glossary is rebuilt whenever the address book, team, forwarding targets, knowledge or account data change, and is deleted with the user account at the latest.
If the customer links an external address book via CardDAV (for example Apple iCloud), we retrieve the contacts there with the credentials stored by the customer; the password is stored encrypted (AES-256-GCM). For Apple, the information on the provider and third-country transfers in section 6.16 applies accordingly. The legal basis is Art. 6(1)(b) GDPR towards the customer and, towards the stored contacts, Art. 6(1)(f) GDPR (the customer's legitimate interest in handling enquiries personally and quickly); towards these contacts we act as the customer's processor. Customers can delete contacts and logbook entries at any time; at the latest we delete them together with the user account.
7. Disclosure of data
Your personal data is not transferred to third parties for purposes other than those listed in this privacy policy. We disclose personal data to third parties only if you have given explicit consent pursuant to Art. 6(1)(a) GDPR, disclosure is required pursuant to Art. 6(1)(f) GDPR to assert, exercise, or defend legal claims and there is no reason to assume you have an overriding legitimate interest in non-disclosure, a legal obligation pursuant to Art. 6(1)(c) GDPR applies, or disclosure is legally permitted and required pursuant to Art. 6(1)(b) GDPR to process contractual relationships with you.
We use processors (e.g. hosting providers such as AWS, analytics services such as Google, and CRM services such as HubSpot per section 6.4) within the EU or with adequate safeguards (e.g. standard contractual clauses). A list of processors is available on request.
The recipient of data in connection with the review widget (section 6.14) is B A Media Group FZE LLC, Sharjah, United Arab Emirates, as operator of Trustportal. Where data is processed in a third country in this context, this is based on your consent (Art. 49(1)(a) GDPR).
8. Rights of data subjects
a) Right of access (Art. 15 GDPR): You have the right to obtain information about your personal data processed by us, including categories, recipients, and retention period.
b) Right to rectification (Art. 16 GDPR): You have the right to obtain without undue delay the rectification of inaccurate personal data or completion of incomplete data stored by us.
c) Right to erasure (Art. 17 GDPR): You have the right to obtain erasure of your personal data stored by us unless statutory retention obligations prevent this.
d) Right to restriction of processing (Art. 18 GDPR): Under certain conditions you have the right to restrict processing of your personal data (e.g. where accuracy is contested).
e) Right to data portability (Art. 20 GDPR): You have the right to receive your personal data in a structured, commonly used, machine-readable format.
f) Withdrawal of consent (Art. 7(3) GDPR): Where processing is based on consent, you may withdraw it at any time with effect for the future (e.g. by email to info@fonella.ai). Lawfulness of processing before withdrawal remains unaffected.
g) Right to object (Art. 21 GDPR): Where personal data is processed on the basis of legitimate interests pursuant to Art. 6(1)(f) GDPR, you have the right to object to processing, in particular to direct marketing. Objection may be made informally.
h) Right to lodge a complaint (Art. 77 GDPR): You have the right to lodge a complaint with a supervisory authority. The authority responsible for us is the Brandenburg Commissioner for Data Protection and the Right of Access to Files, Stahnsdorfer Damm 77, 14532 Kleinmachnow.
9. Cookies and consent
(1) Our website uses technically necessary cookies required for operation. These cookies are set on the basis of Art. 6(1)(f) GDPR in conjunction with § 25(2) TDDDG.
(2) For analytics cookies (e.g. Google Analytics), marketing cookies, and similar technologies, we obtain your prior consent pursuant to Art. 6(1)(a) GDPR in conjunction with § 25(1) TDDDG via our cookie banner. You may withdraw consent at any time via our cookie consent tool.
10. Data security
When you visit our website, we use the widespread SSL procedure (Secure Socket Layer) together with the highest encryption level supported by your browser (at least TLS 1.3). All data flows are encrypted and auditable. We also implement organisational and technical measures to protect your data, such as firewalls, intrusion detection systems, regular backups, and staff training. In the event of a data breach, we inform affected persons and authorities pursuant to Art. 33/34 GDPR.
11. Automated decision-making and profiling
We do not carry out automated decision-making within the meaning of Art. 22 GDPR. Profiling is performed only in anonymised form for analytics purposes (e.g. via Google Analytics), without individual impact on you.
12. Notice pursuant to the EU AI Act
(1) Pursuant to Art. 50(1) of Regulation (EU) 2024/1689, we point out that our service involves the use of an AI system. Persons interacting with the AI phone assistant are clearly and understandably informed at the start of the call that they are communicating with an AI system.
(2) The AI systems we use are currently assessed as limited-risk AI systems under the EU AI Act. We fulfil the resulting transparency obligations and proactively inform callers about the use of artificial intelligence.
(3) Where synthetic audio content is generated in the service (text-to-speech), it must be labelled as artificially generated pursuant to Art. 50(2) of Regulation (EU) 2024/1689. Labelling is provided by the information at the start of the call.
13. Currency and changes to this privacy policy
This privacy policy is current as of November 2026. Due to the further development of our website and services or changes in legal or regulatory requirements, it may become necessary to amend this privacy policy. The current version is available on our website. Material changes will be communicated to you by email if we hold your contact details.