Terms of Service

Effective date: 30 August 2026 Version: 2.0

1. Who these Terms are with

1.1 Us. These Terms are between you and Misschevious Development, a sole proprietorship established in the Commonwealth of Virginia, USA ("we", "us", "our"). We trade online only and do not operate premises open to the public. Our contact address for all purposes is support@misscheviousmarketplace.com, and section 38 sets out how notices work.

We also trade as Misschevious Marketplace. Both names are the same legal person. A Resource, listing, invoice or document issued under either name is issued by us and is governed by these Terms.

1.2 You. "You" means the person accepting these Terms, and where you act for a community, business or other organisation, that organisation as well.

1.3 What we do. We design, build and licence software resources for FiveM servers. We sell ready-made resources through a Tebex storefront, and we take custom commissions billed directly.

1.4 Language. These Terms are written in English. Any translation is provided for convenience. The English text governs.

2. Definitions

Defined terms are capitalised throughout and carry the meaning given here.

3. Acceptance and formation

3.1 How you accept. You accept these Terms by doing any of the following:

• visiting or using our website;
• creating an Account or signing in;
• joining or remaining in the Discord Server;
• using the Bot or any of its commands;
• purchasing a Resource through the Store;
• downloading or installing a Resource;
• opening a Custom Request Ticket or starting a commission enquiry;
• paying a Commission invoice.

3.2 Clickwrap. Where we present these Terms with a checkbox or equivalent control, your acceptance is recorded against your Account with the version and the time. That record is the primary evidence of acceptance.

3.3 If you do not agree. Do not use the Services, do not purchase, and leave the Discord Server.

3.4 Authority. If you accept these Terms for a Community, business or organisation, you confirm you are authorised to bind it. You and that organisation are jointly responsible for compliance.

3.5 Terms travel with the files. A copy of sections 7 to 13 is shipped inside each Resource as a licence file. Those sections continue to apply to you whether or not you remain in the Discord Server and whether or not you retain access to your Account.

3.6 Third-party terms you also accept. Using the Services means you also deal with third parties on their own terms. You are responsible for complying with:

• Tebex terms of service, for the purchase itself;
• Discord Terms of Service and Community Guidelines, for the Discord Server and the Bot;
• Cfx.re Creator Platform Licence and platform rules, for running a FiveM server;
• your hosting provider's terms.

We are not a party to those agreements and do not control those platforms.

4. Order of precedence

4.1 Where documents conflict, the following order applies, highest first:

1. Mandatory law that cannot be excluded, including your non-waivable rights as a consumer.
2. Tebex checkout terms, for the contract of sale Tebex makes with you and anything Tebex controls: payment, tax, and the money in a refund or chargeback.
3. A signed Engagement Summary and its Design Document, for the Commission it governs.
4. These Terms.
5. Documentation, for the technical scope of a Resource.

4.2 Within a Commission, the Design Document governs scope and acceptance; these Terms and the Engagement Summary govern everything else. A Design Document cannot alter payment, ownership, liability or dispute terms.

4.3 Nothing in these Terms limits or replaces the terms on which Tebex sells to you.

5. Eligibility

5.1 You must be capable of entering a binding contract where you live.

5.2 Age. You must be 18 or over to join the Discord Server, use the Bot, hold an Account, purchase a Resource, hold a licence, or commission work. The Services are not directed at children, and we do not knowingly collect personal data from anyone under 16.

5.3 We may refuse or withdraw access where we reasonably believe you do not meet section 5.1 or 5.2.

5.4 Screening. We may decline to sell to, or work with, any person or Community we reasonably believe is running leaked, pirated or unlicensed resources, or has previously breached these Terms. That check happens at enquiry.

6. Store purchases, delivery, price and tax

6.1 Tebex is the merchant of record. All Catalog purchases go through the Store. Tebex Limited is the seller for the transaction. Its terms and its dispute process apply to the payment, and a Tebex decision governs the money.

6.2 We do not take card details. Payment happens at Tebex. We never collect card or payment details in Discord, in a Ticket, or by direct message. Anyone asking you for card details through Discord is not us. Report it.

6.3 Delivery - Catalog. A Resource is delivered, and supply begins, at the earliest of:

• download access becoming available on your Tebex account page; or
• the Resource being granted to your Cfx.re account through Keymaster or Asset Escrow.

Files come from Tebex, never as a Discord attachment. Your Discord roles unlock customer channels and support. They are not the product, and losing Discord access does not revoke your licence.

6.4 Cfx.re binding. Where a Resource is escrowed, Cfx.re may bind it to the Cfx.re account used at checkout. Buy with the account you intend to run it on. Section 13.4 covers what we can and cannot do about a wrong-account purchase.

6.5 Price and tax. Prices are those shown at checkout and are configured through Tebex, which determines the tax treatment and the currency. Prices may change at any time. A price change never affects a purchase already made. We give no price guarantee beyond the price displayed at checkout.

6.6 Your account and links are yours alone. Your Tebex account, order history and download links are personal to you. Sharing them is redistribution under section 10.

7. Licence grant - Catalog

7.1 Grant. On payment in full, we grant you a perpetual, worldwide, non-exclusive, non-transferable licence to install, run and modify the Resource on one Licensed Server, in accordance with these Terms.

7.2 Term. The licence does not expire. It survives you leaving the Discord Server, us discontinuing the Resource, and us ceasing to trade. It ends only as set out at section 12.4 or section 34.

7.3 Reservation of rights. We retain ownership and all intellectual property rights in the Resource. You are licensed to use it. You have not bought the copyright. All rights not expressly granted are reserved.

7.4 Supported Environment. Each Resource ships with Documentation stating the frameworks, versions and third-party resources it supports, its installation steps, and its known behaviour. That Documentation forms part of these Terms for that Resource. It defines:

• what the Resource is warranted to do, and on what;
• steps you must follow, and warnings you must observe;
• behaviour the Documentation records as expected, which is not a Defect.

Where the Documentation and a Store listing conflict, the Documentation governs technical scope.

7.5 Third-party components. A Resource may depend on or include third-party frameworks, libraries or assets. Those keep their own licences, which govern those components and are identified in the Documentation. Nothing here grants you rights in them beyond what their licences give.

7.6 Trade marks. "Misschevious", "Misschevious Marketplace", "Misschevious Development", our logos and our branding are ours. You acquire no rights in them. You may state factually that your Community runs our Resources. You may not present yourself as us, as endorsed by us, or as the author of a Resource.

8. What one purchase covers

8.1 One purchase, one Community. One purchase licences the Resource for one Community.

8.2 A Community, not a machine. A Community is one server community, under one identity, with one player base. Running it across several machines, instances, shards or addresses for capacity, redundancy or region does not make it more than one Community, and does not need more than one licence.

8.3 A second Community needs its own purchase. Two Communities are separate where they have separate identities and separate player bases, whoever owns them. Sister cities, spin-offs, second cities and "network" servers with their own identity and player base are separate Communities and each needs its own licence, even under common ownership and common branding.

8.4 Development and test servers you personally own do not count. Use them freely, for development, staging and testing. They must not be open to the public and must not operate as a Community.

8.5 Rented servers. A server you rent counts as yours if you control it. A server you contribute to but do not control does not.

8.6 Rebrand, merge and sale.

• Rebranding a Community does not need a new licence. Tell us so we can update our records.
• Merging two Communities into one leaves one Community, and one licence is enough afterwards. It does not entitle you to a refund of the other.
• Splitting one Community into two creates a second Community, which needs its own licence.
• Selling your Community is covered at section 11.

8.7 Where a licence key is issued. For Commission work and any Resource we licence by key, the key and its registered server addresses are the record of the Licensed Server. You may register up to the number of addresses stated for that licence, and change them through us or through your Account.

8.8 Licence checks will not break your server. Where a Resource checks a licence, it is built to keep running through a failed or unreachable check for a grace period. A problem at our end must not take your Community down. This is a design commitment, not a warranty of uninterrupted operation.

9. What you may do

9.1 Run it. Install and run the Resource on your Licensed Server, including commercially - donations, subscriptions, priority queues, whatever your Community does, subject to section 29.

9.2 Modify it, for your own Licensed Server. You may edit, fix, extend and adapt the Resource for your own use. The files you may edit are the files that Resource's Documentation identifies as configurable or open. Some Resources ship fully open; others are escrowed, with named configuration files open and the remainder encrypted. The Documentation for each Resource states which. Modification is encouraged within that boundary.

If a modification breaks something, say so when you open a Ticket, so we are not debugging a version we have never seen.

9.3 Contractors. You may give a developer you engage access to the Resource, for work on your Licensed Server, provided:

• they are told the Resource is licensed to you and is not theirs to keep;
• they use it only for your Licensed Server;
• they delete every copy when the work ends; and
• they do not reuse, publish or redistribute it or anything derived from it.

You remain responsible for what they do with it. A leak by your contractor is treated as a leak by you, subject to section 12.

9.4 Backups. Keep your own backups. Copies made for backup are permitted and do not count as additional installations.

10. What you may not do

You may not:

10.1 redistribute, resell, sublicense, publish, lend, rent, or upload the Resource anywhere, modified or unmodified, in whole or in part;

10.2 share your Account, Tebex account, order history, download links or licence keys;

10.3 run the Resource on more Communities than you hold licences for;

10.4 remove, bypass, defeat, or attempt to defeat Escrow, licence checks, authentication or any other technical protection, or assist anyone doing so;

10.5 decompile, disassemble or reverse engineer any encrypted or escrowed part of a Resource, except to the extent that right cannot lawfully be excluded;

10.6 remove or alter copyright notices, licence files or attribution;

10.7 claim authorship of a Resource, or present it as your own work;

10.8 request, offer, link to, or knowingly use leaked or pirated resources, ours or anyone else's; or

10.9 use a Resource to build a competing product for distribution.

11. Transfer

11.1 Catalog licences are non-transferable, with one exception.

11.2 One permitted transfer. If you sell your Community as a going concern, the licence may be assigned once, in writing, to the buyer, provided:

• you notify us in writing before or at completion, through a Ticket or to support@misscheviousmarketplace.com;
• you identify the Resource, the Community and the buyer;
• the buyer accepts these Terms in their own name; and
• you retain no copy and stop all use.

11.3 We acknowledge a valid transfer in writing and move the Discord roles. We do not unreasonably withhold or delay acknowledgement. What transfers is the licence only. It does not transfer your Account, your Tebex order history, or any Commission relationship.

11.4 A transfer not made under section 11.2 is void, and the licence is not transferred.

12. Audit, investigation and enforcement

12.1 Records. We keep records of purchases, licence keys, registered server addresses and licence checks. Section 8.7 explains what those are for.

12.2 Investigation. Where we have reasonable grounds to believe a Resource has been leaked, redistributed, or run beyond the licences held, we may:

• ask you for information reasonably needed to establish the position;
• suspend the licence and access to customer channels while we investigate; and
• suspend a licence key or deregister a server address.

12.3 Proportionality and reinstatement. Suspension under section 12.2 is a holding step, not a finding. We will tell you what we believe and why, in enough detail for you to answer, unless doing so would prejudice an investigation or breach someone else's rights. If the concern is not made out, we reinstate the licence and any roles promptly and at no cost to you. We will not suspend on an anonymous or unevidenced allegation alone.

12.4 Termination for breach. Your licence terminates immediately if you:

• redistribute, resell, leak, publish or share the Resource, modified or unmodified;
• circumvent or attempt to circumvent Escrow, licence checks or authentication; or
• run the Resource on more Communities than you hold licences for.

On termination you must stop using the Resource and remove it from every server.

12.5 Preserving evidence. Where a leak is alleged, both of us should preserve what is relevant - logs, files, messages, distribution records - while it is resolved.

12.6 Injunctive relief. Redistribution causes harm that money does not repair, because a leaked file cannot be recalled. We may seek an injunction or equivalent relief for a breach of section 10 without needing to post a bond, where the applicable law permits, and without that being our only remedy. Nothing here removes a court's discretion.

12.7 Proportionate consequence. Suspension of licences and revocation of access under this section apply to the breaches listed at section 12.4, to fraud, and to chargebacks under section 16. They do not apply to conduct in the Discord Server, which is dealt with under section 27 and does not affect what you have bought.

13. Updates, discontinuation and platform change

13.1 Updates are free for life. While we maintain a Resource, updates are free. Re-download from your Tebex account page.

13.2 Discontinuation. We may stop maintaining a Resource. If we do, your licence continues and your downloads remain available through Tebex, but new updates stop. We will say so in the Discord Server.

13.3 Platform-forced change. Cfx.re, Rockstar, Tebex and Discord change their rules. If a change makes a Resource or a listing non-compliant, we may withdraw or modify it. Where that materially affects a Resource you have bought, we will fix it, substitute it, or refund that item. That is the remedy, and section 31 caps anything beyond it.

13.4 Wrong-account purchases and lost Cfx.re accounts. Where a Resource is bound to a Cfx.re account, we can only act through the mechanisms Cfx.re provides. If Cfx.re offers a transfer mechanism, we will use it on reasonable request. If it does not, we cannot move the asset, and recovering a lost Cfx.re account is between you and Cfx.re. The same applies where a developer you engaged holds files or an account you no longer control - section 9.3 puts that risk on you.

14. Support

14.1 How to get it. Through a Ticket in the Discord Server. Ticket types are Billing / Purchase, General Support, Installation, Bug Report, Custom Request, and Other. Do not direct-message staff: DMs are not tracked, not logged, and not covered when that person is asleep.

14.2 Response times are targets, not a service level. We aim to respond within 30 to 60 minutes during active hours, and within 24 hours otherwise. We work to those targets and publish them because they are real. They are targets, not a service level, and they are not guarantees. No credit, refund or remedy arises from missing one.

14.3 What we support. A Resource on its Supported Environment, on an unmodified installation. We are not obliged to support a version you have modified, though we will usually try, and we are not obliged to make a Resource work alongside every third-party resource in existence.

14.4 Version mismatches. Framework and dependency version mismatches are the most common cause of installation failure. A version mismatch is not by itself a Defect. Check the Documentation first.

14.5 Helping us help you. Include your server console output, your framework and version, what you already tried, and any edits you made. A Bug Report needs reproduction steps.

15. Refunds - Catalog

15.1 The position. Digital goods are non-refundable once downloaded, except where required by law or where the Resource does not work as advertised.

15.2 We would rather fix it or refund it than leave you stuck. If a Resource is broken, open a Billing / Purchase Ticket. That is the fastest route to either a fix or your money back.

15.3 When you are entitled to a refund. Where:

• the Resource does not work as advertised, on its Supported Environment with an unmodified installation, and we cannot fix it within a reasonable time;
• you were charged twice, or charged in error;
• the Resource was never delivered and we cannot deliver it; or
• your consumer rights require it. See section 15.7.

15.4 Remedy order. Where section 15.3 applies because a Resource does not work as advertised, we will first try to fix it within a reasonable time. If we cannot, you get a refund. You are not required to accept repeated attempts at a fix, and a reasonable time is judged against the fault, not our convenience.

15.5 When you are not entitled to a refund. Where:

• you changed your mind after downloading;
• you bought the wrong Resource, or one you already owned;
• your framework was not supported and the listing said so;
• you wanted a feature that was never listed;
• it conflicts with a third-party resource we never claimed to support, and the conflict cannot reasonably be resolved;
• an installer, framework or third-party tool outside the Resource failed;
• you modified it and the modification broke it;
• you want a refund but wish to keep using it; or
• your Community closed, changed framework, or your plans changed.

15.6 Immediate supply, and the EU/UK cancellation right. Where you are a consumer with a statutory right to cancel a distance purchase, that right normally lasts 14 days. For digital content supplied immediately, the right is lost once supply begins, where you expressly consented to immediate supply and acknowledged losing the right. That consent is captured at Tebex checkout. See Appendix C. If it was not captured, this section does not take your right away.

15.7 Your statutory rights win. Nothing in these Terms removes or reduces rights you have under the law of your own country. Where your statutory rights give you more than this section does, your statutory rights apply.

15.8 How to ask. Open a Billing / Purchase Ticket with your Tebex transaction ID, a description of the problem, and for a fault, your server console output. We respond within 24 hours as a target and aim to resolve within 7 days.

15.9 Tebex processes the money. Refunds are issued through Tebex to your original payment method, usually within 5 to 10 business days. Tebex's terms and dispute process apply, and a Tebex decision may differ from ours. We will always tell you what we decided and why. Where Tebex reaches a different outcome, that outcome governs the money.

15.10 After a refund. Your licence for that Resource ends. You must remove it from your servers. The package role is removed. Your other purchases are unaffected.

16. Chargebacks

16.1 Talk to us first. If something is wrong with a purchase, open a Billing / Purchase Ticket. A chargeback filed without contacting us removes our ability to help, costs both of us, and is slower than a refund.

16.2 Chargeback without notice is a breach. Filing a chargeback without first opening a Ticket and allowing us a reasonable opportunity to resolve it is a breach of these Terms. Where that happens we may suspend your licences and access to customer channels and decline future sales, and we may give the payment processor a record of the purchase, the delivery and the support history.

16.3 What this is, and is not. This is withdrawal of discretionary services and enforcement of the licence. It is not a penalty, and it does not affect your right to dispute a payment with your bank or card issuer. Nothing in this section limits your statutory rights or your rights under Tebex's process.

16.4 Resolution. Where a chargeback is withdrawn or decided in our favour and the underlying issue is resolved, we reinstate access.

17. Commissions - what these Terms govern

17.1 Standing terms. Sections 17 to 25 are the standing terms for Commission work. They apply to every Commission unless the Engagement Summary says otherwise for that job.

17.2 No contract at enquiry. Opening a Custom Request Ticket, discussing a job, receiving a feasibility reply, or receiving a quote does not form a Commission contract. The enquiry stage is free and carries no obligation on either side.

17.3 When a Commission is formed. A Commission is formed only when you sign the Engagement Summary. Electronic signature is valid and sufficient. We accept no deposit and start no work before the signed Engagement Summary is received.

17.4 What "in writing" means. For a Commission, "in writing" means a post in the engagement Ticket, an email to or from support@misscheviousmarketplace.com, or a signed document. Ticket posts are the primary record, because transcripts are archived automatically.

17.5 What the Engagement Summary contains. The parties, your legal status, the tier and scope, the Design Document incorporated by reference and version, the total price and milestone breakdown, the deposit, the confirmed start date and estimated delivery date, the ownership position restated plainly, the Supported Environment, and these Terms incorporated by reference with a version number.

17.6 Amendments. No amendment takes effect unless in writing and agreed by both of us. A post in the engagement Ticket, identified as an amendment and acknowledged by both, is enough.

18. Enquiry and screening

18.1 The free stage. Open a Custom Request Ticket with what you want, your framework and version, your budget range and your deadline. Within 24 to 48 hours you get a straight answer on feasibility, a ballpark tier, and whether it is something we should build at all. No spec, no obligation, no charge.

18.2 What we will not build. Anything built on leaked, pirated or unlicensed resources; direct clones of another creator's paid work; anything breaking Cfx.re, Rockstar, Discord or Tebex terms; cheats, exploits or tooling designed to break other servers; and full server setups or ongoing server administration. If your request lands here we tell you in our first reply - free, before you have paid anything.

18.3 Price bands are guidance. Published tiers and bands tell you which ballpark you are in. They are guidance, not a quote. Every Commission is quoted from its Design Document. A written quote may come back above a published band, and you are free to walk away at that point having paid nothing toward the build.

19. Design Phase

19.1 Paid, and separate. Anything larger than a tweak begins with a paid Design Phase. Design and build are separate purchases.

19.2 What you get. A written Design Document: research, scope, decisions and their consequences, the data model, the interfaces, milestones with their Acceptance Conditions, and an explicit list of what is out of scope.

19.3 The document is yours to keep. It is yours whether or not you proceed. You may take it to another developer. If you do not proceed you keep it and owe nothing further.

19.4 The design fee is earned on delivery. It is a fee for work delivered, not a deposit, and it is not refundable once the Design Document is delivered. This is stated plainly wherever the fee is quoted.

19.5 Credit against the build. 50% of the design fee is credited against the build if you proceed within 30 days of delivery of the Design Document.

19.6 Licence in the Design Document. You receive a perpetual, irrevocable licence to use the Design Document for your own purposes, including having it built by someone else. We retain copyright in it.

20. Quote, scheduling and the queue

20.1 Fixed quote. Priced from the Design Document, not from a guess. You get a per-milestone price, a start date and a delivery date. Valid 30 days.

20.2 Builds run one at a time. We do not run two builds at once. The queue is first-paid, first-served.

20.3 Your start date is confirmed in writing before you pay. It is a date, not "soon". No build money is taken before the start date is confirmed in writing.

20.4 Turnaround runs from the confirmed start date. Published turnarounds are working time from your start date, not from when you pay.

20.5 Rush. Rush is +40% and buys an earlier start, not a shorter build. The verification stage is not skippable. Rush can only take a slot nobody has been promised. It never moves someone whose date is already confirmed, and it never starts a second build alongside yours.

20.6 The deposit books a slot, not immediate work.

21. Build, delivery and acceptance

21.1 Source at every Milestone. You receive the full source at every Milestone, not only at the end. Each Milestone ships as a working, testable thing with its own Acceptance Condition.

21.2 What Delivery means. A Milestone is Delivered when we post in the engagement Ticket: (a) the source at that Milestone, (b) a statement of which Acceptance Conditions it meets, and (c) instructions sufficient to run it on the Supported Environment. The Ticket timestamp is the delivery time.

21.3 Acceptance window. 7 calendar days from Delivery. Calendar days deliberately: this deadline runs in your favour and does not depend on our schedule.

21.4 Deemed acceptance, and the reminder that gates it. If the window passes with no response, the Milestone is deemed accepted and invoiced. We must post a reminder in the same Ticket by the end of the 5th calendar day, or where that falls on a non-working day, by the end of the last working day before it. Without that reminder the window does not lapse. Both posts are kept as the record.

21.5 Rejection. You may reject a Milestone within the window by identifying which Acceptance Condition it fails. We correct it at no cost, as a Defect. If no failing condition can be identified, the request is a Change, not a rejection.

21.6 Invoicing on acceptance. Each Milestone is invoiced on acceptance, never on delivery. You never pay for work you have not been able to test.

21.7 Prepayment limit. No more than one Milestone may be delivered and unpaid at a time, and no Milestone beyond the next may be prepaid.

21.8 What "done" means. Every build ships with an automated test suite, debug and probe commands you keep, benchmarks measured against a budget stated in advance, and milestone gates reported honestly - including when one has not been met. Anything touching existing player data is dry-run by default and writes a rollback file before it mutates anything.

22. Defects, Changes and revisions

22.1 Defect. Behaviour that fails an Acceptance Condition, or contradicts the Design Document or Documentation, on the Supported Environment. The test is the Design Document, not intent, expectation or preference.

22.2 Change. Any requirement not stated in the Design Document, including anything in its out-of-scope list, and anything that becomes apparent only after seeing the work.

22.3 Treatment.

22.4 Revisions. Two revision rounds are included for anything that does not match the agreed design where the implementation is defensible but not what you wanted. Bugs are never counted as revisions.

22.5 Nothing is added silently. A Change gets its own price and its own effect on the delivery date, agreed in writing before the work is done.

22.6 Gaps in the Design Document. Where an omission is something a competent designer should have specified, we absorb it as a Defect. Where it is a genuine change of requirement, it is a Change. Where reasonable people would disagree, it is treated as a Defect - the Design Document is our deliverable and its quality is our responsibility. Work absorbed under this paragraph is capped at 10% of the affected Milestone's quoted value; beyond that, we re-scope by agreement.

22.7 Not Defects. A requirement that turns out to be impossible or unwise; changes to the Supported Environment after sign-off, including framework and third-party updates; and anything caused by your own modification of delivered source. You may modify freely; we are not responsible for the result.

23. Commission ownership, licence and exclusivity

23.1 What you get. The full source, and a perpetual, non-exclusive, irrevocable licence to use, modify and deploy the commissioned work on any server you own or operate. The licence never expires and survives the end of our working relationship for any reason.

23.2 What you may not do. Resell, redistribute, sublicense or publish it, modified or unmodified.

23.3 What we keep - read this part. We retain ownership of the commissioned work, and unless you buy exclusivity we may produce and sell a derived or generalised version later. You are buying a licence and the source, not the copyright.

23.4 Never reused. Your configuration, branding, artwork, written content, anything identifying your Community, and any mechanic you tell us is unique to you and which is recorded as such in the Design Document before the build starts. These exclusions survive indefinitely.

23.5 The reuse boundary. Reusable: anything that would be written substantially the same way for a different client with a different brief. Not reusable: anything shaped by your specific requirements. Where a component is arguably both, it is not reused without your written agreement.

23.6 Exclusivity. Available at +100% of the quoted build price, agreed in writing before the build starts. Under exclusivity we will not sell, reuse or licence the commissioned work, or any substantially similar work, to anyone else.

23.7 The exclusivity field. Exclusivity is worldwide, perpetual, and limited to FiveM and other Cfx.re platforms. "Substantially similar" means work implementing the same distinguishing mechanics in a way an ordinary player or server operator would recognise as the same system, regardless of naming, framework or reimplementation. It does not extend to shared techniques, libraries, infrastructure or general know-how, or to work in other games or media.

23.8 Materials you supply. Where you supply code, artwork, data or written content that becomes embedded in the work, you grant us a perpetual, royalty-free licence to use it solely as embedded in that work, and you confirm you have the right to do so. We acquire no other rights in it and it falls inside the section 23.4 exclusions.

23.9 Transfer on sale. Your licence may be assigned once, in writing, to a buyer acquiring your Community as a going concern, provided they accept these Terms and you keep no copy. Notify us through the engagement Ticket or support@misscheviousmarketplace.com. We acknowledge the transfer in writing and do not unreasonably withhold or delay it. What transfers is the licence, not the engagement.

23.10 Portfolio. We may describe the engagement in general terms as portfolio work. We will not publish your configuration, branding, artwork, written content or anything identifying your Community, and we will not describe the engagement at all if you ask us in writing not to.

23.11 Survival. Your licence is perpetual and irrevocable and survives termination, expiry, breach and any dispute.

24. Commission warranty and aftercare

24.1 What we warrant. That the work will conform to the Design Document and perform materially in accordance with its Acceptance Conditions on the Supported Environment, and that it is our original work or properly licensed.

24.2 Aftercare. On delivery you receive the source, the Design Document, the test suite, debug commands, and install support until it runs on your server.

24.3 Reproducible Defects are free for 60 days from Delivery of the final Milestone.

24.4 What aftercare does not cover. Third-party resources and scripts we do not control; frameworks or versions outside the Supported Environment; changes to your environment after sign-off, including framework and dependency updates; your own modifications; your hosting; and Cfx.re, Discord or Tebex outages or rule changes. Compatibility work after a platform or framework update is chargeable, including during the 60-day window.

24.5 Otherwise. Except as stated in this section, the work is provided without other warranties, express or implied, including implied warranties of merchantability and fitness for a particular purpose, to the maximum extent permitted by law.

25. Cancellation, delay and your responsibilities

25.1 If you cancel before your slot starts: full refund of the deposit.

25.2 If you cancel after your slot starts: the deposit covers work already done and is not refundable, and you receive everything built so far - source, Design Document and tests, at whatever Milestone it reached. You are invoiced only for completed and accepted Milestones. Partially completed work is delivered but not charged for.

25.3 The design fee is never refundable. You already have the document.

25.4 If we are late. You are told as soon as we know, with a revised date and the reason. If a delay is on us and you no longer want the work, you get your deposit back.

25.5 If we become unavailable. Where we cannot continue, you receive everything built to that point and the money position at section 25.2 applies. The detailed continuity mechanism is in the Engagement Summary and the commission contract terms it incorporates.

25.6 Your delay. Delay attributable to you extends the delivery date correspondingly and is not a Defect. Where an engagement is idle for 30 consecutive days because we are waiting on you, we may release your build slot and re-queue the work at the next available date. Your deposit is not forfeited, and nothing paid is lost - the slot is, and rejoining the queue may mean a later start.

25.7 Backups are yours. You are solely responsible for maintaining current backups of all server data. Any migration or data tooling we provide is a convenience and does not replace your backups. Back up your database before running any installation or migration step. This allocation is repeated in the Documentation and in the Engagement Summary because it matters.

25.8 Late payment. Invoices are due within 14 days. We may pause work on an overdue invoice, having told you first. Interest on late payment accrues at the statutory rate applicable in the Commonwealth of Virginia.

25.9 Access and decisions. You will give us timely access, information and decisions, and a test environment where the work needs one.

26. The Discord Server and the Bot

26.1 The Discord Server is a privilege, not property. Membership, roles and channel access are provided at our discretion and may be changed or withdrawn. They are not the product. Losing Discord access does not revoke a licence you hold, or entitle you to a refund.

26.2 The Bot is licensed, not sold. We grant you a revocable, non-exclusive right to use the Bot for its intended purpose. We may change, suspend or discontinue it, or any command, at any time.

26.3 No uptime warranty. The Discord Server and the Bot depend on Discord's platform, its API and its rate limits. We give no warranty of availability for either, and we are not responsible for Discord outages, changes or moderation decisions.

26.4 What the Bot handles. The Bot processes your Discord user ID, the email you submit to /link or /verify, your Tebex customer record and purchases, your ticket contents, and your command usage. What we hold and why is set out in our Privacy Policy. You can see what is on file with /privacy status and remove a verified email with /privacy delete.

26.5 Never put these in a Ticket or a DM. Card numbers, payment details, passwords, API keys or authentication tokens. We will never ask for any of them. A Ticket is a shared support channel, not a secure vault.

27. Acceptable use and enforcement

27.1 In the Discord Server you must not: harass, abuse or attack others, or use hate speech or slurs; post NSFW, gore or shock content, including in avatars, nicknames and status text; spam, mass-ping, advertise unsolicited, or DM-advertise our members; raid, scrape, or attempt to disrupt the server; impersonate staff, the Bot, or another member; request, offer or link to leaked or pirated resources; advertise a competing store in customer channels; or bring conflicts from other communities here.

27.2 Moderation. Staff apply these with judgement rather than as a checklist. Consequences scale with what was done and whether it has happened before: typically warning, then timeout, then kick, then ban. Some things skip to the end: leaks, redistribution, raids, hate speech and NSFW.

27.3 We are not obliged to give a public reason for a moderation decision. If you think one was wrong, open a General Support Ticket and make your case. That route works. Arguing in public does not.

27.4 Conduct and your purchases are separate. Moderation of your conduct in the Discord Server does not affect the licences you hold, except where the conduct is itself a breach listed at section 12.4, fraud, or a chargeback under section 16. Being banned for rudeness does not revoke what you bought.

28. In-game fiction and lawful use

28.1 Roleplay systems are fiction. Resources such as the Blackmarket Shop, Money Laundering, EMS and similar systems are roleplay mechanics for a game. They simulate fictional activity inside FiveM. They do not facilitate, encourage or provide instructions for anything in the real world.

28.2 Lawful use only. You must not use the Services, or anything we supply, for real-world criminal activity, fraud, money laundering, sanctions evasion, or the sale of illegal goods or services. You must not use them to attack, disrupt or gain unauthorised access to any system.

28.3 We may report unlawful activity to the appropriate authorities and to the relevant platform.

29. Your server, your compliance

29.1 Your Community is yours. You are responsible for it: its content, its rules, its moderation, its players, and how it makes money.

29.2 Platform rules. You are responsible for complying with the Cfx.re Creator Platform Licence and Cfx.re platform rules, Rockstar Games policies including its policy on monetisation of Grand Theft Auto, the Tebex Acceptable Use Policy, and Discord's terms. That includes, without limitation, not running real-money gambling, not selling in-game currency or advantage in breach of those policies, and not using unauthorised intellectual property.

29.3 We do not vet your server. Nothing in these Terms, and no sale or Commission, is an approval of your Community, its content or its monetisation.

29.4 Consequences are yours. If a platform suspends, bans or takes action against your Community, your Cfx.re account or your Tebex store, that is between you and that platform. It does not entitle you to a refund of Resources you have bought, except where the cause is our breach.

30. Disclaimers

30.1 As is. Except for the warranties expressly given at section 15.3, section 24.1 and this section, the Services and the Resources are provided "as is" and "as available", and we disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement, to the maximum extent permitted by law.

30.2 What we warrant, and what we do not. We warrant that we have the right to grant the licences in these Terms, and that a Resource performs materially as described in its Documentation on its Supported Environment. We do not warrant:

• that a Resource will work on a framework, version or third-party resource outside its Supported Environment;
• that it will be compatible with every other resource you run;
• that Cfx.re rules, Escrow behaviour, Keymaster, framework APIs or platform policies will stay as they are;
• that the Services will be uninterrupted or error-free; or
• any level of commercial success, player count, donations or revenue for your Community.

30.3 Documented behaviour is not a defect. Behaviour a Resource's Documentation records as expected is not a Defect and is not grounds for a refund.

30.4 Third parties. Discord, Tebex, Cfx.re, Rockstar, payment processors and hosting providers are independent third parties we do not control. We are not responsible for their acts, omissions, outages, rule changes or decisions.

31. Liability

31.1 Nothing in this section limits liability that cannot lawfully be limited. Section 31.6 lists what is carved out.

31.2 No indirect loss. We are not liable for indirect, incidental, special, consequential or punitive loss, or for lost profits, lost revenue, lost donations, lost players, loss of goodwill, server downtime, or lost or corrupted data, however caused.

31.3 Cap. Our total aggregate liability arising out of or in connection with these Terms, a Resource or a Commission is limited to the fees you actually paid us for the specific Resource or Commission giving rise to the claim in the 12 months before the claim arose.

31.4 Where a claim relates to the Services generally rather than to a specific Resource or Commission, the cap is the total fees you paid us in the 12 months before the claim arose.

31.5 Data. You are responsible for your own backups - section 25.7. Migration and data tooling we supply is a convenience and does not replace them. Subject to section 31.6, we are not liable for loss or corruption of data.

31.6 Carve-outs. Nothing in these Terms excludes or limits our liability for fraud or fraudulent misrepresentation; wilful misconduct; death or personal injury caused by negligence; or any other liability that cannot be excluded or limited under the law that applies to you.

31.7 Consumers. If you are a consumer, this section applies only to the extent permitted by the consumer law of your country, and your non-waivable statutory rights are unaffected.

32. Indemnity

32.1 What you cover. You will indemnify us against third-party claims, losses and reasonable costs arising from:

• your Community, its content, its rules, its moderation and its players;
• how you monetise your Community, including any breach of Cfx.re, Rockstar or Tebex policy;
• your breach of these Terms, including any redistribution, leak or licence circumvention by you or by a contractor you engaged under section 9.3;
• material you supply to us under section 23.8; and
• a chargeback you file in breach of section 16.2.

32.2 What we cover. We will indemnify you against third-party claims that a Resource, as supplied by us and used in accordance with these Terms and its Documentation, infringes that party's intellectual property rights. This does not apply to your modifications, third-party components under their own licences, use outside the Supported Environment, or use in breach of these Terms. Our liability under this section is subject to the cap at section 31.3.

32.3 Process. The party seeking indemnity will notify the other promptly, not admit liability, and allow the indemnifying party to conduct the defence, with reasonable cooperation at the indemnifying party's cost.

33. Force majeure

33.1 Neither of us is liable for delay or failure caused by events beyond reasonable control, including natural disaster, severe weather, war, civil unrest, epidemic, utility, internet or infrastructure failure, government action, and serious illness or injury.

33.2 This expressly includes outages, suspensions, rule changes, API changes and decisions of Discord, Tebex, Cfx.re, Rockstar, payment processors and hosting providers.

33.3 For Commissions, our unavailability is governed by the continuity mechanism in the Engagement Summary and the commission contract terms it incorporates, which are more specific and take precedence. This section is the backstop for anything that mechanism does not describe.

34. Suspension and termination

34.1 By you. Stop using the Services at any time. Perpetual licences you hold survive, as long as you comply with them.

34.2 By us. We may suspend or terminate your access to the Services, and where section 12.4 applies your licences, where:

• you materially breach these Terms and, where the breach can be fixed, do not fix it within 14 days of us asking you to;
• you breach section 10, section 16.2 or section 28, which are treated as breaches that cannot be fixed;
• payment due to us is overdue and remains unpaid after notice;
• a platform requires it; or
• we are required to by law or by a valid legal demand.

34.3 Effect. On termination of a licence you must stop using the Resource and remove it from every server. Termination does not entitle you to a refund except where section 15 applies, and does not release you from amounts already due.

34.4 Ceasing to trade. If we stop trading, your perpetual licences continue. We will give what notice we reasonably can.

34.5 Survival. Sections 1, 2, 4, 7.3, 7.5, 7.6, 10, 11, 12.5, 12.6, 16, 23, 28, 30, 31, 32, 35, 37 and 38 survive termination, along with any other provision which by its nature should.

35. Disputes, governing law and venue

35.1 Talk to us first - this is a condition precedent. Before starting any proceeding, you must give us written notice of the dispute through a Ticket or to support@misscheviousmarketplace.com, describing the dispute, identifying your transaction or engagement, and stating what you want. We then have 30 days to resolve it. Compliance with this section is a condition precedent to commencing proceedings, and either of us may seek a stay or dismissal of a proceeding started without it. We owe you the same obligation before bringing a claim against you.

35.2 No class actions - both tracks. Any claim may be brought only in your individual capacity, and not as a plaintiff or class member in any purported class, collective, consolidated or representative proceeding. You and we each waive any right to participate in one. This applies whether the claim proceeds in court or in arbitration.

35.3 Catalog track - court, no arbitration. For Store purchases and everything other than a Commission:

• disputes are resolved in court, not arbitration;
• these Terms are governed by the laws of the Commonwealth of Virginia, USA, without regard to its conflict-of-laws rules;
• the parties submit to the non-exclusive jurisdiction of the state and federal courts located in Virginia. Non-exclusive deliberately, so a small claim does not become uneconomic for either of us;
• jury trial is waived by both of us, to the extent permitted by law; and
• either of us may bring an individual claim in small claims court instead, where it qualifies.

35.4 There is no arbitration agreement on the Catalog track. Nothing in these Terms requires you to arbitrate a Store purchase.

35.5 Commission track - arbitration where activated. For a Commission, arbitration applies only where the Engagement Summary states that it does. It is offered for engagements where you are a business or other organisation, or the contract value exceeds $2,500.

35.6 Where activated: the dispute is finally resolved by binding arbitration administered by the arbitral institution named in the Engagement Summary, under its rules then in force, before one arbitrator, seated in the Commonwealth of Virginia, USA, conducted in English. Judgment on the award may be entered in any court of competent jurisdiction. Where arbitration is not activated, section 35.3 applies to the Commission as well.

35.7 Carve-outs from arbitration. Regardless of section 35.5, either of us may bring proceedings in court for injunctive or other equitable relief in respect of intellectual property, redistribution, leaks or licence circumvention - see section 12.6 - and either of us may bring an individual claim in small claims court.

35.8 If you are not in the United States. Where the law of your country of residence gives you a mandatory right that this section would remove, that right applies and this section does not. In particular, where a pre-dispute arbitration agreement or a class action waiver is unenforceable against you as a consumer under mandatory local law, that provision does not apply to you, and you may bring proceedings in the courts of your country of residence. The rest of this section continues to apply.

35.9 If the class waiver fails. If section 35.2 is held unenforceable as to a particular claim, then as to that claim only, any arbitration agreement is void and the claim proceeds in court. Class arbitration is not agreed to and is not available. The remainder of this section survives.

35.10 Severability of this section. If any part of this section is held unenforceable, the rest stands.

36. Changes to these Terms

36.1 We may change these Terms. The current version is always published at https://misscheviousmarketplace.com/legal/terms, with a version number and an effective date.

36.2 Notice. For a material change we will give notice at least 30 days before it takes effect, by posting in the Discord Server and on the website, and by email where we hold a verified address for you.

36.3 Which version applies. The version in force when you purchase governs that purchase. Continuing to use the Services after a change takes effect means you accept the updated Terms for future use. If you do not accept a change, stop using the Services; licences you already hold are unaffected.

36.4 Quotes and engagements are locked. A change to these Terms does not alter a written quote already issued and still valid, or a Commission already under way. Those remain on the version incorporated into the Engagement Summary.

37. General

37.1 Entire agreement. These Terms, together with any signed Engagement Summary and its Design Document, and the Documentation, are the entire agreement between us, and supersede prior discussions, quotes and marketing statements. Nothing in this section limits liability for fraudulent misrepresentation.

37.2 Assignment. You may not assign or transfer these Terms or your rights under them, except the single permitted licence transfer at section 11.2 or section 23.9. We may assign these Terms to a successor of the business, including on a sale of the project, on notice to you. Your licences and any Commission in progress transfer with it.

37.3 Independent contractor. For Commissions we act as an independent contractor. Nothing creates employment, partnership, joint venture or agency. Each party is responsible for its own taxes.

37.4 Severability. If a provision is held unenforceable, it is modified to the minimum extent necessary or severed, and the rest stands.

37.5 Waiver. A failure to enforce a term is not a waiver of it.

37.6 No third-party beneficiaries. These Terms are between you and us. No one else may enforce them, except that Tebex, Discord and Cfx.re may enforce any provision that expressly protects them, where the applicable law requires it.

37.7 Headings are for convenience and do not affect interpretation.

38. Notices

38.1 To us. By Ticket in the Discord Server, or by email to support@misscheviousmarketplace.com. The Ticket is the preferred route, because transcripts are archived automatically and there is always a record of what was agreed.

Formal legal notices may be sent to support@misscheviousmarketplace.com and are effective under section 38.4. If you need a postal address for service of process or to exercise a statutory right, ask through a Ticket or by email and we will provide one. We will not refuse a reasonable request for it.

38.2 To you. By post in your engagement Ticket, by email to the address on your Account or your Tebex record, or by a notice in the Discord Server for general changes.

38.3 Mail from us. Automated licence and transactional email is sent from licenses@send.misscheviousmarketplace.com with a reply-to of support@misscheviousmarketplace.com. Email from any other address claiming to be us, particularly one asking for payment details, is not from us.

38.4 Effective. A notice is effective when posted in the Ticket or when sent by email, unless a delivery failure is received.

---