Security Overview
Security and compliance, stated plainly.
BridleOS is built for a regulated, high-trust business. This page explains how customer data is handled, how the AI is constrained, and exactly where our compliance work stands today.
Status labels on this site are literal. “Built in” means the control is part of the product design today. “In progress” means the work is under way and not finished.
Six controls, one standard
Privacy-law aligned
Designed to support PIPEDA and provincial privacy obligations for Canadian dealers, and the FTC Safeguards Rule for US rooftops. Customer data is encrypted in transit and at rest.
Built inSOC 2 Type II
Controls are being implemented against the SOC 2 Trust Services Criteria. Audit report available to customers on completion.
In progressCanadian data residency
Customer and inventory data stored in Canadian cloud regions by default. No model training on your dealership's data.
Built inHuman-in-the-loop by default
Any message that touches price, financing, trade value or a legal commitment is drafted first and released only on GM or manager approval.
Built inZero-hallucination grounding
Vehicle, pricing and policy answers are restricted to your own records. If the answer isn't in the data, the AI says it doesn't know and escalates.
Built inFull audit trail
Every inbound message, AI draft, approval, edit and send is logged with a timestamp and actor. Exportable for compliance review.
Built in
What the AI will never do
- Quote a price, payment or APR outside GM-approved rules
- Describe a vehicle that isn't in your inventory table
- Make a promise about financing approval
- Contact a customer who has opted out
- Delete or alter a logged conversation
Proprietary IP & Security
Your data, your rules, your record.
Proprietary Data Isolation
Your dealership's inventory data, customer leads, and margin rules are isolated within private enterprise containers and never used to train public LLM models.
Immutable Human-in-the-Loop Audit Logs
Every autonomous action generates a time-stamped, manager-auditable trail. Entries are append-only and chained, so an edited or deleted record shows up on review.
Deterministic compliance guardrails: rules are evaluated before anything is sent, not left to model judgement. Designed to support CASL, PIPEDA and the FTC Safeguards Rule. SOC 2 controls are in progress.
Customer data stays in Canada
Customer and inventory data is stored in Canadian cloud regions by default and encrypted in transit and at rest.
Your dealership's data is never used to train models. It is used to answer your customers, inside the rules you set, and for nothing else.
The AI works inside rules you control
You decide what the AI may say, what it must escalate, and who approves. Every rule is versioned and auditable.
Any message that touches price, financing, trade value or a legal commitment is drafted first and released only on GM or manager approval.
Answers come from your records, or not at all
Vehicle, pricing and policy answers are restricted to your own records, and every vehicle recommendation cites the VIN and stock number it came from.
If the answer isn't in the data, the AI says it doesn't know and escalates to a person. It never invents a vehicle, a price or a promise.
Every action is logged
Every inbound message, AI draft, approval, edit and send is logged with a timestamp and actor. Logs are exportable for compliance review, and the AI can never delete or alter a logged conversation.
Privacy law and consent
BridleOS is designed to support PIPEDA and provincial privacy obligations for Canadian dealers. Unsubscribe and consent handling are built in for CASL, and the AI never contacts a customer who has opted out.
For US rooftops, BridleOS is designed to support the FTC Safeguards Rule.
SOC 2 Type II: in progress
Controls are being implemented against the SOC 2 Trust Services Criteria. The audit is not complete, and we do not hold a SOC 2 report today. The report will be available to customers when the audit is finished.
Questions and security reports
Send security questions, vendor questionnaires or a suspected vulnerability to hello@bridleos.ai. We reply within one business day.
Stop being the integration layer.
See BridleOS run a lead, a service booking and a VIN match end-to-end on your own inventory — in a 30-minute demo.