Security and data handling for dealers and dealer groups
We never receive customer names, credit applications, deal jackets or any other shopper data from dealers. To make window stickers we only need vehicle data: VINs, stock numbers, prices and photos.
Last updated 2026-11-19. For your vendor file. Questions: support@stickerbyvin.com.
- Shopper data
- Never received from dealers
- Encryption
- HTTPS in transit, encrypted at rest
- Card numbers
- Never seen or stored by us
- Certifications
- No SOC 2 or ISO 27001 today
On this page
What data we handle
- Vehicle data: VINs, stock numbers, prices, options and photo links, entered by you or sent in an inventory feed or export.
- Dealer staff contact details: the work email addresses of people who sign in, and the dealership name, city and website.
- Billing records: which plan you bought and its status. Card details stay with Dodo Payments.
- Usage records: which VINs were looked up and which stickers were made, so we can bill and support you.
We do not receive consumer or shopper data from dealers: no customer names, addresses, phone numbers, driver's licence or Social Security numbers, credit data or deal data. If a future feature ever needs shopper data, we will tell you first and it will only be switched on with your written agreement.
Where it is stored
Everything runs on Cloudflare: the application on Cloudflare Workers, records in Cloudflare D1, cached lookups in Cloudflare KV, and sticker files in Cloudflare R2. Our application is set to run close to Cloudflare's US East region. We have no servers or office network of our own.
- In transit: the site only works over HTTPS (TLS), with HSTS switched on. All calls to our providers use HTTPS.
- At rest: Cloudflare encrypts D1, KV and R2 data at rest.
- Secrets (provider API keys) are kept as encrypted Cloudflare Worker secrets, not in our code.
Payments
Dodo Payments is our merchant of record. It takes the payment and issues the receipt or invoice. We never see or store card numbers or bank details.
We send email through Resend: sign-in codes, report links, receipts and replies.
Sign-in and accounts
- Dealer accounts have no passwords. You sign in with a one-time code or link sent to your email, or with Google sign-in.
- A sign-in code expires after 20 minutes and stops working after 5 wrong tries. Sign-in requests are rate-limited.
- Every account can turn on 2-step verification with an authenticator app (Google Authenticator, 1Password, Authy or similar). Sign-in then also needs the 6-digit code from the app. Ten one-time backup codes cover a lost phone. After 10 wrong codes, sign-in pauses for 15 minutes.
- The owner of a Dealer Pass can require 2-step verification for everyone on the team. Team members who haven't set it up can't use the account until they do.
- Authenticator secrets are stored encrypted. Backup codes are stored only as one-way hashes.
- If you use Google sign-in, Google gives us only your email address. Your Google 2-step verification applies.
- Sessions last up to 30 days. We store only a one-way hash of each session id, sign-in token and API key, not the value itself.
- Each dealer account can only see its own stickers, reports and seats.
Who at StickerByVIN can access data
Access is limited to the operators of StickerByVIN. We keep 2-factor authentication switched on for every provider account that holds or can reach your data (Cloudflare, Dodo Payments, Resend, Google). We only look at dealer data to run the service, bill it, or answer your support request.
Backups
Cloudflare D1 keeps a point-in-time history of our database (Time Travel), so we can restore it to an earlier minute within the retention window Cloudflare gives our plan. Files in R2 are stored by Cloudflare with very high durability. We do not keep a separate offline backup today.
Uptime and monitoring
Uptime for the site and the API is checked every 10 minutes and shown on our public status page, with 90 days of history. A separate check looks at site errors every 30 minutes and alerts us. Cloudflare's network protection against denial-of-service attacks sits in front of the site.
If something goes wrong
Report a security incident or a suspected breach to support@stickerbyvin.com. If we confirm a breach that affects your data, we will tell you by email within 72 hours, with what happened, what data was involved and what we are doing about it.
Reporting a vulnerability
See our security.txt. Email support@stickerbyvin.com with the details. Please do not access other people's data or disrupt the service while testing. We will reply, fix confirmed issues and credit you if you want.
Data retention and deletion
- VIN lookup results are cached for 30 days (24 hours if no sticker exists).
- Reports and stickers you make are kept so their links keep working.
- Anonymous visit records are deleted after 60 days.
- Order and billing records are kept as long as accounting law requires.
- Your account data is kept while your account is open.
To delete your dealership's data, email support@stickerbyvin.com from an account address. We delete account data, staff emails, stored inventory data and your reports within 30 days, except billing records we must keep by law, and confirm by email.
Subprocessors
These services process data for us. Vehicle data providers receive the VIN only, never anything about you or your customers.
| Provider | What for | Data it gets |
|---|---|---|
| Cloudflare cloudflare.com | Hosting, database (D1), cache (KV), file storage (R2), bot check (Turnstile), network protection | All data we store |
| Dodo Payments dodopayments.com | Payments and invoices, as merchant of record | Billing name, email, payment details (we never see card numbers) |
| Resend resend.com | Sending email (sign-in codes, report links, receipts) | Email address and the email we send |
| Google google.com | Google sign-in (optional) and Google Analytics | Email address if you use Google sign-in; page views, rough location and device type |
| MarketCheck marketcheck.com | Vehicle data and reproduced window stickers | VIN only |
| VinAudit vinaudit.com | Vehicle history and market value data | VIN only |
| Cardog cardog.app | Window sticker data for some brands | VIN only |
| NHTSA, EPA (fueleconomy.gov) and vehicle manufacturers nhtsa.gov | VIN decoding, recalls, original window stickers | VIN only |
| Paradigm Machines (Orion) paradigmmachines.ai | Session replay on public pages, to fix usability problems. Not used on account or login pages | Scrolling, clicks and pointer movement on public pages |
| Telegram telegram.org | Internal alerts to our operators about new sales enquiries | Company name and contact email from an enquiry form |
We will update this list before we add a new subprocessor that handles dealer data.
Dealer vendor security questionnaire: our answers
Dealer groups often check vendors with the free STAR questionnaire (24 questions, based on the FTC Safeguards Rule). The questions below follow its topics, in our own words, with our honest answer. Most of the Safeguards Rule is about vendors that handle customer information. We do not, so several answers are "not applicable".
What we do not have: no SOC 2 report, no ISO 27001 certificate, no outside penetration test and no cyber insurance policy today. We would rather say so than leave you to find out.
Do you have a written information security program?
Yes, in short form. This page is our written summary of how we protect data, and we update it when our setup changes.
Is access to personal information limited by role and least privilege?
We do not receive consumer personal information from dealers. Access to our systems is limited to the operators of StickerByVIN. Each dealer account sees only its own data.
Do you assess risks at least once a year?
Yes. We review risks when we add a provider or a feature that touches new data, and at least once a year.
Do you securely dispose of data and documents?
We keep no paper records. Data is deleted from our database and storage on request or when its retention ends. Cloudflare handles the disposal of physical storage media.
Do you have a penetration test at least once a year?
No. We have not had an outside penetration test. Researchers can report issues through our security.txt.
Do you run vulnerability scans at least twice a year?
Not by an outside firm. Automated tests run before every release, we keep our software dependencies up to date, and Cloudflare's network protection sits in front of the site.
Do your service providers and subprocessors sign data processing agreements?
Our providers that hold data (Cloudflare, Dodo Payments, Resend, Google) apply their standard data processing terms to our accounts. Vehicle data providers receive VINs only.
Do all endpoint devices run endpoint detection and response (EDR)?
We have no servers or office network. The computers we use to run the service use the operating system's built-in malware protection with automatic updates. We do not run a separate EDR product.
Do you patch operating systems and software regularly?
Yes. The service runs on Cloudflare Workers, so Cloudflare patches the servers. Our computers install system updates automatically, and we update our code's dependencies regularly.
Is multi-factor authentication required on workstations and on-premises servers?
Not applicable for servers: we have none on premises. Our computers are locked with a device password or PIN, and every provider account uses 2-factor authentication.
Does your cloud application support and require multi-factor authentication?
Yes. Dealer accounts have no passwords. Sign-in needs a one-time code sent to the dealer's email, or Google sign-in. On top of that, any account can turn on 2-step verification with an authenticator app, and a Dealer Pass owner can require it for the whole team.
Is multi-factor authentication required for company email and identity accounts?
Yes. 2-factor authentication is on for our email and every provider account.
Are your engineers trained in secure coding?
No formal course. Our code uses parameterized database queries, stores tokens and keys only as hashes, keeps secrets out of the code and is covered by automated tests.
Do you follow platform and operating system security guidelines?
Yes. We follow Cloudflare's guidance for Workers: encrypted secrets, HTTPS only, and secure, HTTP-only cookies.
Do you use anonymized data in test systems?
Yes. Our tests use made-up data and public sample VINs. We do not copy dealer data into test systems.
Do you check that privacy and security features work as intended?
Yes. Automated tests, including checks on API keys and access to paid reports, run before every release. A failed test stops the release.
Do you run phishing simulations and security awareness training?
No. We are a small team and have no formal program.
Do you require complex, unique passwords?
Yes. Every provider account has its own long, unique password, and 2-factor authentication on top.
Is customer personal information encrypted?
Not applicable: we do not receive customer personal information. All data we hold is encrypted in transit (HTTPS) and at rest (by Cloudflare).
Do you keep automated backups offline or immutable?
Automated, but not offline. Cloudflare D1 keeps a point-in-time history of the database, and R2 stores files with very high durability. We do not keep a separate offline copy today.
Do you have cyber insurance that covers breaches of customer personal information?
No, not today. We do not receive customer personal information. Tell us if your group requires a policy for vendors.
Do workstations lock automatically when idle?
Yes. Our computers lock after a short idle time.
Do you use application allow-listing?
No.
Do you lock out credentials after repeated failed logins?
Yes. A sign-in code stops working after 5 wrong tries, and sign-in requests are rate-limited by IP address and email. With 2-step verification on, 10 wrong authenticator codes pause sign-in for 15 minutes.
Contracts and paperwork
Our Data Processing Agreement template is signed on request. Our Terms and Privacy policy apply to every account. For your group's own questionnaire, email support@stickerbyvin.com.