What we collect
Only what you type into the audit: your email, and optionally your dealership, name and role. Plus your answers to the handoff questions.
Privacy / Data handling
What we collect, and what we do with your store's data.
Two different things live on this page. The first is the audit form on this website. The second is how dealership data is handled once there is an actual build. Both are short on purpose.
Questionsjoshua@dealershipautomations.comDeletion requests answered the same way
The audit form on this site
Five lines, and that is the whole policy.
Why
So Joshua can read the brief and reply to you. That is the only reason it exists.
Where it goes
A private database we control. It is not sold, shared with a marketing platform, or used to build an advertising audience.
How long
Until you ask us to delete it. Email us and it goes.
What we do not do
No tracking pixels for third-party advertising, no lead resale, no enrichment against outside data brokers.
Integrations and security
Your systems stay yours.
A dealership build touches the DMS, the CRM, the phone system and customer records. These are the standing rules for that access. They are written into the runbook for every engagement, not agreed to verbally.
Source of truthThe DMS or the store's approved inventory feed decides the facts. A workflow never invents trim, price, warranty status or availability.
AccessRead scopes wherever a read is enough. Write access is requested per workflow, named in the runbook, and revocable by the store at any time.
Customer dataStays inside the systems the store already runs. We connect to them; we do not create a shadow copy of the customer base.
Call and message dataRecording, retention and consent follow the store's existing policy and the law in its state. We do not change those settings on a store's behalf.
CredentialsHeld in the store's own vault or secret manager. We do not keep dealership credentials in project files, documents or email.
Audit trailEvery automated action writes who or what did it, from which facts, under whose approval. The store keeps that record.
ExitPermissions, runbooks, data maps and change control are documented for the dealership. A system should not need its builder.