B4R

B4R · Buying 4 Retail

Privacy Policy

Effective date: [[EFFECTIVE_DATE]] · Operated by [[LEGAL_NAME]]

The short version

This summary is here to help you read the policy. The full text below is the policy.

1. Who we are

[[LEGAL_NAME]] ("we", "us") runs B4R, short for Buying 4 Retail, at buying4retail.com. B4R is appraisal software for used-car dealerships. It tells a buyer what is likely to go wrong with a vehicle and what that tends to cost, so the dealership can price a trade-in correctly.

This policy covers the website and app at buying4retail.com. It applies to people who visit the site and to the appraisers, managers and other dealership staff who use B4R with an account. If your dealership has an agreement with us, our Terms of Service and any order form also govern how we handle what the dealership puts into B4R.

2. What we collect when you make an account

You can look up vehicles without an account. You need one to save anything. When you make one, we collect:

If you sign in with Google or Microsoft

If you choose "Continue with Google" or "Continue with Microsoft", that company asks for your permission and then sends us basic profile information: your email address, your name, the ID that company uses for your account, whether your email address is verified and, where it provides one, a link to your profile picture. From Google we ask only for the openid, email and profile permissions. From Microsoft we ask only for openid, email, profile and User.Read (your basic profile). We don't ask either company for your mail, calendar, contacts or files, and B4R cannot see them.

Supabase stores that profile information with your account. B4R itself uses only your email address and your name. Section 12 covers this in more detail.

3. What your dealership enters about vehicles

Most of what B4R holds is work: vehicles your store looked at and what it decided. That data belongs to your dealership (see the Terms, section 6).

Things you enter that we don't keep

What we don't collect about your customers

B4R does not ask for the names, phone numbers, email addresses or home addresses of the dealership's customers, and there is no field for them anywhere in B4R. Information about a consumer can reach us only incidentally: a VIN and mileage, what is visible in a photo, or something a user types into a free-text note. Please don't put customer contact details into notes, change requests or Diagnose.

4. What we collect automatically

5. Who receives data, and why

We use these services to run B4R. Each receives only what its part of the job needs.

Supabase

WhatEverything in sections 2 and 3 that we keep: accounts, profiles, stores, appraisals, saved cars, photos, notes, change requests, Diagnose questions, plus the logs in section 4. Supabase also stores cached copies of vehicle and market lookups.

WhyIt is our database, our sign-in service and our photo storage. Our database is hosted in the United States (AWS us-east-1, Northern Virginia).

Vercel

WhatEvery request to buying4retail.com, with its IP address, browser and address; the page analytics in section 4. Vercel's network also caches some of our server's answers, including VIN decodes and a VIN's listing history, under an address that contains the VIN.

WhyIt hosts the website, runs our server code and scheduled jobs, and serves cached answers faster.

Resend

WhatYour email address and the email we send it: a one-time sign-in link, or the link that confirms a new account. The emailed sign-in link is also how you get back in if you forget your password.

WhyIt delivers those emails from buying4retail.com on behalf of our sign-in service.

NHTSA (U.S. National Highway Traffic Safety Administration)

WhatA VIN, to decode it. For recalls, owner complaints and safety ratings, only the year, make and model, never a VIN.

WhyIt is the public source for VIN decoding and federal safety data. These requests come from our server, not your browser, so NHTSA does not see your IP address.

MarketCheck

WhatFor market data: the year, make, model, trim, a mileage range, and the ZIP code and radius or the state you searched. For listing history: the VIN.

WhyIt supplies other dealers' asking prices, competing listings, cars that recently left dealer lots, days' supply and a VIN's past listings. Requests come from our server, not your browser. The answers contain other dealers' public listings.

Anthropic (Claude)

WhatOnly what each feature needs, sent from our server:

  • Diagnose: the symptom you typed, the vehicle, the list of catalogued issues for it, and up to seven earlier turns of that conversation.
  • Buy score: the vehicle, its reliability and known issues, condition, mileage, the retail and wholesale figures (including a Manheim MMR you typed in), the maximum buy and recon totals.
  • Risk score: the vehicle, its catalogued issues, the recall count, mileage and repair totals, with federal complaint data.
  • Common questions for a vehicle: saved Diagnose questions and their matches, without the store.
  • Catalogue corrections: when we review a change request, the requested change and the reason you gave.
  • The daily market brief: no user data at all.

We don't send your name, email address or account with any of these.

WhyTo produce the answer B4R shows you, and for nothing else. Anthropic's Commercial Terms state that "Anthropic may not train models on Customer Content from Services." Anthropic's privacy center says it automatically deletes API inputs and outputs within 30 days, except where it keeps them longer to enforce its Usage Policy or to meet legal requirements. When our Anthropic key is not configured, these features run on built-in formulas and nothing is sent to Anthropic; the market brief is simply not produced.

Google and Microsoft

WhatOnly if you choose to sign in with them: they learn that you are signing in to B4R, and they send us the profile information in section 2.

WhyTo sign you in. Their own privacy policies apply on their sign-in pages.

Content delivery: Google Fonts, unpkg and cdnjs

WhatWhen your browser opens the B4R app, it downloads fonts from Google Fonts and code libraries from unpkg.com. When you upload a run sheet, it also downloads file readers from cdnjs.cloudflare.com. Like any web server, these receive your IP address, browser details and the page that asked. Google says its Fonts service sets no cookies.

WhyThey deliver the fonts and code the app is built on.

People inside B4R who can see your data

Other disclosures

6. What we don't do

7. Cookies and browser storage

B4R sets no cookies. It keeps a few small items in your browser's local storage, which stays on your device:

Vercel Web Analytics uses no cookies. Clearing this site's data in your browser removes all of the above. If you sign in with Google or Microsoft, their pages set their own cookies on their own sites.

8. How long we keep data

We have not set automatic time limits on most data. Here is what actually happens today:

9. Seeing, correcting, exporting and deleting your data

We won't treat you differently for making any of these requests.

10. Security

No system is perfectly secure. If a breach affects your personal information, we will notify affected account holders and dealerships without unreasonable delay and as the law requires.

11. Children

B4R is a business tool for dealership staff. It is not meant for anyone under 18, and we don't knowingly collect personal information from children. If you think a child has made an account, email us and we will delete it.

12. Google and Microsoft sign-in data

Google user data

B4R's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Microsoft

Microsoft sign-in works the same way. We receive the basic profile information in section 2, use it only to create your account and sign you in, and keep it with your account until the account is deleted. You can remove B4R's access in your Microsoft account settings, or, for a work account, ask your IT administrator. As with Google, removing access does not sign you out of B4R or delete your account.

13. California privacy disclosures

These disclosures are made under the California Online Privacy Protection Act and the other California laws named below.

California Do Not Track disclosures

B4R does not track you across other websites over time, and we have not put advertising or cross-site tracking tools on it. Because there is no cross-site tracking to turn off, B4R does not change what it does when your browser sends a Do Not Track signal or a Global Privacy Control signal. No third party collects personal information about your online activity over time and across different websites through B4R. The content delivery services in section 5 receive your IP address and browser details when your browser fetches files from them, and their own policies cover what they do with that.

California Consumer Privacy Act

The California Consumer Privacy Act (CCPA) applies to businesses above certain thresholds: more than $26,625,000 in annual revenue, buying, selling or sharing the personal information of 100,000 or more California consumers or households, or earning half of annual revenue from selling or sharing personal information. We don't meet any of them, so the CCPA does not apply to us directly. Some dealerships that use B4R are covered by it. For those dealerships we act as a service provider: we process the personal information they put into B4R only to provide B4R to them as this policy and our Terms describe, and we don't sell or share it as the CCPA defines those words. Whatever the law requires of us, you can make the requests in section 9.

Direct marketing (California Civil Code section 1798.83)

We don't disclose personal information to third parties for their direct marketing purposes.

14. Where data is processed

B4R is run from and for the United States. Our database is hosted in the United States. Our other providers may process data in the United States and in other countries where they operate; Vercel's network, for example, serves the site from locations around the world.

15. Changes to this policy

When this policy changes, we update the effective date at the top. For a material change, such as collecting a new kind of data, sending data to a new service or using it in a new way, we will email account holders at the address on their account at least 30 days before the change takes effect. Earlier versions are available on request.

16. Contact us

[[LEGAL_NAME]]

[[MAILING_ADDRESS]]

Email: [[CONTACT_EMAIL]]