Privacy notice

When you register or sign in, account information such as your email address, account identifier, verification status, and selected buyer or seller role is processed to operate your account.

Seller listings may include vehicle specifications, VIN, price, photos, and city/state/ZIP. Approved listing details are public; the public listing shows the seller’s first name and does not display their email address or phone number. Search filters, saved searches, favorite listings, reports, and private message content are also processed to provide marketplace features.

Before submitting a first listing, sellers provide their legal first, middle (optional), and last names, date of birth, legal address, any different billing address, and images of the front and back of a driver’s license. These identity details and license images are private and are not included in public listings.

A security challenge may process a verification token and technical signals to distinguish a person from automated abuse. Routine service logs may include device, browser, and network information needed to operate and protect the site.

Information is used to authenticate accounts, confirm email status, publish and manage listings, support search and favorites, deliver requested saved-search alerts, enable private messaging, review safety reports, and protect the service from misuse.

Messages are available to their conversation participants and may be reviewed when needed to investigate reports, enforce marketplace rules, or respond to a legal obligation. Seller identity details are used to support account and listing verification, fraud prevention, and safety review. The marketplace does not process payments or request payment credentials.

We use service providers to support sign-in, account security, hosting, private image storage, and email delivery for alerts users enable. License images are re-encoded to remove image metadata and stored privately. Replit PostgreSQL and App Storage provide managed encryption at rest; data is protected in transit with TLS. Those providers process information as needed to perform their services and under the arrangements that apply to them.

Clerk provides account sign-in, and Cloudflare Turnstile supports the security check shown during sign-up. Their own privacy notices describe their processing in further detail.

The marketplace uses cookies needed for sign-in and request security, along with a preference cookie that remembers navigation state. We do not currently use advertising or analytics cookies, so the site does not show an optional cookie-consent banner.

If non-essential analytics or marketing technologies are added, this notice and any consent controls will be reviewed before they are enabled. This explanation is part of a draft notice and should receive legal review before launch.

We retain seller identity details and license images while needed for account verification, marketplace safety, and legal obligations. Approved account-deletion requests remove the seller profile and its stored license images; limited audit records may be retained to document administrative actions. Retention periods should be confirmed in the final notice before launch.

Seller identity details are stored in Replit PostgreSQL, and license images are kept in private storage and served only through authenticated routes. Replit provides managed AES-256 encryption at rest for both services. Sellers can access their own profile; administrative access requires an administrator account with multi-factor authentication. We use technical and organizational safeguards intended to protect information. No online service can promise that every transmission or storage system is completely secure.

You may choose not to create an account. You can turn saved-search email alerts off in your account. Use the contact details on our Contact us page for account or privacy requests. Depending on your location, you may have additional rights to access, correct, delete, or restrict certain information.

We will revise this notice when the service or its data practices change and publish an updated effective date. This placeholder notice should be replaced with the final notice before launch.