Quantum Connect AI | AI Revenue Operating Layer

Program overview

Quantum Connect AI, LLC operates an AI revenue layer for automotive retail covering marketplace automation, AI lead response through our assistant Hannah, managed on-premises appliances, and dealer-approved CRM or inventory integrations. This page summarizes the security program that governs those services.

The program is aligned to FTC Safeguards Rule and the NIST Cybersecurity Framework. Alignment is an ongoing operating program, not a certificate. This summary describes our controls and design commitments. It does not replace a dealership's own security, privacy, legal, or vendor risk review.

Program version 0.1, effective August 16, 2026.
Reviewed at least annually and after material changes. Next scheduled review August 16, 2027.
Owned by the President, Quantum Connect AI, LLC, who coordinates governance, risk assessment, and incident response.

Data we process

Data is classified before it is processed, and each class carries its own handling rules.

Class	Examples	How it is used
Public	Public vehicle details and vehicle photos.	Marketplace posting, vehicle information, and lead-response context.
Confidential	Dealer operational data, inventory rules, and pricing rules.	Approved posting, business rules, and rooftop-specific workflows.
Restricted	Lead contact information, marketplace and messaging content, CRM activity, dealer user records, device information, and access tokens.	Lead response, approved CRM activity, support, access management, and audit records.
Highly Restricted	Social security numbers, credit applications, payment card data, banking information, and driver license images.	Not collected or processed through marketplace or AI messaging workflows. These requests are routed to the dealership’s approved secure workflow or a trained employee.

Highly restricted finance and identity data is out of scope by design. If a shopper raises a finance, payment, identity, credit application, or document request in a messaging channel, the workflow routes that person to the dealership's approved secure process or a trained employee.

Security model

Dealer isolation

Each dealer group and rooftop is treated as a distinct tenant. Dealer data, user access, device identity, credentials, workflows, and audit records are designed to stay inside the correct dealer boundary. One rooftop deployment must not create a path to another dealership’s network or data.

Identity and access

Unique named accounts are required and shared administrative accounts are prohibited. Role-based access control and least privilege limit personnel, integrations, and devices to the access needed for approved work. Multifactor authentication is required for workforce and administrative accounts, privileged access is reviewed quarterly, and access is removed the same day it is no longer authorized.

Encryption and secrets

The program requires encryption in transit using TLS 1.2 or higher, preferably TLS 1.3, and encryption at rest for applicable databases, storage, backups, device storage, and sensitive logs. API keys, certificates, and service credentials are held in an approved secrets manager and are never embedded in source code, device images, browser profiles, logs, screenshots, or support tickets.

Secure delivery

Protected source control, peer review, separated development, testing, staging, and production environments, security scanning, release approval, rollback planning, and staged appliance updates.

Logging and monitoring

Device, application, identity, administrative, integration, and AI activity is logged. Monitoring covers suspicious authentication, unusual device or network behavior, configuration changes, privilege changes, token activity, and AI actions.

Incident response and recovery

The incident program covers detection, containment, investigation, recovery, evidence preservation, dealer communications, credential revocation, appliance isolation, and integration disablement, with tabletop exercises at least annually. Specific notification timelines are set in the dealer agreement.

Managed appliance

Where a Quantum appliance, the Qbox, is deployed at a rooftop, it is a managed on-premises device. It is not a general-purpose computer and not a pathway into dealership systems. Full terms are on the Qbox appliance terms page.

Control baseline

One unique certificate, cryptographic key, or equivalent identity per appliance, issued after authenticated enrollment.
Dealer-specific configuration and credentials that are never embedded in a shared device image or copied between appliances.
Outbound-only encrypted connectivity to approved Quantum services, with default-deny access to dealer internal networks.
A supported, maintained operating system image carrying only the software required for approved workflows.
Disabled password-based SSH and root login, with administrative access only through an approved identity-aware path.
Asset inventory covering serial number, MAC address, dealer group and rooftop, location, installer, deployment date, support owner, connectivity type, and device status.
Patch management, health checks, configuration drift detection, tamper-evident enclosure, and telemetry to protected logging.
Quarterly review of fleet inventory and privileged device access.

Prohibited on the appliance

Inbound internet access to the appliance.
Public SSH, RDP, VNC, or web-based management interfaces.
Port forwarding, public IP exposure, or direct inbound remote control.
Network scanning, port scanning, or broad probing of dealer networks.
Routing, bridging, Wi-Fi access point operation, DHCP service, or DNS service.
Unapproved access to dealer internal subnets, DMS, finance systems, printers, file shares, cameras, or point of sale systems.
Use of the appliance as a shared gateway, remote access relay, or proxy for dealership personnel.

AI governance

Hannah operates inside dealer-approved policy. Automated actions are limited to approved workflows, and exceptions escalate to a person.

Dealer-specific knowledge, inventory context, policies, and tool access.
Approved response topics, messaging rules, and escalation instructions.
Human approval for higher-risk actions, unusual messaging, pricing changes, bulk messages, data exports, and commitments outside policy.
Audit records for input context, tool calls, responses, CRM activity, policy blocks, escalations, and human overrides.
Testing for prompt injection, unauthorized tool use, cross-tenant exposure, unsafe outputs, and data leakage.

The model does not decide its own permissions. Authority is evaluated before an action runs, and every consequential action is written to an append-only event history.

Retention and deletion

Data is kept only for an approved business, security, contractual, legal, or recovery purpose. Retention rules by record category are below. Exact periods are set per dealership in the applicable agreement rather than published as a blanket schedule.

Record category	Retention rule
Public vehicle listing data	Retained only while needed for authorized listing, audit, operational, or contractual purposes.
Dealer configuration and pricing rules	Retained while active and for the approved post-change, audit, or contractual period.
Lead contact information and messages	Retained only for the authorized dealer workflow, contractual requirement, or security investigation.
CRM activity and integration records	Retained per the dealer agreement, the authorized workflow, and the system schedule.
AI inputs, outputs, and audit records	Retained only as needed for authorized service operation, quality review, and security investigation.
Identity and access records	Retained for account lifecycle, access review, audit, and incident investigation.
Device inventory and health records	Retained while the device is active and through the approved post-decommissioning audit period.
Security logs	Retained for monitoring, investigation, audit, legal, and contractual needs.
Backups	Retained under the approved backup schedule and recovery requirements, then aged out on the normal cycle.

On offboarding we revoke accounts, integration tokens, and device certificates, then delete or return dealer data under the agreement. Deletion preserves the integrity of other dealer tenants, and backups age out on their normal cycle. See the Data Processing Addendum for the contractual commitments.

Compliance position

We do not claim to be FTC certified, SOC 2 certified or compliant, ISO certified, PCI compliant, or independently penetration tested. Our current position on each program is stated plainly below.

Program	Current position
FTC Safeguards Rule and GLBA alignment	Operating compliance program in progress. This is not an FTC certification.
SOC 2 Type II	Planned. SOC 2 Type II is an independent attestation report, not a certification. No report exists today.
ISO/IEC 27001	Planned certification target once the core information security management system is operating.
ISO/IEC 27701	Planned privacy extension for evaluation after or alongside ISO/IEC 27001.
PCI DSS	Designed to be out of scope because our workflows do not handle payment card data. Scope is reassessed if that ever changes.
Independent penetration test	No published third-party test report.
State privacy requirements	Applicability is determined with counsel for each applicable state framework.

Shared responsibility

Security depends on both parties. The split below is confirmed during onboarding.

Quantum is responsible for

Approved service design, tenant separation, and dealer-scoped access model.
Managed appliance baseline, asset tracking, enrollment, patching, and remote credential revocation.
Secrets management for Quantum-held credentials and integration tokens.
Logging, monitoring, incident response, and dealer notification for confirmed incidents involving dealer data.
Vendor and subprocessor oversight for material providers that handle dealer data.

The dealership is responsible for

Its own network, network segmentation, and physical access control at the facility.
Marketplace account ownership, CRM permissions, and user administration.
Approval of appliance placement, connectivity model, and integration scope.
A trained employee or approved secure workflow for finance, payment, identity, and document requests.
Prompt reporting of suspected incidents, lost appliances, compromised credentials, or unauthorized activity.

Before deployment we agree with the dealership on the connectivity model, appliance location, approved integrations, access scope, incident contacts, and AI escalation path.

Evidence and review

We organize security materials for dealer due diligence and answer vendor security questionnaires from verified records. Distribution depends on sensitivity.

Public: Executive security overview, high-level architecture, compliance roadmap, and privacy summary.
Under NDA: Detailed data flows, appliance and network requirements, policy summaries, incident response summary, and subprocessor information.
Restricted review: Verified audit reports, full penetration test reports, vulnerability remediation evidence, and sensitive architecture documentation, once they exist.

Routine evidence never includes credentials, API keys, raw logs, IP addresses, unredacted testing findings, or another dealership's information.

Contact

For a security review, a completed questionnaire, or the current subprocessor information, contact legal@quantumconnectai.com. To report a suspected vulnerability, follow the responsible disclosure process.

How Quantum protects dealer data.