Trust
Your data, handled the way we would want ours handled.
DriveLocal holds the contacts, the vehicle records, and the marketing history a dealership has built over years. This page says plainly who owns that data, how consent and removal are honored, who can see what, and what happens when something goes wrong. Where the honest answer is that something is still being built, it says that too.
Data ownership
The dealer owns its data. That is the whole principle, and everything else on this page follows from it.
- Contacts, vehicle records, and campaign history belong to the dealership they came from.
- We never sell them, and we never pool one dealer’s records with another’s to build a shared list.
- An agency working across several rooftops sees each rooftop’s data only inside that rooftop’s workspace.
- A dealership that leaves can ask for its records to be removed, and they are.
Consent and removal
Consent travels with the record. An opt-out is a fact about the contact, not about one campaign.
- Unsubscribes and suppressions are honored on every send, across every campaign and every channel.
- A text-message opt-out is honored when it arrives, and a confirmation is sent back.
- A deletion request is handled end to end, from the contact record to the lists and audiences it was part of.
- Requests come to the same address as every other privacy question, and a person handles them.
Access control
Sign-in is passwordless, so there is no dealership password to leak or reuse.
- People sign in with a one-time code sent to their email or phone, or with single sign-on through a work account.
- Every person has a role, and the role decides what they can see and change inside a workspace.
- Invitations are how people join a workspace. Nobody sees a rooftop they were not invited into.
- Sessions are held on the server, so access can be ended from there when someone leaves.
Workspace and environment separation
Each dealership’s workspace is its own boundary, and the public site is kept apart from the signed-in application.
- Every query the application runs is scoped to the workspace the signed-in person is working in.
- The public site you are reading now loads no dealer data at all.
- The database is locked down so that only the application’s own connection can read customer tables.
- The platform runs on managed services with their own controls rather than on servers we operate ourselves.
Incidents and backups
When something goes wrong, the people it affects hear about it from us.
- The database is backed up automatically on a schedule by the managed service that hosts it, and we can restore from those backups.
- If an incident touches a dealership’s data, we tell that dealership what happened, what was involved, and what we changed, in plain language.
- We do not hold a third-party security certification today, and we will not describe one until we do.
Report a security issue
If you find a vulnerability, tell us directly and give us time to fix it before saying so publicly.
- Write to us with what you found and how to reproduce it.
- A person reads every report and replies.
- While testing, please do not access, change, or delete data that is not yours, and do not test against dealership data at all.
Security reports go to legal@studiorllc.com, the same address the Privacy Policy gives for questions about your data.
Ask us anything on this page.
If a question about your data is not answered here, ask it during a walkthrough and we will answer it plainly, including where the answer is not yet.