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

# Compliance

# Compliance Requirements

Operating a voice AI system requires strict adherence to local and international telecommunications laws. Movoice AI provides the tools to help you stay compliant, but it is your responsibility to ensure your use case follows the law.

## 🇺🇸 TCPA (United States)

If you are calling or messaging users in the US, you must comply with the Telephone Consumer Protection Act.

* **Opt-in**: You must have "prior express written consent" before calling users for marketing purposes.
* **Do Not Call (DNC)**: You must respect the national DNC registry and maintain your own internal DNC list.
* **Identification**: Your agent MUST identify itself and your business at the start of the call.

## 🇮🇳 TRAI Guidelines (India)

Commercial calls in India are regulated by the Telecom Regulatory Authority of India.

* **UCC Regulation**: Unsolicited Commercial Communications are strictly prohibited to numbers registered on the DND (Do Not Disturb) list.
* **Header/Sender ID**: You must use registered headers for official business communication.
* **Consent Templates**: Scrutiny over the templates used for communication.

## 🇪🇺 GDPR (Europe)

* **Right to be Forgotten**: You must be able to delete a user's call logs and personal data upon request.
* **Recording Consent**: Always inform the user if the call is being recorded for "quality and training purposes."

## Compliant Prompting

We recommend adding a compliance section to every system prompt:

* *"Start every call by saying: 'Hello, this is an automated call from \[Business Name].'"*
* *"If the user asks to be removed from the list, say 'Certainly' and use the `end_call` tool immediately. Tag the call as DNC."*