Canonical draft
Read the current pre-launch terms.
The versioned Terms of Use and policy set remain marked not effective and require counsel and owner approval before transactional activation.
Open draft Terms of UseDraft terms and consent review
This demo inventories customer acknowledgements, seller commitments, auction rules, privacy notices, and version controls proposed for launch. It is not an operative agreement, does not record acceptance, and does not create a commercial relationship with Dravara, LLC.
Policy history
Review policies and archive status.
No click or demo action on this page accepts a policy. Exact acceptance must be bound server-side to an approved policy version when that workflow is activated.
Open draft policy centerBuyer Acknowledgement
- Checkout should show item price, fees, handoff choice, return setting, condition proof, and report windows before a buyer confirms.
- Buyers should acknowledge that item photos, condition notes, seller terms, hub notes, and shipment choices become part of the order record.
- Report prompts should explain documentation needed for missing, damaged, not-as-described, or pickup-release issues.
Seller Agreement
- Sellers should agree to accurate titles, category attributes, item photos, condition notes, included accessories, return choices, and handoff commitments.
- Seller terms should disclose fee rules, release timing, reserve holds, response expectations, records, restricted items, content rights, and appeal paths.
- Listing edits after buyer interest should keep a reviewable trail for support and owner review.
Content Rights
- Sellers should agree that listing photos, item proof, descriptions, certificates, and packing evidence can be displayed where needed for the marketplace flow.
- Rights reports should have a clear notice path, seller response path, and reinstatement path.
- Order and support proof should remain available where needed for reports, appeals, records, and customer notices.
Auction Rules Acceptance
- Bidders should see reserve status, bid increment, top bid behavior, instant buy availability, close timing, and winner follow-through expectations.
- Sellers should confirm reserve settings, cancellation limits, closeout rules, and support holds before an auction opens.
- Bid history and closeout events should stay visible on the item page and support surfaces.
Privacy Notice
- The current demo does not ask for card, bank, tax, address, private message, or sensitive identity details.
- Standard hosting may process technical request data needed to deliver and protect the site.
- A launch needs customer notice for account records, messages, support cases, marketing choices, retention, export, deletion, and processor use.
Consent Choices
- Account settings should separate required marketplace notices from optional alerts, saved-search updates, seller messages, marketing choices, and pickup reminders.
- Customers should be able to change optional choices without losing access to order, support, safety, or legal notices.
- Withdrawal paths should explain what remains in records tied to completed orders, reports, seller obligations, or legal retention.
Version History
- Terms should show effective date, owner, affected routes, customer notice, seller notice, support changes, and rollback notes.
- Version history should be readable by operators without exposing private staff notes to customers.
- Major changes should require owner sign-off before checkout, seller onboarding, or auction start flows use the new copy.
Minor and Geography Rules
- Launch rules should define age limits, unsupported regions, local pickup boundaries, restricted shipping destinations, and category limits.
- Checkout and selling screens should block unsupported combinations before a customer reaches a commitment step.
- Support should have clear language for blocked orders, cancelled bids, hub refusal, and seller account limits.
Launch Approval
- Counsel and owner approval should confirm buyer terms, seller terms, auction rules, privacy notice, optional consent choices, version history, and support ownership.
- Approval should connect the visible pages, checkout review, seller onboarding, account preferences, policy pack, and operator evidence.
- Any provider change should trigger review of customer notices, seller notices, retention rules, and rollback controls.
Bids Center
Bid states, top bid controls, reserve status, retraction review, and winner follow-through.
Checkout Review
Cart items, handoff choices, fees, buyer acknowledgement, and report windows.
Seller Onboarding
Seller commitments, listing quality, records, handoff terms, and support cues.
Policy Pack
Buyer, seller, auction, privacy, fee, support, and approval ownership.
Content Rights
Seller media rights, item proof boundaries, rights reports, takedown review, and reinstatement.
Bid Integrity
Bid rules, retraction reasons, reserve-change limits, closeout holds, and seller cancellations.
Privacy & Data
Data boundary, retention, deletion, staff access, and processor review.
Account Preferences
Notification choices, saved handoff settings, privacy controls, and safety cues.
Service Activation
Checkout, identity, notifications, media evidence, carriers, and launch guardrails.
International Shipping
Country limits, customs notices, duty responsibility, return limits, and customer acknowledgements.
Localization Preferences
Translated policy versions, regional notices, fallback rules, and approval records.
Launch Decision
Approval scope, blockers, rollback controls, policy review, and evidence.
Owner Handoff
Evidence bundle, acceptance checks, service gaps, and ownership boundaries.
Current demo state
Terms are represented as a review surface.
The static demo shows the customer-facing terms and consent model without collecting personal information, account registrations, payment details, addresses, or legally binding acceptances.
Future platform state
Launch needs accepted versions and records.
A live marketplace needs versioned terms, acceptance records, optional consent choices, withdrawal handling, customer notices, seller notices, support ownership, and owner approval before checkout or selling is activated.