Skip to content
CollectionsQA

Compliance

The gate comes before the recording

Most monitoring products let you switch everything on and leave the legal basis to you. We put the gate in the software, because the moment a floor most needs a constraint is the moment before it starts recording.

The attestation

Recording voices and storing what people type are treated as distinct legal categories — by two-party consent statutes, under GDPR, and by works-council regimes. So they sit behind an attestation in the console. An administrator states the lawful basis and confirms staff were told, and the record keeps who signed it, when, and which policy version they acknowledged.

Until that is signed, those endpoints do not collect. Not collect-and-hide. Do not collect.

Revoking is a single write that switches it all off across every device, without deleting the record of who enabled it. That asymmetry is deliberate: turning monitoring off should be instant, and the history of it being on should be permanent.

Off by default

A device collects nothing until an administrator switches that specific capability on for that specific machine.

Never on an update

A machine cannot begin monitoring because it took a new version. Absent configuration means remote-access only, always.

Per-listen audit

Every access to a stored recording is logged against the person who did it.

Stated retention

Content is kept for a defined window, not indefinitely. Retention is a promise to the people recorded.

A signed policy document on a desk beside a pen and reading glasses

One-party and all-party consent

Federal law permits recording with one party's consent. Roughly fifteen states require every party to consent, and a collections floor calling across state lines will routinely place calls into them.

The common operational answer is a disclosure at the top of every call regardless of where it lands, which is also what most collections scripts already carry for other reasons. Whether that is sufficient for your program is a question for your counsel, not for a software vendor.

What we can tell you is which states impose the stricter rule, so the conversation with counsel starts from the right map.

See the state-by-state map

This is not legal advice

Nothing on this site is legal advice, and we are not your lawyers. Call-recording and employee-monitoring obligations turn on facts we do not know about your program. Confirm your own position with counsel before you record anyone — and tell your team first, in writing. The attestation records that you did; it does not do it for you.