Skip to buyer pilot content

Draft for review

Buyer Pilot privacy and withdrawal preview

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

There is no active waitlist record to withdraw

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.

Data the future notice must explain

If the separate intake gates are approved, the notice must describe these minimized categories plainly and must stay synchronized with the trusted applicant contract.

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.

Coarse location information

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-interest profile

Buyer type, vehicle categories, budget band, expected timeline, pickup capability, preferred contact method, and optional experience, purchase-frequency, and qualification context.

Consent and request records

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.

Workflow and attribution

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.

Limited security and delivery data

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.

Intended purposes

  • Receive and human-review a request to be considered for the Buyer Pilot.
  • Confirm coarse service-area context without making an automatic applicant decision.
  • Contact an applicant about the pilot or a possible interview only under the required pilot-contact consent.
  • Send optional inventory or event marketing only under the separate optional marketing consent.
  • Protect the intake from abuse, keep consent and request evidence, and meet applicable legal obligations.

Uses this contract does not permit

  • No automatic approval, decline, qualification, ranking, invitation, or expiration.
  • No applicant profile is a reservation, offer, payment, or guarantee of inventory.
  • No seller submission, seller contact information, precise device location, credit, income, bank, financing, government identifier, document, or photograph enters this applicant contract.

Withdrawal principles for a future approved process

These are design requirements, not a live request procedure. An effective notice must replace them with truthful, monitored contact instructions.

  1. Withdrawing optional marketing consent must not withdraw a separate request for pilot consideration unless the person asks for both.
  2. Withdrawing pilot-contact consent must stop future pilot outreach; it must not be treated as an adverse applicant decision.
  3. A privacy or withdrawal request must use a published, monitored channel and collect only what is needed to locate and authenticate the requester safely.
  4. RideWorth must confirm what was withdrawn or could not be completed without exposing whether another person is on the waitlist.
  5. Deletion must not silently erase the minimum suppression or legal evidence needed to keep honoring an opt-out; the approved retention rule must explain that distinction.

Publication blockers

Decisions that must be real before this becomes a notice

Unresolved

Controller identity and contact

Approve the legal operator name, mailing address, and an active monitored privacy contact or equivalent secure request mechanism.

Unresolved

Retention and deletion

Approve how long applicant, consent, security, suppression, and request evidence is kept, plus documented deletion exceptions and disposal controls.

Unresolved

Service providers and sharing

Approve the actual provider categories, data each provider receives, contractual restrictions, and the truthful sale or targeted-advertising disclosure.

Unresolved

Privacy rights and authentication

Approve request types, identity-verification rules, response and appeal handling, authorized-agent handling, and a method that does not require a new account.

Unresolved

Pilot and marketing withdrawal channels

Approve accessible ways to revoke pilot contact and optional marketing consent, how every channel is monitored, and how suppression evidence prevents later contact.

Unresolved

Age and eligibility

Approve who may submit and how the program avoids collecting personal data from people outside the approved audience.

Unresolved

Legal review and effective version

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.

Back to the Buyer Pilot preview