Identity and contact details
Full name and email address; a mobile phone number when supplied or required for phone or text contact; and a business name for a powersports-business applicant.
Draft for review
This page previews the information RideWorth must finalize before Buyer Pilot interest registration can open. It is not an effective privacy notice, a live withdrawal channel, or permission to collect applicant data.
Not effective: Draft 2026-08-26-draft-r1. No effective date, approved privacy contact, retention schedule, published notice, or withdrawal mechanism has been assigned. All of those boundaries remain closed.
Current operational truth
Interest registration is closed. This preview has no submission path, so nothing entered here can be sent or saved and there is no Buyer-Interest record to withdraw today.
This draft applies only to the planned Buyer Pilot. It is not the privacy notice or request process for seller submissions, staff accounts, or any other RideWorth service.
If the separate intake gates are approved, the notice must describe these minimized categories plainly and must stay synchronized with the trusted applicant contract.
Full name and email address; a mobile phone number when supplied or required for phone or text contact; and a business name for a powersports-business applicant.
A five-digit ZIP code and confirmation choice; derived city and state; and a private server-derived service-area result, coarse band when known, and derivation provenance. The private result, band, and provenance are not returned to the browser or used as an automatic qualification decision.
Buyer type, vehicle categories, budget band, expected timeline, pickup capability, preferred contact method, and optional experience, purchase-frequency, and qualification context.
The notice and consent versions shown, required pilot-contact consent, separate optional marketing consent, associated timestamps, and future records needed to honor a withdrawal or privacy request.
Server-controlled workflow or status values, source attribution such as a physical placement or QR campaign, and an opaque public reference only if one is separately approved and retained internally.
A client submission identifier, an email-deduplication HMAC and its pepper version, and limited request, anti-abuse, and message-delivery evidence needed to protect the service and prove whether an approved communication was sent or stopped.
These are design requirements, not a live request procedure. An effective notice must replace them with truthful, monitored contact instructions.
Publication blockers
Unresolved
Approve the legal operator name, mailing address, and an active monitored privacy contact or equivalent secure request mechanism.
Unresolved
Approve how long applicant, consent, security, suppression, and request evidence is kept, plus documented deletion exceptions and disposal controls.
Unresolved
Approve the actual provider categories, data each provider receives, contractual restrictions, and the truthful sale or targeted-advertising disclosure.
Unresolved
Approve request types, identity-verification rules, response and appeal handling, authorized-agent handling, and a method that does not require a new account.
Unresolved
Approve accessible ways to revoke pilot contact and optional marketing consent, how every channel is monitored, and how suppression evidence prevents later contact.
Unresolved
Approve who may submit and how the program avoids collecting personal data from people outside the approved audience.
Unresolved
Have qualified counsel review the complete, fact-checked notice and withdrawal process before assigning an effective date or opening intake.
The publication boundary is still publication: null and the request boundary is still withdrawalRequest: null. Counsel and the owner must approve the completed facts before an effective date can be assigned.