1. Demo Data
The public demo uses fake accounts only and does not contain real dealership records, Hunter Ford data, private notes, route maps, customer emails, or logos.
DealerReach Legal
DealerReach Security Overview
Version 1.0 | Effective June 13, 2026
The public demo is sample-data-only and front-end-only. Real dealership deployments should use private, organization-specific security controls.
2. Production Isolation
Customer deployments should separate organizations and restrict data access by role, organization, and business need.
3. Authentication and Roles
Production systems should use authentication, admin/user roles, permission checks, and secure session handling.
4. Audit History
Production deployments should track changes to account fields, notes, imports, users, roles, and billing events.
5. No Browser Secrets
Secret keys must remain server-side. Stripe secret keys, webhook secrets, and database service keys must never be exposed in client code.
6. Exports and Backups
Production deployments should include appropriate export, backup, retention, and deletion practices.
7. Limitations
No system is perfectly secure. Customers should manage authorized users, devices, passwords, and internal access policies.