A multi-stakeholder environment, not a single technology stack
A franchised dealership is not a single organization from a data governance standpoint. The dealer operates independently, but its technology environment includes OEM-provided platforms, third-party CRM and finance and insurance (F&I) software, and a dealer management system (DMS) that typically serves as the system of record. AI agents deployed for sales follow-up, service scheduling, or F&I workflows do not operate inside one contained system. They make tool calls across the DMS, query or write to CRM records, and in some cases interact with OEM-owned portals that carry their own contractual data terms. Each of these boundaries represents a distinct trust domain with different owners, different data sensitivity levels, and in some cases different regulatory exposure. Governance frameworks designed for a single application do not map cleanly onto this structure, which is why dealership AI oversight needs to start from the assumption that agents will routinely cross organizational lines rather than stay within one.
The regulatory baseline: GLBA and the FTC Safeguards Rule
Dealerships that extend or arrange financing are treated as financial institutions under the Gramm-Leach-Bliley Act (GLBA), which places them under the FTC Safeguards Rule. This rule requires a written information security program that includes access controls limiting authorized users to only the customer information needed for their role, monitoring and logging of user activity, detection of unauthorized access, and oversight of service providers through contractual safeguard commitments. These obligations apply regardless of whether the "user" accessing customer information is a person or an automated agent acting on the institution's behalf. An AI agent that queries a customer's credit application data, income information, or deal terms is subject to the same access-limitation and monitoring expectations as a human employee. The GLBA Privacy Rule adds a separate constraint: limits on disclosing nonpublic personal information to third parties without proper notice. An AI agent that shares customer data across a CRM-to-OEM tool call needs to operate within these disclosure limits, not around them.
Where AI-specific risk management fits
NIST's AI Risk Management Framework (AI RMF 1.0) organizes AI governance around four functions: Govern, Map, Measure, and Manage. It calls for organizations to establish accountability structures and monitor AI system behavior across its lifecycle, and specifically recommends policies for AI system access, use, and third-party component integration where AI systems interact with multiple internal and external data sources. This maps directly onto the dealership environment, where a single AI agent workflow may touch DMS records, CRM fields, and OEM system calls in one interaction. The AI RMF is voluntary and does not itself create legal obligations, but it provides a structured way to organize the accountability and monitoring work that GLBA's binding requirements already demand. No automotive-specific AI regulation or OEM-published AI governance standard has been confirmed at this time, which means GLBA and the AI RMF currently function as the practical baseline for dealership AI governance planning.
Implementation steps for dealership AI governance
Dealerships and their governance leads should approach AI agent oversight as an extension of existing information security obligations, not a separate compliance track.