Compliance built into the record
Compliance comes down to the evidence you can produce months later. That is why consent is stored on the lead record, not in a separate system. These two pages explain how the platform works. One covers how consent is captured and passed to each buyer for TCPA. The other covers how data subject requests, retention, and transfers are handled for GDPR and CCPA. Neither page is legal advice. They describe what the platform does so your counsel can judge the rest.
Inside Lead Router
See where consent provider setup starts
- Connect the provider
- Your team supplies the required provider account and settings.
- Review the evidence
- The guides below explain the role of the product and the work your team still needs to do.
Two Frameworks
Where the evidence lives
One page covers consent and calling rules. The other covers personal-data rights.
TCPA Architecture
Consent capture at the source, submitted consent evidence and native certificate workflows, DNC integration, and an audit log entry on every lead.
GDPR & CCPA
A data-subject request workflow with a 30-day SLA, consent tracking, data minimization, standard contractual clauses for transfers, and a DPA on request.
Evidence By Default
Keep the consent next to the lead
Consent metadata, DNC checks, and an audit log entry travel with the lead record, so you can answer a dispute months later with a single lookup.
Every feature is part of the plan. Usage is billed in credits.