Terms of Service

These Terms of Service (“Terms”) govern your access to and use of BountySmith, a platform operated by BountySmith LLC, a California limited liability company (“BountySmith,” “we,” “us,” or “our”). By creating an account you agree to these Terms and the Privacy Policy. The version you accept is recorded with your account at signup. BountySmith is not affiliated with Roblox Corporation.

You must be at least 18 years old to use BountySmith, and you confirm this when you sign up. The platform involves paid work, payouts, disputes, and contractual marketplace behavior. It is not for minors.

• Provide accurate information and keep it up to date.
• Keep your password confidential. You are responsible for activity on your account.
• Tell us promptly at support@bountysmith.com if you suspect unauthorized access.

BountySmith has two participant roles. Creators offer Roblox asset work: VFX, modeling, animation, UI, icon/logo, sound, and building (no programming or scripting). Studios post bounties for that work. Both go through an admin verification review before they can fully participate.

BountySmith LLC operates the platform. Studios and creators contract with each other for commissioned work through it: the studio's brief, the creator's accepted application, and the funded bounty form that arrangement between the two of them. BountySmith does not create, own, or deliver the commissioned work, and it is not a party to the commission beyond providing the platform, the funded-bounty workflow, and the dispute review described in these Terms.

Creators are independent providers. They choose which bounties to apply for, how to do the work, and when to work. They are not employees, agents, or representatives of BountySmith LLC, and nothing in these Terms creates an employment, partnership, or joint-venture relationship between a creator, a studio, and BountySmith.

Verification means an admin reviewed a creator’s portfolio evidence or a studio’s ownership proof and found it credible. It is not a guarantee of work quality, identity, or the outcome of any bounty. Do your own diligence before working with anyone.

• Deliver original work you have the rights to sell.
• Disclose any third-party assets, samples, or licensed components used in your work, along with their licenses.
• Deliver what the bounty brief describes, as agreed.
• Represent your portfolio honestly. It must be your own work.

• Fund a bounty before expecting work. Creators only start after funding.
• Write accurate, complete briefs.
• Review delivered work in good faith: give real feedback, use revisions for fixable issues, and don’t hold approval hostage.

The money flow uses funded bounties, held payments, and platform-managed release: a studio funds the bounty up front, the payment is held while work happens, and it is released to the creator when the studio approves (or a dispute resolves that way).

• Live payments. Pilot payments run on Stripe Connect and are live: funding a bounty is a real charge to the studio, and release is a real payout to the creator's connected Stripe account. Stripe handles card and bank details; BountySmith never sees them.
• Not a true escrow service. Stripe does not provide escrow accounts. The funded-bounty workflow is escrow-like, not escrow: the held payment sits on BountySmith's Stripe platform balance under platform management until it is released or refunded, and no licensed escrow or trust account is involved.
• Fees. A platform fee (currently 10%) is charged to the studio on top of the creator payout, and is earned only when payment is released after approval. If a bounty is refunded before release, the platform fee is returned but the payment-processing fee is non-refundable: the refund is what the studio paid minus that processing fee.

The money story (funding, refunds, and fees) is on the Payments & Refunds policy, and the dispute mechanics are on the Disputes page.

Creators deliver through the vault. Final files stay locked, with no viewing or downloading, until the studio approves and payment is released. Previews are meant for evaluation only; like anything shown in a browser, a preview may be technically saveable, and the vault is not a substitute for acting in good faith.

• Revisions are normal feedback. Payment stays held and work continues.
• Disputes can be opened only while the payment is funded and held, after work is delivered, and before approval. An admin resolves them.
• Cancellation stops at delivery. A studio can cancel a funded bounty, and be refunded minus the non-refundable processing fee, only until a creator delivers work. Once work is delivered, cancellation is no longer available: the studio approves, requests revisions, or opens a dispute.
• Approval is final. Releasing payment unlocks the finals and cannot be clawed back.
• Auto-approval. A delivered submission that the studio takes no action on auto-approves after 7 days.

• Ownership before release. Everything a creator makes for a bounty stays the creator's until payment is released.
• Previews and progress updates. These are shown to the studio for evaluation only. The studio gets no rights in them and may not use saved copies. For image, video, and audio work the preview shown may be the submitted file itself, which is why this rule matters.
• Cancellation, refund, or a dispute the studio wins. Nothing transfers, and the final files stay locked.
• Transfer on release. When payment is released, whether by approval, by auto-approval, or by a dispute resolved in the creator's favor, the creator assigns to the studio the rights the bounty brief describes in the delivered final files.
• When the brief is silent. The studio receives ownership of the delivered final files, including the right to use, modify, and distribute them in its Roblox experiences and related promotion.
• Pre-existing components. Creators keep their pre-existing tools, techniques, and generic components. They grant the studio a license to use those as part of the delivered files, and they identify them in the submission notes, just as they disclose third-party components.
• Portfolio. After release, a creator may show the delivered work in their portfolio, on BountySmith and elsewhere, to demonstrate their skills, but may not sell, license, or reuse it. If the brief states the work is confidential, the creator may show it only after the studio has made it public. A studio that needs more than this uses its own agreement with the creator; BountySmith does not provide or enforce NDAs.
• Third-party components. The creator is responsible for having the rights to everything in the delivered work and for disclosing any third-party components and their licenses.
• Studio materials and Roblox. The studio owns its brief, reference files, and other materials it provides, and grants the creator a license to use them only to complete the commission. How delivered work is used on Roblox, and compliance with Roblox's terms, is the studio's responsibility.
• The platform. BountySmith LLC owns BountySmith itself: the software, the brand, and the platform content. BountySmith does not claim ownership of either side's work. By uploading content, you grant BountySmith a limited, non-exclusive license to host, reproduce, and display it only as needed to operate the platform (including generating previews and showing your portfolio publicly) until you delete it or your account closes.

The Acceptable Use Policy is part of these Terms. Breaking it can cost you content, access, or your account.

Reviews must reflect a real working experience, honestly told. No fake reviews, review trading, retaliation reviews, or pressuring anyone to change a review.

Any logged-in user can report a bounty, user, or file for review. We may remove content and limit, suspend, or terminate accounts that violate these Terms or the Acceptable Use Policy, and we may decline or revoke verification. These are reversible operator decisions. You can reach us on the support page. During the pilot we may also reset or wipe demo data.

BountySmith is pilot software provided “as is”, without warranties of any kind. We do not guarantee uptime, data durability, error-free operation, or that any bounty will end well.

To the fullest extent permitted by law, BountySmith LLC and its members, managers, and service providers are not liable for indirect, incidental, special, consequential, or punitive damages. The same applies to lost profits, lost revenue, lost data, and the cost of substitute services, whatever the cause, arising out of or relating to BountySmith or these Terms. To the same extent, our total liability for all claims relating to BountySmith in any twelve-month period is limited to the greater of the platform fees you paid us during that period and one hundred US dollars. Nothing in this section limits liability that cannot be limited under applicable law.

You agree to indemnify and hold harmless BountySmith LLC and its members, managers, and service providers from third-party claims, damages, and reasonable legal costs that arise from your content, your commissioned work, your breach of these Terms or the Acceptable Use Policy, or your violation of law or of someone else's rights. We may choose to control the defense of such a claim at our own expense, and you agree to cooperate with it.

These Terms are governed by the laws of the State of California, without regard to its conflict-of-laws rules.

We may update these Terms. When we do, the “last updated” date at the top changes, and the version you accept is recorded with your account. After a material change, we ask you to accept the updated Terms before you next post, publish, fund, cancel, or dispute a bounty, apply to one or accept an applicant, or submit progress or final work or approve it.

Questions about these Terms, and legal notices to BountySmith LLC: support@bountysmith.com. See the contact page.