Home / Compliance
Compliance
The mandate, turned into an API call.
Disclosure and consent rules for AI voice aren't coming — they're in force. NoAICalls maps each control to the obligation it satisfies, and gives you the evidence to prove it.
The forcing function
Disclosure is already law in the places that matter.
Automated agents interacting with people must disclose that they are bots. The first US bot-transparency statute.
The FCC confirmed AI-generated voices count as "artificial" under the Telephone Consumer Protection Act — prior consent required for calls that use them.
Utah and a growing set of states enacted AI-disclosure requirements for consumer-facing automated communication.
The duty to tell people they are interacting with an AI system applies from 2 August 2026. Penalty tier for breaches: up to €15M or 3% of worldwide annual turnover.
Note: under the May 2026 Digital Omnibus provisional agreement, only the Article 50(2) machine-readable marking obligation for generative systems already on the market received a grace period to 2 December 2026. The interaction-disclosure duty NoAICalls addresses proceeds on 2 August 2026. Regulations evolve — confirm current obligations with counsel.
Control mapping
Each obligation, and the control that meets it.
This mapping is provided for orientation and is not legal advice. Applicability depends on your jurisdiction, use case, and role (provider vs deployer). NoAICalls supports your compliance program; it doesn't replace counsel.
Export on demand.
Signed, timestamped records for any session — disclosures, consents, policy checks — ready for an auditor or a regulator.
Mapped, not marketed.
Controls tied to TCPA, FCC guidance, and EU AI Act Article 50, with the mapping maintained as rules evolve.
Where your data lives.
Region pinning for EU and US deployments, with subprocessor transparency under enterprise agreements.