Skip to main content
Security Posture

Safeguards-ready today. Audit-ready path documented.

LouieAuto is FTC Safeguards Rule program built in — all nine required elements tracked, with TOTP MFA and role-based access. SOC 2 Type I certification in progress; engagement confirmed with auditor. Targeted completion Q3 2026 — Type II operating-period audit follows. This page is the public summary; full control matrix and readiness roadmap available in the diligence data room under NDA.

Compliance matrix.

FrameworkScopeStatusEvidence
FTC Safeguards Rule (16 CFR Part 314)Dealer nonpublic personal informationBUILT-INControl matrix + risk assessment in data room
SOC 2 Type ISecurity, Availability, ConfidentialityIN PROGRESSControls implementation: complete. Auditor engagement: confirmed. Type I audit: scheduled Q3 2026. Operating period begins Q4 2026. Full control matrix in data room.
Progress: Controls complete · Auditor engaged · Audit Q3 2026
SOC 2 Type II6-month operating period post-Type IPLANNEDOperating period: Q4 2026–Q1 2027. Report targeted Q1 2027. Readiness roadmap available under NDA.
GLBA (Gramm-Leach-Bliley) Privacy RuleDealer customer financial infoALIGNEDData flow and consent documentation in data room
PCI DSSNot in scopeN/ANo card data stored; payment flows delegated to dealer's existing processor
CCPA / CPRACalifornia resident dataALIGNEDPrivacy policy, deletion workflow, data subject request handler documented

FTC Safeguards — All 9 Elements

Built Into Every License

16 CFR Part 314 requires all nine elements of an Information Security Program. Louie has every one built in.

Designate a Qualified Individual
Owner role in Louie = designated responsible party, logged in audit trail
Risk Assessment
Automated risk scanning built into the FTC Safeguards module
Implement Safeguards
TOTP MFA, role-based access, encryption at rest (LUKS), session timeouts
Oversee Service Providers
Vendor contract tracking in compliance module
Train Your Staff
Role-based training triggers built into onboarding flow
Monitor and Test
Automated compliance checks — flagged daily in Morning Brief
Incident Response Plan
Response plan template + incident log in compliance dashboard
Update Your Program
Quarterly review reminder triggered by Louie compliance agent
Board Reporting
Owner-level compliance summary available on demand
SOC 2 Certification Progress
SOC 2 Type I Target: Q3 2026
In Progress — 40%
Design & gap phase complete · Controls implemented · Auditor engaged · Audit scheduled Q3 2026
SOC 2 Type II After Type I — Q1 2027
Planned — 10%
6-month operating period begins Q4 2026 · Report targeted Q1 2027 · Readiness roadmap in data room
🖥️
Louie runs on-premise. Your customer data never leaves your building.
  • No cloud upload — ever
  • No SaaS subscription required
  • No vendor breach risk — your server, your firewall
  • AES-256 encryption at rest (LUKS)

When a dealer's IT counsel asks "where does our customer data go?" — the answer is: on your hardware. This is a fundamental architecture choice that legacy DMS and legacy DMS providers cannot match. You own the server, you own the data, you own the brain.

Threat model (STRIDE summary).

CategoryPrimary threatControl
SpoofingDealer staff impersonationSession token + IP fingerprint; rotation on anomaly
TamperingModification of lender decisioning logicRead-only system-prompt release; code-signed deployment pipeline
RepudiationDealer disputes Louie recommendationBroker-access log; full request/response audit trail; NDA-compliant retention
Information disclosureCustomer PII leakage via LLM prompt loggingProvider-routing layer redacts PII before send; Anthropic/OpenAI zero-retention flags set; local Ollama fallback
Denial of serviceFlood against /api or /copilotNginx rate-limiter + per-token throttle; graceful degradation to cached responses
Elevation of privilegeBroker token escalationPer-broker scoped token; admin secrets gated by header + IP allowlist

Data handling.

Data classes

  • Dealer identifiers — rooftop name, DMS integration tokens. Encrypted at rest.
  • Customer PII — name, phone, email, DOB for deal structure. Encrypted in transit (TLS 1.3); sensitive fields and exports encrypted (AES-256-GCM); redacted before LLM calls.
  • Financial data — credit score tier, income range, deal structure. Never transmitted to third-party LLMs as raw values; bucketed before send.
  • Operational telemetry — request latencies, error rates, module usage. No PII.

Retention & deletion

  • Dealer-initiated deletion: honored within 5 business days.
  • Customer deletion request: honored within 30 days (CCPA / CPRA aligned).
  • Broker access logs: 24-month retention under NDA, then purge.

Cross-border transfer

  • All data resides on US-region infrastructure.
  • LLM inference: provider routing allows selecting US-region endpoints (Anthropic, Azure, GCP).
  • Local Ollama inference available for dealers who require on-prem processing.

Incident response.

SeverityDefinitionResponse SLA
P0Data exposure confirmed60 minutes to containment; 24 hours to dealer notification; 72 hours to regulator where required
P1Service outage affecting deal flow15 minutes to acknowledge; 4 hours to restore or provide workaround
P2Degraded feature or non-critical errorBusiness-hour response; 48 hours to resolve
P3Cosmetic or low-impactNext release cycle

Detailed runbook, contact tree, and post-mortem template are in the data room. Report vulnerabilities to brian@louieauto.com — PGP key published in /.well-known/security.txt.

Dependency & supply chain.

  • SBOM generated per release (CycloneDX format).
  • Dependencies pinned; npm audit + Snyk CI integration on readiness path.
  • No known high-severity unpatched CVEs at date of publication.
  • LLM provider routing isolates single-vendor failure — Anthropic, OpenAI, Azure, GCP, local Ollama all supported.

This page is a public summary. The full security pack (control matrix, gap analysis, penetration-test scope, SOC 2 readiness roadmap) is available under NDA.

Uptime SLA.

MetricCommitmentMeasurement
Service availability99.9% per calendar monthnginx access logs + PM2 process monitor; status.louieauto.com
Scheduled maintenanceOff-peak only (2–4 AM local); 48-hr advance noticeAnnounced via status page and email to account contacts
P0 containment60 minutesFrom first confirmed report to service restoration or workaround
P1 restore4 hoursDeal-flow-impacting outage resolved or workaround confirmed
P2 resolution48 business hoursDegraded feature or non-critical error

Full SLA terms at louieauto.com/sla. Enterprise and Managed Services tier accounts receive SLA credits and dedicated escalation contacts. Group and Enterprise tier: 12-month minimum with formal SLA addendum.

Penetration testing & vulnerability disclosure.

Pen test cadence

  • Annual penetration test scheduled. Scope: API surface (/api/*), authentication flows, session management, data access controls, injection vectors.
  • Testing methodology: OWASP Testing Guide v4 + ASVS Level 2 controls.
  • Reports and executive summary available under NDA to qualified acquirers and enterprise partners.

Vulnerability disclosure

  • Responsible disclosure: report to brian@louieauto.com with subject line SECURITY:. PGP key at /.well-known/security.txt.
  • Acknowledgement within 24 hours. Severity assessment and remediation timeline within 5 business days.
  • Coordinated disclosure window: 90 days from report unless extended by mutual agreement.
  • No bounty program active at this time. Researchers acknowledged in release notes.

Enterprise support tiers.

All license holders receive dedicated support. Managed services partners (Presidio-model) receive joint escalation access for their client rooftops.

LicenseSupport channelP0/P1 SLADedicated contact
LouieAuto License ($19,995 one-time)Email + AI assistant + Slack channel4-hr P1 SLANamed CSM
Multi-rooftop (2+ stores)Direct phone + Slack + email60-min P0 / 4-hr P1Named CSM + SE
Managed Services partnerJoint partner escalation portal60-min P0 / 4-hr P1Named partner SE

For enterprise procurement: send security questionnaires and vendor assessment forms to brian@louieauto.com. Full responses within 5 business days. NDA available on request before data room access.

System requirements.

LouieAuto ships two ways: a downloadable desktop app (Windows or Mac) for single rooftops — with the AI brain running on-device — and a local-server deployment for multi-rooftop groups (staff use a browser, no per-device install). The requirements below are for the group server host and client browsers.

Server (on-premise host)

ComponentMinimumRecommended
OSUbuntu 20.04 LTS or Windows Server 2019Ubuntu 22.04 LTS
CPU2-core (x86-64)4-core
RAM4 GB8 GB
Disk20 GB SSD100 GB SSD (for deal history + reports)
Node.js18 LTS20 LTS (current production runtime)
InternetRequired only for optional cloud-LLM featuresOn-device Ollama brain runs offline; broadband recommended for cloud features + DMS sync

Client browsers (all staff devices)

BrowserMinimum versionNotes
Chromev110+Recommended
Firefoxv110+Fully supported
Safariv16+iOS/iPad included
Edge (Chromium)v110+Fully supported
IE / Legacy EdgeNot supported

Bandwidth

  • Standard operations: 1–5 Mbps per active user (dashboards, deal entry)
  • AI features (briefings, deal coach, voice): 5–10 Mbps per concurrent AI session
  • DMS sync (nightly batch): burst up to 25 Mbps for 2–5 minutes
  • Multi-rooftop groups: recommend dedicated LAN segment for server; standard business internet (50 Mbps+) for user devices

Backup & restore

  • Automated daily backup: runs at 2 AM local; average completion 3–8 minutes depending on database size
  • Restore from backup: average 12–25 minutes for a single-rooftop database; up to 45 minutes for a multi-store group database
  • Optional cloud sync: encrypted offsite backup to dealer's cloud provider (AWS S3, Azure Blob, or Google Cloud Storage) configurable in admin settings
  • Point-in-time recovery: available to the last automated backup (24-hour max data loss window without continuous WAL archiving)

The on-device AI brain (local Ollama inference) runs offline after initial setup — deal entry, inventory, compliance, pipeline, lender routing, and the nightly learning loop all function without internet. Optional cloud-LLM features (e.g., long-form Ad Generator, conversational chat) use an internet connection to your configured provider. Fully air-gapped operation is supported — setup guide at louieauto.com/developers.

Ready to see it run?

Walk the live platform — every deal screened, logged, and audit-ready. The full SOC 2 / FTC Safeguards control matrix is available under NDA.

Take the Floor → Request the control matrix →