Security and compliance
We're touching customer data. That comes with rules, and we build to them.
Compliance isn't a step at the end of implementation. It's part of the design, and it occasionally means telling you not to deploy something that would otherwise work.
FTC Safeguards Rule
Most dealers that finance or lease fall under the Safeguards Rule, including obligations around service providers who touch customer information. We work inside your program, not around it. A written data handling agreement is signed before we receive any dealership data. Before analysis, customer-identifying fields are removed or replaced with pseudonymous identifiers, and free-text notes are scrubbed for sensitive information. If the anonymization engine can't run, processing stops rather than continuing without it.
TCPA and AI voice
The FCC has confirmed that TCPA restrictions on artificial and prerecorded voices cover AI-generated voices in covered outbound calls, with consent requirements attached. We will not stand up an AI calling or texting program simply because the technology works. Consent handling is part of the build.
No real customer data in development
Prototypes and test environments run on synthetic data. No SSNs, no credit applications, no financial information, ever, in anything that isn't production.
Humans stay in the loop
Every workflow we design has defined approval points and escalation rules. Your people decide where the system is allowed to act on its own and where it has to stop and ask.
Questions about your specific program
Bring your compliance officer to the call.
If your store has its own Safeguards Rule program or vendor-risk process, tell us up front — it shapes the diagnostic from day one.