Terms of service

1. Operator and status of this draft

roavmarket is a proposed marketplace for digital assets and commissioned work for Roblox aviation. The intended operator is [LEGAL ENTITY], trading as [TRADING NAME], registered in [COUNTRY / STATE], with registration number [NUMBER] and address [REGISTERED ADDRESS]. Blackvalk Ltd and White Sparkle LLC are candidates, not confirmed operators. Contact: [SUPPORT CONTACT]; legal notices: [LEGAL CONTACT].

This document is a working draft dated 25 September 2026, not operative launch terms. The current website is a visual prototype: accounts, orders, commission proposals, advertisements, and payouts are simulated. No real sale, license grant, employment arrangement, or payment results from using the demo. The proposed service rules below require legal and operational approval before publication.

2. Eligibility and accounts

The intended seller policy permits adults and minors with the assistance of a parent or legal guardian. A minor must not independently accept obligations they lack capacity to undertake. [DECISION REQUIRED: minimum buyer and seller ages, supported countries, guardian verification, the guardian's contracting role, and responsibility for the payout account.] A production account must use accurate details, and anyone acting for an airline, group, or business must have authority to do so. Account sharing, impersonation, and attempts to evade a suspension are prohibited. Keep sign-in methods secure and report suspected misuse through [SUPPORT CONTACT].

Seller verification and payout eligibility will be separate from ordinary browsing or account access. Guardian involvement does not override a payment provider's eligibility rules. Required checks and the process for incomplete verification must be disclosed before a seller accepts paid work.

3. Marketplace role and order information

A production listing must identify the seller, price and currency, applicable taxes and fees, supplied files, supported versions, dependencies, license, delivery method, and any support or update commitment. The contracting seller and business responsible for collecting payment must be identified before checkout. [DECISION REQUIRED: seller-of-record, merchant-of-record, tax collection, and responsibility for refunds and disputes.]

roavmarket is independent of Roblox Corporation. A listing is not an endorsement by Roblox, an aircraft manufacturer, or a real airline. Sellers must have permission to use third-party branding, models, textures, code, and other protected material.

4. Licenses, uploads, and optional previews

The listing must disclose the license before purchase. The prototype illustrates use within the buyer's own projects, with no standalone redistribution or resale; this is an example, not a finalized platform license. [DECISION REQUIRED: group use, team access, commercial use, modifications, redistribution in compiled experiences, and vendor-specific exceptions.] Ownership transfers only if a separate written agreement expressly provides for it.

A seller retains rights in their uploads and must grant only the permissions needed for hosting, formatting, displaying, and delivering them for the selected service. Interactive model previews are opt-in. Sellers may instead supply a 360-degree image series or a standard gallery. A preview should accurately represent the deliverable and clearly identify omissions, concept art, or separately sold items.

Before enabling an interactive preview, the seller must be told what model data is sent to visitors' browsers and what protection is actually available. Browser display cannot be promised to prevent all copying or reconstruction. A private delivery file must not become public merely because a seller enables screenshots.

5. Delivery and linked hubs

Vendors may choose delivery through the roavmarket library or an approved external hub. The destination, necessary account links, and any additional terms must be shown before purchase. An external delivery link alone is not proof that the buyer received access. The production service must record delivery status and provide a support path for missing files or failed whitelisting.

Any approved connection to Enviglo, Parcel, Vendr, or another service must use the permissions needed for the buyer's purchase. Those names describe proposed integrations, not partnerships or working connections. [DECISION REQUIRED: availability checks, redelivery, version retention, access after a hub closes, and how account unlinking affects existing purchases.] Buyers should retain authorized backups where their license permits.

6. Prices, payments, and seller settlement

The prototype uses USD customer prices and illustrates a 5% commission fee deducted from the work payment. This does not establish a product-sale fee or include processing, payout, currency conversion, or tax costs. A production checkout must show the payable total, and a seller statement must explain each deduction and adjustment.

Stripe checkout and Connect onboarding are planned. Bank and debit-card payout availability depends on the approved setup and recipient eligibility. Robux group payouts and crypto settlement are exploratory concepts, not promised payment services. No conversion rate, custody arrangement, payout time, or supported territory has been agreed.

A production seller agreement must specify payment-provider terms, verification, settlement schedules, reserve or delay grounds, chargeback evidence, refunds, transfer reversals, negative balances, appeals, and account closure. Neither a payout selector nor a delayed transfer should be described as a regulated escrow service without a confirmed legal and provider basis.

7. Commissions

Before work begins, the parties must agree on the scope, deliverables, file formats, milestones, deadlines, dependencies, revisions, acceptance criteria, license or ownership transfer, cancellation, and support. A listing or proposal alone does not settle these matters. Material changes should be recorded and accepted by both parties.

The prototype illustrates two arrangements: payment after delivery, where no funds have been reserved, and funding before work, with release after approval. The latter requires an approved funds flow, maximum holding periods, and a process for rejected or disputed delivery. [DECISION REQUIRED: inspection period, nonresponse, partial completion, refunds, and release authority.] A displayed balance is not a guarantee of protected or immediately withdrawable funds.

8. Refunds, complaints, and consumer rights

A buyer should be able to report non-delivery, material misdescription, defective files, licensing issues, or unauthorized charges using [SUPPORT PROCESS]. Sellers must cooperate with an investigation and provide the agreed remedy where required. A production refund policy must identify who decides, how to submit evidence, expected response times, and the applicable payment route.

Nothing in the final terms should exclude rights or remedies that cannot lawfully be excluded. A digital download is not a blanket reason to deny all refunds. Where immediate digital supply affects a withdrawal or cancellation right, the applicable disclosure and consent process must be implemented before delivery. [COUNTRY-SPECIFIC REVIEW REQUIRED.] Do not revoke a license or claw back unrelated earnings automatically merely because a complaint was filed.

9. Advertising and acceptable use

Sponsored placements must be labeled. Advertisers must have rights to their creative and accurately describe the flight, community, destination link, and schedule. No placement guarantees attendance, sales, or impressions unless a separate agreement expressly defines that commitment. [DECISION REQUIRED: pricing, approval, cancellations, refunds, and synchronization with an external flight service.]

Stolen assets, malware, concealed backdoors, credential theft, fraudulent sales, unlawful content, harassment, and manipulative reviews are prohibited. Sellers must disclose code behavior and dependencies that materially affect the buyer. Reviews and badges must reflect an actual, defined verification process rather than imply an unperformed security audit.

10. Reports, enforcement, and account closure

Report suspected infringement to [IP CONTACT] with the listing location, identification of the protected work, your authority to report it, and a way to contact you. An applicable notice, counter-notice, repeat-infringer, and appeal process must be adopted before launch; no statutory safe-harbor status is claimed in this draft.

The service may need to limit content or accounts to address misuse, security risks, provider requirements, or law. The production process should provide a reason and an appeal route unless doing so is prohibited or would compromise an investigation. Closure must address outstanding work, eligible refunds, seller funds, buyer access, and records that must be retained.

11. Availability, liability, and governing law

Third-party changes and outages may affect the service. The production agreement must define any availability or support commitments and a reasonable exit process for paid services. No guarantee of uninterrupted operation is made by the prototype.

[LAWYER TO COMPLETE: governing law and venue after entity and customer markets are confirmed; any enforceable liability cap; non-excludable liabilities; appropriately limited business indemnities; dispute resolution; assignment; severability; and material-change notice.] No arbitration waiver, foreign jurisdiction, arbitrary monetary cap, or blanket consumer-rights exclusion has been borrowed from another platform.