Security
What we protect, and how.
Stores trust Driverseat with their shoppers' details, their website and their team's access. This page says what protects each one today, exactly as the product does it, and marks what is still to come.
01 · Shopper data
A shopper's most private answers stay encrypted.
When a shopper adds a finance profile in Build My Deal, their date of birth, the last four of their SSN, income and address are each stored encrypted in the database. The lead goes on to your team and your CRM without them.
A finance profile, as the database holds it
An example shopper's Build My Deal answers, and what is stored for each.
Date of Birth04/12/1987
Stored asc30d04070302b3aa511f2d617ede79d23b010ef86796c590f29f15c3f92d6cf1f24b92d6cdfad12507d5385731ff46a392a0efe59b422c1dcacd4056dda593472606d1936c565063578edab5
Last 4 of SSN4417
Stored asc30d04070302320e61899fbb3a2a72d23501cc9333e62e82fd1f070935e47f218990025ca3d6ae0066e310e23b141017d5b4edebc3c78525f916bba73236e2330bd1557bb29c
Gross Annual Income86000
Stored asc30d040703021a67154583f47d017bd23601dc62a6ecc2e1a84ca2168fb451cbfb68c043e2057818f6072fcf27702656e0f8c31924620a317eaec06f032e5112e3abf10f080f42
Address2210 Oak Ridge Dr
Stored asc30d0407030229330ff169d3897b68d24201b75088854792d943c6c8ab8e4952072273fa846c56200168e6e5340e4305b55a8a587203bbe4447bddefba972aa5293433e8cfc19aaa9b2cdc81ad6b273f7bd984
Zip Code56401
Stored asc30d04070302d1098e67f5efd5796ed236010055a57f4c3e2b4a71342d5935d8f82a78b266e47454570627ad42af263ddb170bc90fb5a09334031307fb408c8c981ecc930d639f
Each answer is sealed on its own with AES-128 and a fresh salt, so the same answer never stores the same bytes twice. This is write 1 of 4.
The lead travels on to your team without it.
- Lead notes“Applicant finance profile: Captured in Driverseat.”No finance profile
- Email to your CRMName, email, phone and the carNo finance profile
- Inquiry linkContact, car, trade-in and visitNo finance profile
pgcrypto · pgp_sym_encrypt
02 · Access
Everyone sees only what their role allows.
Each person is Admin, Content or Analyst at each store. The dashboard hides what a role can't use, and the API checks the role again on every request, so a hidden button is never the only lock.
Who
Tries to
- Signed inSession token verifiedpassed
- Member of this storeBellwether Ford, or its grouppassed
- Role allows itAdminAdmin, ContentAdmin, Content, Analystpassed
- Runslead goes aheadupdatePageDetails goes aheadcreateSlideReport goes aheadcreateInvite goes aheadrotateDealershipApiKey goes aheadNothing is read or changedpassed
authorization: Bearer eyJhbGciOiJSUzI1NiIs…
mutation { updatePageDetails(input: { … }) { … } }
← { "data": { "lead": { … } } }
← { "data": { "updatePageDetails": { … } } }
← { "data": { "createSlideReport": { … } } }
← { "data": { "createInvite": { … } } }
← { "data": { "rotateDealershipApiKey": { … } } }
← { "errors": [{ "message": "You do not have the required role for this dealership." }], "data": null }
← { "errors": [{ "message": "You no longer have access to this dealership." }], "data": null }
← { "errors": [{ "message": "Unauthorized" }], "data": null }
All 25 requests
8 run · 17 refused
The same person can hold a different role at each store in a group.
Every request, checked by the server
An example store. Pick who, and what they try. The API decides, not the button.
Carla Nguyen · updatePageDetails · runs
Driverseat API · every request
Team invites last 14 days and only work for the email they were sent to. API keys are shown once and kept only as a hash.
03 · Every change accounted for
No change without a name. No AI change without a yes.
The activity log keeps who changed what, when, and the value it replaced. A change the assistant drafts waits for the person who asked, for up to two days, and runs at most once, exactly as they saw it.
One proposal, five checks
An example change at Bellwether Ford, asked for by Dana. Pick what happens next.
The assistant drafted one change for Dana: the Winter tires page's meta title, from “Winter tire event” to “Winter tire event | Bellwether Ford”.
- The person who askedDana asked, so only Dana decides.“Only the delegating user can act on this proposal.”Passed
- The exact change they sawThe payload hash matches the preview.Saw 3f9ac04e…7bd2c21e. On record: 91e0b7aa…04f6d3a8.“The agent action changed after it was presented.”Passed
- Within two daysA proposal expires 48 hours after it's made.Asked Tuesday 11:32 AM. Decided Thursday 11:40 AM.Passed
- Not run beforeIt runs at most once, and is never retried.Applied at 11:34 AM. The first result comes back.Passed
- Role still allows itChecked again right before it runs.Passed
Dashboard · Assistant
Approving by email works without signing in, so the link itself is the key: it covers one person and one exact change, ends with the proposal, and opening it changes nothing until “Approve and run it” is pressed. Passwords, keys and shopper contact details are logged only as Set or Not set.
04 · Consent and privacy
Scripts wait for the shopper's say-so.
Turn on the built-in banner and every tag on your site waits for its kind of consent. Google hears the choice through Consent Mode. Already use ComplyAuto, Privacy Pillar or KPA? The banner steps aside for them.
Scripts on this page
- The storefront itselfEssential
- Google AnalyticsAnalytics
- Microsoft ClarityAnalytics
- Google Tag ManagerMarketing
- Meta pixelMarketing
- The store's own scriptsMarketing
- Podium chatFunctional
- KBB trade-inFunctional
Google Consent Mode
- analytics_storagedenied
- ad_storagedenied
- ad_user_datadenied
- ad_personalizationdenied
Visit history for leads
Not keptKept only when the shopper allows Analytics.
What a page may run
An example store with the built-in banner on. Make a choice in the banner.
No choice yet · 7 scripts waiting · Consent Mode denied
Storefront · Cookie preferences
A shopper's choice is kept for a year and can be changed from the Cookie preferences link in your footer. Switching a kind off reloads the page, so nothing it allowed keeps running.
05 · Leads
The link in every lead email expires, and you can pull it.
Each lead your CRM receives carries a link to the inquiry in Driverseat, so your team sees the shopper's visit without signing in. The link works for 90 days, an Admin can replace or revoke it, and Driverseat keeps only a fingerprint of it.
The inquiry link in a CRM email
An example lead. Drag through the days, or replace or revoke the link.
Day 12 of 120 · Oct 8
The link in the CRM emailSep 26 to Dec 25, expires after 90 days
Its replacementNone
Replacing or revoking stops the current link immediately. Links already delivered in CRM comments are not updated.
Driverseat keeps only a SHA-256 fingerprint of the link, with when it expires and whether it was revoked. The link itself isn't stored.
Leads · Standalone inquiry
Inside the dashboard, leads are Admin only. Bots that fill the hidden field on your main forms see a thank-you and are sent nowhere. Every delivery to your CRM is tracked and retried, and its status comes from signed reports from our mail service.
06 · Infrastructure
Staging stays hidden. Live goes out over HTTPS.
Stores run on Vercel. Until launch, a store's staging address tells search engines to stay away, lists nothing in its sitemap and loads no Google tags. The switch to the real domain waits until Vercel confirms it and its certificate.
Go live
Driverseat switches the site to the live domain once everything below is in placewww.bellwetherford.com is the site's address now.- Domain attached to hosting, doneAttached automatically on connect. Checking again retries it.On the storefront project, with the bare domain redirecting to www.
- DNS pointing at Driverseat, waitingAdd the records, then check.Both records found.
- HTTPS certificate issued, waitingVercel confirms this once the records have propagated.Vercel confirmed the configuration.
- Home page published, waitingPublish the home page from Website → Pages.The home page is published.
- GET https://bellwether.driverseat.io/x-robots-tag: noindex, nofollow, noarchive
- <meta name="robots">noindex, nofollow, noarchive
- GET /sitemap.xml0 URLs
- Google Analytics, Tag Managernot loaded
From staging to live
An example store's launch. Check the records, go live, and compare the two addresses.
bellwether.driverseat.io · noindex, nofollow, noarchive · empty sitemap
Settings · Domain
After launch, the domain's records are rechecked every morning. To have personal information deleted, follow the steps on our data deletion page.
07 · Compliance
Where we stand, plainly.
We don't have a SOC 2 report yet. Until we do, this is what is in place today, each item as the product does it.
SOC 2
Coming soon
Filling in a vendor review for your store? Send us the questions.
support@driverseat.ioIn place today
- Finance profiles encryptedDate of birth, SSN last four, income and address, each encrypted in the database.
- Roles per storeAdmin, Content or Analyst at each store, checked by the API on every request.
- Invites that expireA team invite lasts 14 days and only works for the email it was sent to.
- API keys stored as hashesShown once when made. Admins can replace or revoke them.
- An activity logWho changed what and when, with the value it replaced.
- AI changes approved firstBy the person who asked, for the exact change they saw, run at most once.
- Signed webhooksMessages from Stripe, SendGrid and Meta are rejected unless their signature checks.
- No card numbersStore billing runs on Stripe by bank payment. No shopper payment goes through us.
Report a security issue
Found something that looks wrong? Tell us first.
Email support@driverseat.io with what you found and the steps to see it again. Please give us the chance to fix it before you share it, and never test with a store's real shoppers or their data.