> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dairo.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance

> Disclose the AI, get consent where required, and handle recording and caller id correctly before calling real people.

Dairo Phone puts an AI on a live line with a real person, and that comes with legal duties: disclosure, consent, recording, caller id. This page covers the rules most users hit. It is orientation, not legal advice — your own counsel has the final word for your use case.

## Disclose that it's an AI

The EU AI Act (Article 50) requires that people interacting with an AI system are told so, clearly, no later than the first interaction. The natural place is the `greeting`, backed up in `instructions`:

```json theme={null}
{
  "greeting": "Hallo, hier spricht der digitale Assistent von Acme.",
  "instructions": "You are Acme's AI assistant. You have already introduced yourself as an AI in the greeting; if the caller asks, confirm plainly that you are an AI assistant. Then: …"
}
```

Make the disclosure part of your standard call template rather than a per-call decision — a call that opens with "this is Acme's AI assistant" satisfies the duty.

## Advertising calls need consent

In Germany, §7 UWG treats advertising calls to consumers without their prior express consent as unacceptable harassment, and most jurisdictions have similar telemarketing rules. If a call promotes a product or service to a consumer, you need that consent on record before you dial — a contact list is not consent.

Dairo Phone is built for calls people expect:

* **Transactional and expected calls** — delivery updates, appointment reminders and confirmations, fraud alerts, on-call escalations.
* **Calls into an existing relationship** — your customer, your colleague, your vendor, about the matter that connects you.
* **Calls the recipient asked for** — "call me back when it's fixed."

## Call recording

Recording is on by default (`record: true`). Many jurisdictions — Germany among them, and two-party-consent US states such as California — require all parties to consent before a call is recorded. Handle it one of two ways:

* **Disclose it.** Add a recording notice to the `greeting` — "this call is recorded for quality" — alongside the AI disclosure.
* **Turn it off.** Set `record: false` when you [place the call](/phone/making-calls). The transcript is unaffected either way.

<Warning>
  Recording someone without required consent can be a criminal offense (§201 StGB in Germany), not only a civil matter. If your calls reach two-party-consent jurisdictions and your greeting doesn't disclose recording, set `record: false`.
</Warning>

## Caller id in Germany

Since December 2022, German carriers suppress a German mobile caller id (+49 15x/16x/17x) that arrives from a foreign network — an anti-spoofing rule in §120 TKG. If German recipients see "unknown number", they don't answer.

The fix: use a registered German local or national number as the display number for German recipients. Buy one on [Phone numbers](/phone/phone-numbers) — German numbers settle as `pending` until their regulatory requirements are met, then activate — and use it as the `from` on calls into Germany. As always, `from` must be a number your account owns with status `active`; Dairo rejects anything else with `400`, which is also what keeps caller-id spoofing off the platform entirely.

## Before your first production call

* Put the AI disclosure in your greeting template — and a recording notice, if you keep `record: true`.
* Check the call's legal basis: transactional, existing relationship, or requested. If it's advertising to a consumer, confirm you hold prior express consent.
* Pick a `from` your recipients' carriers will display — for Germany, a German local or national number.
* Set `maxDurationSeconds` to the longest call that still makes sense, so cost and conversation stay bounded.