Terms of use

BuyAve is a marketplace where people list goods for local pickup or domestic shipping, and buy them at a fixed price, by accepted offer, or at auction.

BuyAve is not the seller of any item. The seller is; BuyAve operates the marketplace and handles the payment between you.

Pending — This is the single decision the rest of the document hangs from — who the buyer’s contract is with, who owes a refund, who answers a chargeback, who reports the sale for tax. It is recorded internally as a founder’s provisional direction and is counsel’s to confirm. If it changes, this document changes throughout.

Sign-in is handled by an identity provider; BuyAve never sees your password. You can sign out of every device at once, and you can close your account at any time — see the privacy policy for what closing it erases and what it keeps.

BuyAve is for people aged 18 and older, for both buying and selling. Parent-authorized minor accounts are not permitted. Anyone acting for a business must be an adult representative authorized to bind it.

Before buying, bidding, publishing listings or sending messages, members must declare their eligibility and accept the displayed Terms version. This is self-attestation, not verified age. Credible age concerns restrict transaction access pending a stronger eligibility review. Payment-provider onboarding does not replace BuyAve’s adult-only rule.

Pending — These Terms remain a draft. Sandbox acceptance is recorded separately from approval for a public launch. Seller identity checks for live paid sales and payouts remain a separate launch requirement.

Pending — Grounds for suspending or terminating an account, and whether a suspended seller still receives money already owed. The two are separable in the software.

A seller chooses what to sell, the starting price, an optional hidden reserve, an optional Buy Now price, and how long an auction runs. Everything else — fees, increments, the soft-close window, payout timing — is marketplace policy and is not a seller option.

A seller is responsible for the accuracy of their listing and for their right to sell the item. BuyAve can suspend or reinstate a listing with a stated reason, recorded in an append-only log, and the seller is told. Suspending a listing cannot cancel an existing order or reverse a payment.

Pending — A prohibited and restricted items list. None exists. It needs to cover at least weapons, controlled substances, recalled goods, counterfeits, live animals and anything requiring a licence — and to say for each whether it is blocked at listing or removed on report, because those are different pieces of engineering.

Pending — What a seller must verify before listing, before transacting, and before being paid. These are three separate permissions, and federal marketplace rules set a floor under the answer once a seller passes a volume threshold.

Fixed price — you commit at the listed price. Offers — you propose an amount and the seller accepts, declines or counters; a declined offer charges nothing.

Auctions — a bid is a binding maximum and cannot be withdrawn. The full mechanics, including increments, the soft-close extension and the limits on very large bids, are set out in Auction rules, which forms part of these terms.

Pending — Whether an accepted offer or a winning bid forms a binding contract of sale between buyer and seller, and what remedy each has if the other does not perform.

You pay through BuyAve. The seller is not paid at checkout. Payment is released only after the handover is evidenced — a pickup code redeemed in person, or a carrier’s delivery scan. Neither side can assert a handover that did not happen, and BuyAve has no control that marks an order paid, delivered or complete by hand.

After that, payment is released following a holding period shown on the order.

Pending — The buyer-protection promise itself. What is described above is what the software does; what BuyAve undertakes — whether there is a guarantee, what it covers, the claim window, and what a buyer must do to make a claim — is not decided.

Pending — Mandated payout holds, if any, as a floor under the current policy.

Pending — No fee schedule can be stated. The fee configuration is explicitly draft and is labelled as such wherever it is shown. A separate question needs answering alongside it: a mandatory buyer fee that appears only at checkout may have to be included in the displayed price under some state laws.

Pending — Which states make BuyAve, rather than the seller, the party that owes sales tax, who registers and who files. Nothing is calculated or collected today.

BuyAve can issue a refund without the seller’s agreement, under a written policy. Every refund writes reversing ledger entries rather than editing anything.

Pending — Who bears the loss on a refund or a lost chargeback — BuyAve, the seller, or split. The dispute model already computes a seller’s share and works with either answer.

Pending — Cancellation rights before handover, the seller’s right to cancel, and whether returns exist at all — who pays return shipping, and the window. Federal rules on shipping deadlines also apply and are not reflected anywhere yet.

Pending — What a seller owes BuyAve after a refund leaves them negative, and what may be done to recover it.

Messages between parties are stored and are visible to operators when reported. Reviews, reports and blocking exist.

Pending — The licence a seller grants BuyAve over listing photographs and text; acceptable-use and harassment rules; and the takedown and counter-notice process for intellectual-property complaints, which has its own registration requirement.

Pending — Disclaimer of warranties, limitation of liability and indemnity. For proportionality: there is no uptime commitment anywhere in the system and no alerting configured, so any availability language should be written accordingly.

Pending — Governing law, venue, and whether arbitration and a class-action waiver fit this business. Nothing in the product bears on these.

Pending — Notice period and whether continued use is acceptance. Marketplace policy is already versioned per transaction and never applied retroactively, so a version-forward model matches how the system behaves.