FDCPA compliance for debt collection AI —
enforced on every LLM call.
Debt collection chatbots make false threats, invent fee settlements, and skip Mini-Miranda disclosures. Peekr enforces FDCPA rules in-process before responses reach consumers — no proxy, no architecture change.
Why FDCPA on LLM outputs is hard
False threats slip through prompts
You instruct the LLM to be firm. It responds with "failure to pay will result in your arrest." The FDCPA prohibits threats a collector cannot legally make or does not intend to take — and prompt instructions won't reliably stop it.
LLMs invent settlements
"I can waive the late fee if you pay today." The LLM hallucinated an offer your company never authorised. That's a false representation under Section 807 of the FDCPA.
Mini-Miranda is easy to miss
Every initial debt communication must include the validation notice. An LLM that skips it creates per-contact FDCPA exposure — up to $1,000 per violation plus attorney fees.
What Peekr enforces
The FDCPA pack runs as a guardrail inside your agent process. Every LLM response is checked before it reaches the consumer. Violations are blocked (or warned) and stored in an immutable audit log.
| Category | What it catches | Action |
|---|---|---|
| False legal threats | "We will sue you", "you will be arrested", "legal action is imminent" | Block — threats must be intended and lawful |
| Illegal fee promise | "We can waive the fee", "we'll forgive the balance" without authority | Block — unauthorised settlement offers |
| Missing Mini-Miranda | First contact message without debt validation disclosure | Warn — add required disclosure |
| Harassment language | Profanity, threats of violence, repeated automated contact references | Block — Section 806 prohibition |
2 lines to enforce FDCPA
Add compliance=["FDCPA"] to your existing peekr.instrument() call. Rules are fetched from Peekr Cloud and enforced locally — no data leaves your process.
import peekr
peekr.instrument(
exporter=peekr.HTTPExporter(
endpoint="https://peekr.starkspherelabs.com",
api_key="pk_live_...",
),
compliance=["FDCPA"], # ← add this line
)
# Every LLM call is now FDCPA-checked.
# False threats are blocked. Mini-Miranda gaps are flagged.
# Violations go into an audit log your compliance officer can read.Works with OpenAI, Anthropic, Google Gemini, Amazon Bedrock, LangChain, and CrewAI — auto-instrumented, no code changes per call.
Audit-ready violation logs
Every violation is stored as a tamper-evident record in Peekr Cloud: which rule fired, which text triggered it, which model produced it, and when. Your compliance officer can filter by regulation, export to PDF, and hand it directly to an auditor or regulator.
Per-violation detail
Pack, rule name, matched text, span ID, timestamp, tenant.
Team access
Compliance officer gets read-only dashboard access, no code required.
7-day rolling window
Default retention. Enterprise gets configurable retention + export.
Immutable records
Violations can't be deleted by the app — only by explicit data retention policy.
Common questions
Does using Peekr make me FDCPA-compliant?
Peekr enforces the output patterns — false threat detection, required disclosures, prohibited language — but compliance also depends on your collector licensing, data handling, and call scripts. We're a technical control, not a legal certification. Consult FDCPA counsel for your specific program.
What is the Mini-Miranda disclosure?
Under 15 U.S.C. § 1692e(11), every initial communication must disclose that it is from a debt collector attempting to collect a debt and that any information obtained will be used for that purpose. Oral communications must include a variation of this notice. Peekr flags first-contact LLM responses that omit it.
Can debt collection AI legally text or message consumers?
Yes, subject to restrictions. The CFPB's Regulation F (effective 2021) permits electronic communications including texts and messages, but requires an opt-out mechanism, limits on frequency, and compliance with the E-SIGN Act. Peekr checks the output content — you still need to manage consent and channel rules at the infrastructure layer.
Does FDCPA apply to AI chatbots?
Yes. The FDCPA applies to debt collectors regardless of the communication method. An AI chatbot operated by or on behalf of a debt collector is subject to the same prohibitions on false representations, harassment, and unfair practices as a human agent. The CFPB has signalled it will hold covered entities responsible for AI outputs.
What if the AI makes a false threat?
If not caught, a false threat (e.g. "you will be arrested") is a per-communication FDCPA violation — up to $1,000 in statutory damages per consumer, plus actual damages and attorney fees. In a class action, total liability is capped at the lesser of $500,000 or 1% of net worth. Peekr blocks the output before it reaches the consumer.
Start enforcing FDCPA on your debt collection AI today
Free tier includes the FDCPA pack — 10,000 spans/month, no credit card.
Need FINRA, HIPAA, GDPR, or UAE compliance? See all 10+ compliance packs →