Compliance Framework

Compliance by architecture, not by memo

FDCPA, Regulation F, and HIPAA obligations are enforced by the platform itself — controls execute before a contact happens, and every event lands in a tamper-evident record.

Regulatory coverage

Three frameworks, one control plane

FDCPA

Fair Debt Collection Practices Act

  • Validation notices auto-issued within 5 days of first contact.
  • Prohibited-practice guardrails built into scripts and dialer.
  • Dispute rights honored: activity pauses during investigation.
  • Documented call scripts with mandatory recording.
REG F

Regulation F (12 CFR 1006)

  • 7-in-7 call frequency cap tracked per consumer, per debt.
  • Contact windows respect consumer time zone automatically.
  • Electronic opt-outs honored immediately, all channels.
  • Limited-content message rules applied to voicemails.
HIPAA

HIPAA (healthcare clients)

  • BAA executed before any PHI is transmitted.
  • PHI limited to minimum necessary for collection.
  • AES-256 at rest, TLS 1.2+ in transit, row-level isolation.
  • Breach notification protocols meet or exceed requirements.
Platform-enforced controls

Controls that execute, not policies that hope

Control
How it's enforced
Mode
Call frequency (7-in-7)Dialer checks the per-consumer counter at dial time; blocked attempts never ring.BLOCKING
Contact time windowsConsumer time zone + state rules resolve the legal window; out-of-window contacts are queued, not sent.BLOCKING
Cease & desistA C&D on any channel halts all channels and future attempts for that consumer instantly.BLOCKING
Validation noticesGenerated and dispatched automatically within the statutory 5-day window.AUTOMATED
Dispute quarantineDisputed accounts leave all work queues until resolution is documented.AUTOMATED
Call recording & QA100% of calls recorded; auto-flagging on tone and disclosure language for supervisor review.MONITORED
Compliance auditsRegular internal audits of scripts, letters, and dispositions with documented findings.MONITORED
Tamper-evident audit trail

Every event, hash-chained and exportable

Communications, payments, disputes, and status changes are written to an append-only log where each record includes the hash of the one before it. Alteration breaks the chain — and shows. Export the full history for any account, any regulator, any time.

09:14:22PAYMENT $237.00 · ACH · AR-20419a3f1…9c
09:02:57CALL RECORDED · 6:14 · AR-1987777b0…e2
08:51:10DISPUTE ACK SENT · AR-20461c49a…51
08:45:33VALIDATION NOTICE MAILED · AR-205441d8e…07
08:30:01C&D APPLIED · ALL CHANNELS · AR-20102f52c…b8
APPEND-ONLY · SHA-256 CHAIN · EXPORT: CSV / JSON / PDF
Trust, documented

Put your compliance team's mind at ease