Puffify Merchant Agreement

This document is a working draft for attorney and business review. It is not yet effective, does not create a binding agreement, and does not activate ordering, payments, delivery, age-verification, or any other commerce capability.

The existing Puffify Merchant Terms of Service and Privacy Policy remain operative. This draft does not amend, replace, or supersede either document. If approved later, final language, precedence, consent, versioning, and effective-date requirements must be confirmed before use.

Nothing in this draft announces or implies approval, sponsorship, endorsement, or operational readiness by Stripe, BlueCheck, Uber, or any other payment, identity, delivery, or technology provider. No new fee, commission, subscription, penalty, or charge is created by this draft.

A person applying for or administering a merchant account must be legally authorized to act for the identified business. The merchant must provide accurate, current, and complete information and promptly correct material inaccuracies.

The merchant remains responsible for maintaining every license, permit, registration, tax authorization, and other approval required for its locations, products, advertising, and operations. Puffify review or account access is not a substitute for a merchant's own legal review.

Merchants are independent retailers. Puffify provides software and discovery tools; it does not control a merchant's licensed retail operations, staffing, procurement, inventory, product safety, or compliance decisions.

Before live commerce is enabled, counsel and the business must confirm the seller-of-record and merchant-of-record structure, responsibility for tax collection, customer contracting, receipts, fulfillment, refunds, chargebacks, and any payment-provider allocation of responsibility. This draft makes no final determination on those matters.

A product or store may be visible for discovery without being eligible for a transaction. Transaction eligibility, if introduced, would require a separate current determination based on the merchant, product, customer, destination, payment method, and applicable provider and legal restrictions.

Delivery eligibility is a third, independent determination. A visible listing or transaction-eligible item is not necessarily eligible for delivery. Puffify may preserve or tighten any existing control, and no merchant may treat catalog inclusion, a published storefront, or an external delivery link as approval for sales or delivery.

The merchant is responsible for reviewing product names, variants, strengths, sizes, images, warnings, availability, and other information before using or publishing it. Automated matching and AI-assisted suggestions may be incomplete or wrong and always require merchant review.

Inclusion in Puffify's catalog does not mean a product is lawful, FDA-authorized, approved for sale, eligible for payment processing, safe, authentic, or deliverable. Merchants must not use catalog presence as a regulatory or legal claim.

The merchant must protect account credentials, assign staff only the access needed for their work, remove access when it is no longer authorized, and promptly report suspected compromise. Accounts and access may not be shared to evade review, restrictions, or enforcement.

The current operative Merchant Terms of Service govern the one-time $297 onboarding fee: it is refunded if Puffify rejects the application and otherwise becomes nonrefundable once setup work begins, except where applicable law requires otherwise. This draft does not change that rule.

No commission, recurring subscription, payout schedule, transaction fee, delivery charge, cancellation fee, or other future commerce term is established here. Any future payment or ordering service must be supported by separately approved terms and advance disclosure before it is used.

The merchant must respond truthfully and reasonably to customer complaints, preserve relevant records, and cooperate with lawful investigations, safety notices, recalls, refund reviews, and provider disputes. Responsibility for future customer refunds and fulfillment must be confirmed in final commerce terms before launch.

A merchant may not describe an authorization hold as a completed charge or a released hold as a refund. No outcome or processing time may be promised unless supported by the applicable payment method and approved policy.

Merchants must use customer and account information only for authorized purposes, follow the Privacy Policy, apply reasonable safeguards, and honor applicable consent, opt-out, and communication requirements. Access to data or a marketing tool does not establish that consent exists.

Sensitive identity, payment, or age-verification material must not be requested through ordinary email or placed in ordinary logs. Only approved secure channels may be used when a lawful need and retention rule have been confirmed.

A merchant must not misclassify products, disguise its business model, split or reroute transactions, use another account, or direct customers through a different flow to evade law, platform controls, payment restrictions, age checks, product restrictions, or provider rules.

Puffify may request corrections or additional information and may restrict access or visibility while reviewing safety, accuracy, eligibility, security, or compliance concerns. Suspension is a temporary unavailable state. Removal is a distinct state used when a store is taken out of public and operational use while records are preserved.

A lifted suspension restores only the publication state retained by the existing lifecycle controls. Restoring a removed merchant does not republish the storefront; separate authorized review and republishing are required. Subscription or provider cancellation, if any exists in the future, is a separate action and is not automatic.

Questions about this draft may be sent to info@puffify.ai. Do not email passwords, full payment-card information, government-ID images, or other sensitive credentials.

Final dispute, governing-law, liability, indemnity, and precedence language must be reviewed against the operative Terms; this draft intentionally does not create competing provisions.