Privacy policy for LynBro AI-telefon
Version 2026-10-20. English translation; the Danish text prevails.
LynBro AI-telefon (LynBro AI phone) is a telephone service in which an AI assistant answers calls for businesses ("our customers"). This policy explains what personal data we process when a business uses the service and when you call a business that uses it. We never sell personal data.
1. Who is responsible
LynBro ApS, CVR no. 46321499, Rødovre Parkvej 276, 2610 Rødovre, Denmark, email hello@lynbro.dk.
We have two roles:
| If you are … | the controller is … | and LynBro ApS is … |
|---|---|---|
| a customer or user of LynBro AI-telefon (business, staff member with a login, contact person, the responsible person when a number is ordered) or a visitor to our website | LynBro ApS | the controller (section 2) |
| a person who calls, or is called by, one of our customers | the business you call | the business's processor under a data processing agreement (section 3) |
If you called a business, please contact that business first to exercise your rights. If you write to us, we forward your request to the business without undue delay.
2. Data about our customers and users (LynBro ApS is the controller)
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Creating an account and checking that the sign-up is genuine | Business name and CVR no., the contact person's name, work email and mobile number, password (stored as a hash), chosen plan, accepted versions of the terms, IP address, browser and time; information about the business from the Danish CVR register | Art. 6(1)(b) (contract) and (f) (preventing fake sign-ups and misuse) | Sign-ups that are not completed are deleted after 30 days. Otherwise as the account |
| Account, users and delivery of the service | Business name, CVR no. and address; users' name, email, phone, role and sign-in data; settings | Art. 6(1)(b) and (f) (managing the customer's users) | While the account is active and 30 days after it ends, so the customer can receive its data; then deleted, except as set out below |
| Ordering a Danish phone number (identity check, "KYC") | The responsible person's name, date of birth, nationality, phone, email, home address, type, number, issuer and dates of the ID document and a scan of it. We never ask for a CPR number | Art. 6(1)(b) (the number contract), (f) (meeting the telecom operator's requirements and preventing misuse of numbers) and (c) to the extent legislation requires identification | Scans are deleted 30 days after the number is activated or the order is rejected or cancelled. After that we keep only a minimal record (document type, the last characters of its number, who checked it and when) while the number is active and 12 months after |
| One-time codes by SMS at sign-up and when ordering a number | Phone number, time, result | Art. 6(1)(b) and (f) (making sure the number belongs to the person) | The code is valid for a short time; the log as a security log |
| Payment, invoicing and bookkeeping | Plan, invoices, payments, usage (minutes, calls, numbers). Card data is handled by our payment provider, not by us | Art. 6(1)(b) and (c), Danish Bookkeeping Act | 5 years from the end of the financial year concerned |
| Record of acceptance of the terms and the DPA | User, version, time, IP address, browser | Art. 6(1)(f) (evidence of the contract) | While the contract runs and 3 years after (limitation period) |
| Support and enquiries | Name, contact details, what you write | Art. 6(1)(b) and (f) | 12 months after the last contact |
| Service messages and news | Email, name | Service messages: art. 6(1)(b). News about similar LynBro services to customers: Danish Marketing Practices Act s. 10(2) and art. 6(1)(f); otherwise only with consent | Service messages as the account. News until you unsubscribe, which you can always do |
| Operation, security and prevention of misuse and call fraud | IP address, browser, time, requests, sign-in events, call patterns, destinations, security events | Art. 6(1)(f) and art. 32 | Server and request logs up to 90 days; sign-in events and misuse signals up to 12 months; audit log of administrative actions and access to identity data up to 3 years. Longer if the data forms part of a specific case, until it is closed |
| Statistics and development of the service | Use of features, number and duration of calls, errors, response times | Art. 6(1)(f) | Up to 24 months; then only as aggregated figures without personal data |
| Legal claims | The data needed for the case | Art. 6(1)(f) | Until the case is closed and the limitation period has expired |
Data for a number order is sent to the telecom operator (section 5), which must check the subscriber itself and is an independent controller for that. Access to identity data on our side is logged, and scans are stored encrypted outside the database.
Cookies. Our website and control panel use only cookies that are necessary for the service to work (sign-in, security, protection against bots and language choice). We do not use statistics or marketing cookies. If we start doing so, we will ask for consent first.
3. Data about people who call (LynBro ApS is the processor)
When you call a business that uses LynBro AI-telefon, an AI assistant answers. You are always told so at the start of the call (EU AI Act, art. 50). On behalf of the business we process:
- your phone number (caller ID), time, duration and language;
- what you say. The audio is sent to the language model while the call takes place and is not stored by us;
- a transcript and a short summary of the call, and its topics;
- what the call leads to: a booking, a change or cancellation, a message or a callback request;
- if the business already has you as a customer: your name and previous appointments, so the assistant can help you.
The legal basis is the business's, typically art. 6(1)(b) (when you book or have an appointment) or (f) (answering your enquiry). The assistant makes no decisions with legal effect for you (art. 22); if you want to speak to a person, you can ask to be called back. We do not use voice recognition to identify you (biometrics) and do not analyse emotions.
The business decides how long transcripts and the call log are kept (section 7). If you ask for erasure, the business can delete the transcript, summary and customer record; the call log is anonymised so it is used only for billing.
If the business itself has switched on recording or transcription of other calls (e.g. voicemail or calls with its staff), it is the business that must inform you about it.
4. OpenAI: what is sent, where, for how long, and training
The AI assistant uses a speech and language model from OpenAI, which is our sub-processor.
| What is sent | The audio of the call in both directions while it takes place. The assistant's instructions and the business's own information (e.g. prices and opening hours). The data needed for the answer (e.g. free times, your name if the business knows you, a booking). If the business has switched it on: audio files of voicemail messages and of calls with the business's staff, for transcription. We delete the audio files after transcription |
|---|---|
| Where | OpenAI's platform. Data may be processed in the USA. OpenAI's European data residency is currently not enabled for the service |
| Transfer | Transfers to the USA rest on the European Commission's standard contractual clauses and/or another valid basis under GDPR Chapter V, e.g. the EU-US Data Privacy Framework for certified companies |
| For how long | Under OpenAI's terms (October 2026), real-time calls are not stored as application data, but the content may be kept for up to 30 days for abuse monitoring and then deleted, unless the law requires otherwise |
| Training | Under OpenAI's terms, data sent through OpenAI's API is not used to train OpenAI's models unless the customer opts in. We have not |
| Own OpenAI account | If a business uses its own OpenAI account, its own agreement with OpenAI applies, and we send the call there on the business's instructions |
If we obtain European data residency or shorter retention at OpenAI, we may switch it on and will then update this policy.
5. Recipients
We use these suppliers to run the service. The current list of sub-processors for call data is in the data processing agreement, Annex B (pbx-app.lynbro.dk/legal/dpa).
| Recipient | What | Where |
|---|---|---|
| netcup GmbH | Servers for telephony and the control panel, database, backups | Germany (EU) |
| Contabo GmbH | Servers for our own mail server and our CRM and invoicing system | Germany (EU) |
| Zadarma (telecom operator) | Phone numbers, call transport, SMS. For number orders an independent controller for checking the subscriber | EU/EEA or with safeguards under GDPR Chapter V |
| OpenAI | Speech and language model, transcription, summary (section 4) | USA possible, see section 4 |
| Stripe | Payment by card and other payment methods. Stripe is an independent controller for its own payment checks and fraud prevention | EU, USA possible (standard contractual clauses/Data Privacy Framework) |
| Cloudflare | Protection of the sign-up form against bots, when switched on | EU/USA (standard contractual clauses/Data Privacy Framework) |
Searches in the business's knowledge base run in our own installation on our servers. SMS is sent through LynBro ApS' own SMS service via the telecom operator.
On the business's instructions we also send data to the business's own systems and channels, e.g. its booking system, a webhook address or a Telegram group the business has chosen. Otherwise we disclose data only where the law requires it, to the telecom operator and the authorities when fraud is suspected, or where necessary to establish, exercise or defend legal claims.
6. Transfers outside the EU/EEA
Our servers are in the EU. Data may be processed outside the EU/EEA, mainly in the USA, by OpenAI (section 4) and by the suppliers marked in section 5. The transfers rest on the European Commission's standard contractual clauses and/or the EU-US Data Privacy Framework decision (art. 45-46). You can get a copy of the safeguards by writing to us.
7. Retention — overview
| Data | Retention | Who decides |
|---|---|---|
| Audio of calls with the AI assistant | Not stored by us | — |
| Audio files for transcription (voicemail, calls with staff, if switched on) | Deleted after transcription | The business switches it on |
| Transcript and summary | 180 days by default; the business may choose another period | The business |
| Call log (number, time, duration, status, price) | 730 days by default; the business may choose another period | The business |
| Call log after erasure on request | Anonymised: number and content removed, only billing data remains | — |
| OpenAI's abuse-monitoring logs | Up to 30 days under OpenAI's terms | OpenAI |
| Sign-ups not completed | 30 days | LynBro ApS |
| Customer account and settings | Lifetime of the account + 30 days | LynBro ApS |
| ID scans (KYC) | 30 days after activation, rejection or cancellation | LynBro ApS |
| Minimal KYC record | Lifetime of the number + 12 months | LynBro ApS |
| Server and request logs | Up to 90 days | LynBro ApS |
| Sign-in events and misuse signals | Up to 12 months | LynBro ApS |
| Audit log (administrative actions, access to KYC data) | Up to 3 years | LynBro ApS |
| Invoices and bookkeeping records | 5 years from the end of the financial year | Law |
| Acceptance of the terms and the DPA | Term of the contract + 3 years | LynBro ApS |
| Backups | Overwritten and deleted continuously with the backup cycle | LynBro ApS |
8. Your rights
You have the right of access (art. 15), rectification (art. 16), erasure (art. 17), restriction (art. 18) and data portability (art. 20). You may object to processing based on legitimate interest and always to direct marketing (art. 21). You can withdraw consent at any time without affecting processing before the withdrawal (art. 7(3)). There may be limits, e.g. we must keep data required by the Bookkeeping Act or needed for a legal claim (art. 17(3)). We reply within one month and may ask you to confirm your identity. If you called a business, please contact the business (section 1).
9. Complaints
You can complain to the Danish Data Protection Agency (Datatilsynet), Carl Jacobsens Vej 35, 2500 Valby, Denmark, dt@datatilsynet.dk, www.datatilsynet.dk. We would like to hear from you first so we can put things right.
10. Security
Encrypted connections (TLS) for traffic to the control panel, the API and the language model. Each customer's data is kept separate. ID scans are encrypted with a separate key per file and stored outside the database. Customers' own API keys are stored encrypted. Server access is by keys only. We keep systems updated, take backups and log access to sensitive data. No method is 100 % secure. If a personal data breach occurs, we handle it under art. 33-34.
11. Changes
We may update this policy, e.g. when we start using new suppliers or features. The current version and date are always on this page. For material changes we notify customers by email or in the service.