Data processing agreement for LynBro AI-telefon
Version 2026-10-20. Pursuant to Article 28(3) of the General Data Protection Regulation (GDPR). English translation; the Danish text prevails.
Controller: the customer as stated when the account is created (name, CVR no., address) ("the customer").
Processor: LynBro ApS, CVR no. 46321499, Rødovre Parkvej 276, 2610 Rødovre, Denmark, hello@lynbro.dk ("the processor").
1. Background
1.1. The customer uses LynBro AI-telefon under the terms of service ("the main agreement"). The processor thereby processes personal data about the customer's callers, customers and staff on the customer's behalf.
1.2. This agreement is concluded when the customer accepts the terms of service and forms part of them. In case of conflict, this agreement prevails as regards the protection of personal data.
1.3. The customer is responsible for the processing being lawful, including the legal basis, informing data subjects and the information and instructions the customer puts into the service. The processor may provide templates (e.g. a greeting and a text for the customer's website), but the customer approves and is responsible for the texts used under its name.
1.4. Data about the customer itself and its users (account, billing, identity checks for number orders) is processed by the processor as an independent controller under its privacy policy and is not covered by this agreement.
2. Instructions
2.1. The processor processes personal data only on documented instructions, unless EU or Danish law requires otherwise. The customer's use of the service is the instruction: the features the customer switches on and the settings it chooses (e.g. retention periods, integrations, webhooks, notification channels and own OpenAI account). Further instructions are given in writing (email suffices).
2.2. The processor informs the customer immediately if, in its opinion, an instruction infringes data protection law.
2.3. The processor is not obliged to follow an instruction that the service does not support or that requires separate development. If the parties cannot agree, the customer may terminate the main agreement.
2.4. The processor does not use the customer's data for its own purposes and does not sell it. Anonymised and aggregated operational figures that cannot be linked to an individual or a customer may be used to operate, secure and improve the service.
2.5. The statement that the caller is talking to an AI (AI Act art. 50) is part of the service and cannot be removed by instruction.
3. Confidentiality and security
3.1. Only persons who need access have it, and they are bound by confidentiality. Support access to the customer's data takes place only at the customer's request, to fix an error or a security problem, or to prevent or investigate misuse.
3.2. The processor takes measures under art. 32 as described in Annex C and may change them as long as the level of security is not reduced.
3.3. The customer is responsible for its own passwords and users, API keys, webhook addresses and own supplier accounts (e.g. its own OpenAI account or phone system).
4. Sub-processors
4.1. The customer gives general prior authorisation to the use of sub-processors, including those listed in Annex B.
4.2. Additions or replacements of a sub-processor are announced at least 30 days in advance by email and/or in the service and at pbx-app.lynbro.dk/legal/dpa. If a sub-processor must be replaced for security reasons, because it discontinues its service or because the law requires it, the notice may be shorter; the processor then informs the customer as soon as possible.
4.3. The customer may object on reasonable grounds within the notice period. If the parties cannot agree, the customer may terminate the affected part of the service free of charge before the change takes effect. This is the customer's sole remedy.
4.4. Sub-processors are bound by the same data protection obligations as in this agreement, and the processor is liable for them under art. 28(4).
5. Transfers to third countries
Data is stored on servers in the EU. Transfers outside the EU/EEA take place only to the sub-processors in Annex B where this is stated, and only under GDPR Chapter V (standard contractual clauses and/or the EU-US Data Privacy Framework). The customer acknowledges that OpenAI's European data residency is currently not enabled and that calls may therefore be processed in the USA.
6. Assistance
6.1. The processor assists the customer with requests from data subjects (art. 12-22). The service offers self-service for automatic deletion according to the customer's retention settings and for erasure of a caller's data by phone number. Data is provided on request. The processor also assists with art. 32-36, taking into account the nature of the processing and the information available to it.
6.2. Requests from data subjects are forwarded to the customer without undue delay and are not answered by the processor.
6.3. Assistance beyond self-service and normal support may be invoiced at the processor's current hourly rate.
7. Personal data breaches
The processor notifies the customer without undue delay and where possible within 24 hours after becoming aware of a breach affecting the customer's data, with the information available and required under art. 33(3). Information not available at once is provided as it becomes available. The customer notifies Datatilsynet; the processor assists.
8. Audit
The processor provides the information necessary to demonstrate compliance with this agreement, primarily in writing. At most once a year and with 30 days' notice, the customer may have an independent auditor bound by confidentiality carry out an audit without access to other customers' data and without disrupting operations. The customer pays its own costs and the processor's time at its current hourly rate, unless the audit reveals a material breach. Supervision by an authority always takes precedence.
9. Termination
Until the main agreement ends and for 30 days afterwards, the customer may request its data in a common machine-readable format. The processor then deletes it. Backups are deleted with the backup cycle. Data the law requires to be kept is kept for that purpose only.
10. Liability
10.1. Liability follows the main agreement, including its limitation of liability and cap (the amount the customer paid for the service in the 12 months before the event causing the loss). Art. 82 GDPR towards data subjects is not affected.
10.2. The processor is not liable for loss, fines or claims resulting from the customer's instructions, content, texts, failure to inform data subjects, own supplier accounts or choice of integrations, and the customer indemnifies the processor against such claims.
10.3. The limitations do not apply in case of intent or gross negligence.
11. Term, changes, transfer and governing law
11.1. This agreement applies while the processor processes personal data for the customer.
11.2. The processor may change this agreement and its annexes under the main agreement's rules on changes. Changes required by new legislation, a decision or guidance of an authority or new standard clauses may apply from the time they are required. Changes to the customer's disadvantage entitle the customer to terminate free of charge.
11.3. Transfer. The processor may transfer this agreement, including rights and obligations and the personal data processed in connection with the service, to another company as part of a transfer of the service or the part of the business that operates it. The customer is notified in writing at least 30 days before the transfer, with the new processor's name and CVR number. The new processor assumes all obligations under this agreement. Within the notice period the customer may object and terminate this agreement and the affected part of the main agreement free of charge with effect from the date of transfer.
11.4. Danish law. Disputes are settled by the Copenhagen City Court (Københavns Byret) as the first instance.
Annex A — The processing
| Purpose | Answering the customer's phone calls with an AI assistant; phone numbers and call forwarding; call log, transcript and summary; bookings, changes and cancellations in the customer's own or external booking system; messages and callback requests; customer register and knowledge base; notifications and integrations the customer switches on (e.g. partner API, webhooks, email or Telegram, transcription of audio files from the customer's telecom operator) |
|---|---|
| Nature | Receiving audio in real time and passing it to the language model, transcription, summarising, storage, search, display, transfer to the customer's systems and channels, backup, deletion. Audio of AI calls is not stored by the processor. Audio files from the customer's telecom operator (voicemail or calls with staff) for which the customer has switched on transcription are deleted after transcription |
| Data subjects | People who call the customer or are called by it; the customer's customers; the customer's staff, to the extent mentioned in calls or acting as users |
| Data | Phone number, time, duration, language; what is said in the call; transcript, summary and topics; name and appointments if the person is a customer of the customer; bookings, messages and callback requests |
| Special categories | The service is not intended for special categories of data (art. 9), CPR numbers or payment card data. By default the assistant is instructed not to ask for them, and the customer must not set it up to collect them without a written agreement. If a caller mentions them, they form part of the transcript and are deleted with it |
| Retention | According to the customer's settings. By default transcript and summary 180 days and call log 730 days. If the customer chooses "no automatic deletion", that is the customer's instruction. Then under section 9 |
| Location | Servers in the EU (Annex B); the language model under Annex B |
Annex B — Sub-processors
| Sub-processor | Service | When | Location and transfer |
|---|---|---|---|
| netcup GmbH, Germany | Servers: telephony and control panel, database, backups | Always | Germany (EU) |
| Contabo GmbH, Germany | Servers for the processor's own mail server and CRM system: sending email, including notifications, and CRM synchronisation when the customer has switched it on | When email notifications or CRM are switched on | Germany (EU) |
| Zadarma (telecom operator) | Phone numbers, call transport (SIP), SMS; audio files from the customer's own phone system if the customer has switched this on | When the customer has a number or phone system through the processor | EU/EEA or with safeguards under GDPR Chapter V |
| OpenAI (OpenAI Ireland Ltd. and affiliates, including in the USA) | Real-time speech and language model, transcription, summary | For AI calls, unless the customer uses its own OpenAI account | USA possible; standard contractual clauses and/or EU-US Data Privacy Framework. European data residency not enabled. Under OpenAI's terms not used for training; abuse-monitoring logs up to 30 days under OpenAI's terms |
Not sub-processors: the search engine and SMS service the processor runs on its own servers. The customer's own systems and channels (booking system, webhook receivers, Telegram groups, email addresses), the customer's own OpenAI account and the customer's own telecom provider are recipients on the customer's instructions and not sub-processors of the processor.
Annex C — Security measures
- TLS for traffic to the control panel and API; the media stream to the language model runs over an encrypted connection.
- Logical separation of each customer's data, enforced in the data access layer.
- Audio of AI calls is not stored; audio files for transcription are deleted after transcription.
- Automatic deletion according to the customer's retention settings; erasure of one caller's data by phone number.
- Customers' own keys (e.g. OpenAI) are stored encrypted. Secrets are kept separate from the code with restricted permissions.
- Webhooks are signed; addresses entered by the customer are checked against internal networks, and redirects are not followed.
- Server access only with keys of named persons; firewall; continuous security updates.
- Outbound calls restricted to permitted destinations and monitoring of misuse.
- Backups are stored in the EU and deleted with the backup cycle.
- Logging of security events and of access to sensitive data; OpenAI's session tracing is switched off.