Contents
Parties
This Data Processing Agreement (“DPA”) forms part of the Foneklar Terms of Service (“Terms”). It applies whenever Foneklar processes personal data on the Customer’s behalf while providing the Services, and it is concluded when the Customer accepts the Terms. No separate signature is needed; customers who need a countersigned copy can request one at privacy@foneklar.com.
1Definitions and scope
Terms such as “personal data”, “processing”, “controller”, “processor”, “data subject”, “personal data breach” and “supervisory authority” have the meanings given in the General Data Protection Regulation (Regulation (EU) 2016/679, “GDPR”).
“Customer Personal Data” means personal data that Foneklar processes on behalf of the Customer in providing the Services.
“Services” means the Foneklar services described in the Terms, in particular:
- answering the Customer’s calls with an AI voice agent;
- building the agent’s knowledge from the Customer’s website and documents;
- taking callback requests and passing them to the Customer;
- test calls; and
- the dashboard in which the Customer manages all of this.
“Callers” means people who call the Customer and speak with the voice agent.
“Sub-processor” means another processor that Foneklar engages to process Customer Personal Data.
This DPA does not cover processing for which Foneklar is itself the controller, such as managing the Customer’s account and billing, visits to the Foneklar website, or compliance with Foneklar’s own legal obligations. The Foneklar privacy policy describes that processing.
2Subject matter, nature, purpose and duration
The subject matter of the processing is the provision of the Services. Annex 1 describes the categories of data subjects and personal data, and the nature and purpose of the processing.
Foneklar processes Customer Personal Data only to provide the Services to the Customer, which includes keeping them secure, available and working correctly.
Foneklar does not process Customer Personal Data for its own purposes. In particular, Foneklar does not sell it, does not use it for advertising or profiling, does not combine it with the data of other customers, and does not use it to train AI models (clause 7).
The processing lasts for the term of the Terms and ends with the deletion of Customer Personal Data under clause 12.
3The Customer’s responsibilities
The Customer is the controller. It is responsible for the lawfulness of the processing, including the legal basis for answering, recording and storing calls and, where callers share special categories of personal data such as health data, for meeting Article 9 GDPR.
The Customer informs callers about the processing as required by Articles 13 and 14 GDPR, for example in its privacy notice and with a short notice at the start of calls. Foneklar provides a template text on request.
The Customer decides which features it uses, such as call recording, notes on returning callers and the sources the agent learns from. It makes sure that the pages and documents it provides contain no more personal data than the agent needs (for example, no patient or guest lists).
The Customer does not use the Services for emergency calls, and does not instruct the agent to ask callers for special categories of personal data unless this is necessary and lawful.
The Customer keeps its users’ access data confidential, manages who in its organisation has access, and tells Foneklar without undue delay if it finds errors or irregularities in the processing.
4Instructions
Foneklar processes Customer Personal Data only on the Customer’s documented instructions, including with regard to transfers to third countries, unless Union or Member State law requires otherwise. In that case, Foneklar informs the Customer of that legal requirement before processing, unless the law prohibits this on important grounds of public interest.
The Customer’s instructions are set out in this DPA and the Terms, and are given through the settings the Customer chooses in the dashboard. The Customer may give further instructions in text form, for example by email to privacy@foneklar.com. Foneklar documents the instructions it receives. Instructions that go beyond the agreed Services are treated as a request to change them.
Foneklar informs the Customer immediately if, in its opinion, an instruction infringes the GDPR or other data protection law. Foneklar may suspend carrying out such an instruction until the Customer confirms or changes it.
5Confidentiality and professional secrecy
Foneklar ensures that everyone authorised to process Customer Personal Data has committed themselves to confidentiality or is under an appropriate statutory obligation of confidentiality. This obligation continues after their work for Foneklar ends.
Foneklar staff access Customer Personal Data only as far as needed to provide the Services, for example to resolve a support request. Each time Foneklar staff listen to a call recording, this is logged.
If the Customer is bound by professional secrecy, for example as a medical or dental practice, a law firm or a tax adviser (such as under Section 203 of the German Criminal Code (StGB), Section 54 of the Austrian Physicians Act (ÄrzteG) or Section 9 of the Austrian Lawyers’ Act (RAO)), Foneklar acknowledges that it assists the Customer in its professional activity. Foneklar keeps all secrets entrusted to it confidential, takes note of them only to the extent required to provide the Services, and obliges everyone it involves who may learn of such secrets, in text form, to keep them confidential, pointing out the consequences of a breach under criminal law.
6Security of processing
Foneklar implements appropriate technical and organisational measures under Article 32 GDPR, taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of the processing, and the risks to the rights and freedoms of the people concerned. Annex 2 sets out these measures.
The measures are subject to technical progress. Foneklar may update them, provided that the level of protection is not reduced. Foneklar documents significant changes.
Foneklar regularly tests, assesses and evaluates the effectiveness of the measures.
7Artificial intelligence
No training. Foneklar does not use Customer Personal Data, including call audio, transcripts and recordings, to train or fine-tune AI models, or to develop products for other customers. Foneklar engages AI providers only on terms under which they do not use Customer Personal Data to train their models. Foneklar develops and tests its Services with synthetic calls.
No voice biometrics. Callers’ voices are processed only to turn speech into text and to answer. Foneklar does not create voice profiles, does not identify or recognise people by their voice, and does not infer emotions from voice characteristics. The agent may adapt the wording of its replies to what a caller says, based only on the transcribed words.
Disclosure as an AI. The agent tells every caller at the start of the call that they are speaking with an AI (Article 50 of the EU Artificial Intelligence Act). The Customer does not switch this off or disguise it.
No automated decisions. The agent gives information from the Customer’s own sources and records requests. It does not take decisions that produce legal effects concerning callers or similarly significantly affect them (Article 22 GDPR). Bookings, appointments, cancellations and refunds are decided by the Customer’s staff.
Limits on answers. The agent answers only from the sources the Customer provides. It hands emergencies and medical, legal and financial questions to the Customer’s staff and does not advise on them. Every caller utterance is screened for misuse, such as attempts to manipulate the agent.
Consent. Calls are recorded only after the caller agrees. Notes on returning callers are kept only for callers who agree to their conversation being stored.
8Sub-processors
The Customer gives Foneklar general authorisation to engage sub-processors. The sub-processors listed in Annex 3 are approved when this DPA is concluded.
Foneklar informs the Customer at least 14 days in advance of any intended addition or replacement of a sub-processor, by email to the account owner and by updating Annex 3. This also applies when the scope of an existing sub-processor is extended, in particular to a new processing location.
The Customer may object to the change in text form within 14 days of the notice, on reasonable data protection grounds. Foneklar will then work with the Customer to find a solution. If none is found, Foneklar will not use the new sub-processor for the Customer’s data; if this makes it impossible to provide the Services, either party may terminate the affected Services with effect from the date of the change, and Foneklar refunds any fees paid in advance for the period after termination.
If a sub-processor has to be replaced urgently to protect data or to keep the Services running, Foneklar may do so without prior notice, provided that the new sub-processor processes Customer Personal Data in the EU or EEA under equivalent guarantees. Foneklar informs the Customer without undue delay, and the Customer’s right to object under clause 8.3 applies from that notice.
Foneklar engages each sub-processor under a contract that imposes the same data protection obligations as this DPA, in particular sufficient guarantees for appropriate technical and organisational measures (Article 28(4) GDPR). Foneklar checks these guarantees before the engagement and regularly afterwards.
Foneklar remains fully liable to the Customer for the performance of its sub-processors’ obligations.
Providers without access to Customer Personal Data are not sub-processors. Nor are providers that the Customer chooses and contracts with itself, such as its own telephone provider or booking system.
9Location of processing and international transfers
Foneklar stores and processes Customer Personal Data in the European Union or the European Economic Area. Each sub-processor is set up to process it in the locations shown in Annex 3. This includes call audio in transit: the voice platform routes it only through its servers in the EU.
Foneklar does not fail over to locations outside the EU or EEA. If a service in the EU is unavailable, Foneklar switches only to another location or provider within the EU or EEA.
Some sub-processors are, or belong to, companies based in the United States. Where Customer Personal Data could be accessed from a third country, for example for support or by a parent company, the transfer is based on an adequacy decision (in particular the EU-US Data Privacy Framework, for certified companies) or on the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), together with supplementary measures such as encryption in transit and at rest.
Foneklar transfers Customer Personal Data to a third country only in accordance with this DPA and Chapter V GDPR.
10Assistance to the Customer
Taking into account the nature of the processing, Foneklar assists the Customer with appropriate technical and organisational measures in responding to requests from data subjects exercising their rights under Chapter III GDPR. In the dashboard, the Customer can view and erase callback requests, call recordings and notes on returning callers at any time.
If a data subject contacts Foneklar directly, Foneklar forwards the request to the Customer without undue delay and does not respond itself unless the Customer instructs it to.
Foneklar assists the Customer in meeting its obligations under Articles 32 to 36 GDPR (security, notification of breaches, data protection impact assessments and prior consultation), taking into account the information available to Foneklar. On request, Foneklar provides the information the Customer needs for its record of processing activities.
Foneklar informs the Customer without undue delay of any inspection or measure by a supervisory authority, and of any request from an authority, that concerns Customer Personal Data, unless the law prohibits this.
Foneklar maintains its own record of processing activities as a processor (Article 30(2) GDPR).
Foneklar may charge reasonable fees for assistance that goes beyond the self-service functions of the Services and beyond its legal obligations, unless the assistance is needed because Foneklar breached this DPA.
11Personal data breaches
Foneklar notifies the Customer of any personal data breach affecting Customer Personal Data without undue delay, and no later than 24 hours after becoming aware of it.
The notification contains, as far as available, the information listed in Article 33(3) GDPR: the nature of the breach, including the categories and approximate number of data subjects and records concerned; a contact point; the likely consequences; and the measures taken or proposed to address the breach and mitigate its effects. Where not all information is available at once, Foneklar provides it in phases without further undue delay.
Foneklar immediately takes the measures needed to secure the data, investigate the breach and mitigate its possible adverse effects, and documents the breach.
Notifying supervisory authorities and data subjects remains the Customer’s responsibility. Foneklar makes such notifications only on the Customer’s instruction.
Notifying a breach is not an acknowledgement of fault or liability.
12Deletion and return
During the term, Customer Personal Data is deleted according to the retention periods in Annex 4, and the Customer can erase data in the dashboard at any time.
The Customer may request a copy of its Customer Personal Data in a common, machine-readable format up to 30 days after the Terms end. Foneklar then deletes all Customer Personal Data, at the latest 30 days after the end of the Terms, unless Union or Member State law requires it to be stored. Copies in backups are overwritten in the regular backup cycle within a further 14 days and are not restored in the meantime.
Foneklar confirms the deletion in text form on request.
13Information and audits
Foneklar makes available to the Customer all information necessary to demonstrate compliance with Article 28 GDPR and this DPA, and allows for and contributes to audits, including inspections, conducted by the Customer or an auditor it mandates.
Foneklar first provides documentation, such as this DPA and its annexes, the certifications and audit reports of its sub-processors, and written answers to reasonable questions.
If this is not sufficient, if a supervisory authority requires it, or if there are concrete indications of a breach, the Customer may carry out an on-site audit. The Customer announces it at least 30 days in advance (less in the case of a breach). It takes place during normal business hours without disrupting operations and, unless there has been a breach, at most once per calendar year. Auditors must be bound to confidentiality and must not be competitors of Foneklar. Sub-processors are audited by means of their certifications and audit reports.
Each party bears its own costs. Foneklar may charge reasonable fees for on-site audits that take more than one working day, unless the audit reveals a material breach of this DPA by Foneklar.
14Liability
The parties are liable to data subjects in accordance with Article 82 GDPR. Liability between the parties is otherwise governed by the Terms.
15Term and termination
This DPA takes effect when the Customer accepts the Terms and ends when the Terms end. Clauses that by their nature continue, in particular clauses 5, 11 and 12, remain in force for as long as Foneklar processes Customer Personal Data.
The Customer may terminate the Terms with immediate effect if Foneklar seriously breaches this DPA and does not remedy the breach within a reasonable period after being asked to do so.
16Final provisions
If this DPA conflicts with the Terms, this DPA prevails in matters of data protection. Where Standard Contractual Clauses apply, they prevail over this DPA.
Changes to this DPA must be made in text form. Foneklar may update Annex 2 under clause 6.2 and Annex 3 under clause 8. Foneklar may make other changes, for example because of new legislation or new features, by notifying the Customer at least 30 days in advance; changes that reduce the protection of Customer Personal Data require the Customer’s consent.
If any provision of this DPA is or becomes invalid, the remaining provisions are not affected. The invalid provision is replaced by a valid one that comes closest to its purpose.
This DPA is governed by Austrian law, excluding its conflict-of-laws rules. To the extent permitted by law, the exclusive place of jurisdiction is Salzburg, Austria.
This DPA is made in German and English. In case of discrepancies, the German version prevails.
Description of the processing
Data subjects
- Callers: people who call the Customer, for example guests, patients, customers, suppliers and applicants, and people they mention during the call.
- The Customer’s users: owners and staff of the Customer who use the dashboard.
- People named in the Customer’s sources: for example staff and contact persons named on the Customer’s website or in documents the Customer uploads.
Personal data
- Voice: the audio of the call, processed in real time
- Phone number (caller ID), where the telephone network transmits it
- What is said: the transcribed words of the caller and the agent’s replies
- Callback requests: name, phone number, language and the request in the caller’s own words
- Call details: date, time, duration, language, outcome and the caller’s consent decision
- Call recording, if the caller agrees and the Customer has turned recording on
- Short notes from earlier calls, if the caller agrees to their conversation being stored
- Name, email address and role
- Password, stored only as a hash, and login sessions
- IP address and browser information in security logs
- Actions in the dashboard
- Names, roles and business contact details contained in the website pages and documents the Customer provides
Special categories of personal data
The agent does not ask for special categories of personal data. Callers may share them of their own accord, for example health information when calling a medical practice, or an allergy when booking a table. The agent hands medical questions to the Customer’s staff. Where such data is processed, the measures in Annex 2 apply to it in the same way.
Nature of the processing
Receiving and transmitting call audio in real time; converting speech to text and text to speech; analysing transcribed requests with AI language models to understand them, screen them for misuse and answer them from the Customer’s sources; storing, displaying and deleting callback requests, recordings and caller notes; reading the Customer’s website and documents to build the agent’s knowledge; sending emails to the Customer’s users; monitoring and troubleshooting.
Purpose
Providing the Services: answering the Customer’s calls, passing on callback requests, showing calls in the dashboard, and keeping the Services secure and running.
Duration and frequency
Continuously, for the term of the Terms. Retention periods are set out in Annex 4.
Technical and organisational measures
These measures describe the Services as they run today. They apply to all Customer Personal Data, including special categories.
1. Confidentiality
Physical access
- Foneklar runs no servers of its own. All systems run in data centres of Google Cloud, Microsoft Azure, Amazon Web Services (through Neon) and LiveKit, which protect their premises with access control and hold recognised security certifications such as ISO/IEC 27001 or SOC 2.
- Customer Personal Data is not kept on paper or on local storage outside these systems. Work devices use full-disk encryption and lock automatically.
System access
- Every person has their own account; there are no shared logins. Administrative access to cloud and code-hosting accounts requires multi-factor authentication.
- The application server accepts only HTTPS from the internet. Administrative access is possible only through Google’s Identity-Aware Proxy; there is no open SSH port.
- Operating system security updates are installed automatically. Services run under unprivileged accounts, each with its own system user.
- The website scanner runs in a sandboxed browser under a separate system user, without access to the application’s configuration.
- Users’ passwords are stored only as salted hashes. Login sessions are stored as token hashes and expire after inactivity and after a maximum lifetime.
Data access
- Access rights follow the principle of least privilege. Each service (API, website scanner, knowledge processing, voice agent) has its own database login with only the rights it needs.
- Row-level security separates customers’ knowledge data. The voice agent’s database login cannot read callback requests, callers’ phone numbers or caller notes.
- Each customer workspace is isolated; users see only the data of their own workspace.
- Foneklar staff access customer data only for support and operations. Listening to a call recording and viewing a customer’s knowledge are logged.
Separation
- Development and testing use synthetic calls and test data, not real callers’ data. Test environments are separate from production.
Pseudonymisation and data minimisation
- Notes on returning callers are stored under a keyed hash (HMAC-SHA256) of the phone number, never under the number itself.
- The call log contains no caller words, names or phone numbers. Transcripts are not stored in the Foneklar database.
- The voice platform’s own storage of call audio and transcripts is switched off.
- On request, for example for healthcare customers, conversation content is excluded from monitoring traces, which then contain only timings and technical metrics.
2. Integrity
Transfer control
- All connections are encrypted with TLS 1.2 or higher, and the website enforces HTTPS (HSTS). Call audio is transmitted encrypted (DTLS-SRTP).
- Region pinning keeps the voice platform’s signalling and call audio on servers in the EU; connections to servers elsewhere are refused.
- Messages from the voice agent to the application (callback requests, recordings, call summaries) are signed and rejected without a valid signature. The application’s API accepts requests only through the dashboard’s authenticated proxy.
Input control
- Administrative actions such as test calls, listening to recordings and viewing customer knowledge are logged with the user and the time.
- Changes to code and database structure are versioned, reviewed and tested automatically before deployment.
3. Availability and resilience
- Data at rest (database, disks and backups) is encrypted with AES-256.
- The database is backed up every night to Cloud Storage in Frankfurt, and backups are kept for 14 days. The database provider also offers point-in-time recovery.
- Restore points are created before major changes, and every component has a documented rollback procedure.
- Each new version of the voice agent must pass automated test calls before it is released.
- If the speech-to-text provider fails, the agent switches to a second provider in the EU.
4. Regular review and privacy by design
- Privacy contact: privacy@foneklar.com. The measures are reviewed at least once a year and whenever the Services change significantly.
- A documented procedure for handling personal data breaches, including notifying customers within 24 hours.
- Privacy by default: recording only after the caller agrees, caller notes only with consent, and automatic deletion (Annex 4).
- EU-only processing is enforced in code: the voice agent starts its voice services only in its EU project.
- Sub-processors are chosen for their data protection guarantees and EU locations, bound by data processing agreements and reviewed regularly.
- Dependencies and source code are scanned for known vulnerabilities and leaked secrets, and security reviews take place before major releases.
- Access credentials are kept in a secrets manager in Frankfurt and in access-restricted server configuration, never in source code.
- Staff are bound to confidentiality and instructed in data protection.
Sub-processors
As of 12 November 2026, the following sub-processors are approved. Each is set up to process Customer Personal Data in the EU.
LiveKit, Inc.
Seat: USA- Service
- Real-time voice transport for calls and test calls; hosting of the voice agent; access to speech models through LiveKit Inference.
- Data
- Call audio (in real time), call details, technical logs.
- Where
- European Union: EU data region, voice agent hosted in Frankfurt, Germany. Call audio is routed only through LiveKit servers in the EU (region pinning) and is not stored.
- Safeguards
- EU-US Data Privacy Framework; EU Standard Contractual Clauses.
Through LiveKit Inference, LiveKit uses these providers of its own, on EU endpoints and without storing audio or text:
- Cartesia, Inc. (USA): text-to-speech: the agent’s voice
- Deepgram, Inc. (USA): backup speech-to-text
AssemblyAI, Inc.
Seat: USA- Service
- Speech-to-text: turns callers’ speech into text.
- Data
- Call audio (in real time), transcribed text.
- Where
- European Union (AssemblyAI’s EU endpoint).
- Safeguards
- EU-US Data Privacy Framework; EU Standard Contractual Clauses.
Microsoft Ireland Operations Limited
Seat: Ireland- Service
- Azure OpenAI Service (GPT-5.4 mini): understanding requests, screening for misuse, answering from the Customer’s sources, writing caller notes and call summaries; preparing the knowledge from the Customer’s website and documents.
- Data
- Transcribed call content; content of the Customer’s website and documents.
- Where
- EU Data Zone (data centres in EU member states).
- Safeguards
- EU company. For access by Microsoft Corporation (USA): EU-US Data Privacy Framework and Standard Contractual Clauses.
Google Cloud EMEA Limited
Seat: Ireland- Service
- Hosting of the application server (dashboard backend, website scanner, knowledge processing), storage of call recordings and uploaded files, and database backups.
- Data
- All Customer Personal Data stored by the Services.
- Where
- Frankfurt, Germany (europe-west3).
- Safeguards
- EU company. For access by Google LLC (USA): EU-US Data Privacy Framework and Standard Contractual Clauses.
Neon, Inc.
Seat: USA- Service
- Managed PostgreSQL database.
- Data
- Users’ account data, callback requests, caller notes, call log and knowledge.
- Where
- Frankfurt, Germany (AWS eu-central-1).
- Safeguards
- EU-US Data Privacy Framework; EU Standard Contractual Clauses.
Vercel Inc.
Seat: USA- Service
- Hosting of the Foneklar website and dashboard.
- Data
- Data shown to the Customer’s users in the dashboard; IP addresses.
- Where
- Server functions in Frankfurt, Germany; delivery through Vercel’s global network, from European locations for users in Europe as a rule.
- Safeguards
- EU Standard Contractual Clauses.
ClickHouse, Inc. (Langfuse Cloud)
Seat: USA- Service
- Monitoring of calls: the timing, cost and quality of each turn.
- Data
- Call details, transcribed turns and model prompts (can be switched off per customer).
- Where
- European Union (Langfuse EU region). Traces are deleted after 30 days.
- Safeguards
- EU-US Data Privacy Framework; EU Standard Contractual Clauses.
Amazon Web Services EMEA SARL
Seat: Luxembourg- Service
- Sending account emails (Amazon SES), such as email verification and password resets.
- Data
- Users’ names and email addresses.
- Where
- Frankfurt, Germany (eu-central-1).
- Safeguards
- EU company. For access by Amazon Web Services, Inc. (USA): EU-US Data Privacy Framework and Standard Contractual Clauses.
Retention periods
| Data | Kept for |
|---|---|
| Call audio during the call | Processed in real time only, not stored |
| Call recordings (only with the caller’s consent) | 90 days after the call |
| Callback requests: name, phone number and request | 30 days after being marked done; while open, 90 days after arrival |
| Notes on returning callers (only with consent; at most the last five calls) | 90 days after the caller’s last call |
| Call log: time, duration, outcome (no caller words, names or numbers) | For the term of the contract |
| Monitoring traces of calls | 30 days |
| Technical logs | 30 days |
| Record of erased callback requests (identifier and time only) | 90 days |
| Test-call limits | 1 day |
| Website pages, documents and the knowledge built from them | Until the Customer deletes them or the contract ends |
| User accounts | For the term of the contract; login sessions expire automatically |
| Backups | 14 days |
The Customer can erase callback requests, recordings and caller notes earlier, at any time, in the dashboard. When the contract ends, clause 12 applies.
Version history
- 1.012 November 2026First version.
Questions about this agreement?
Write to privacy@foneklar.com. Voicelap Technologies GmbH, Sterneckstraße 35, Top 201A3, 5020 Salzburg, Austria.