ToneCustoms — Partnership Agreement Template
Draft for individual review; not an active agreement or offer. This template is for private discussion and should be adapted to the actual collaboration and reviewed for applicable legal requirements before signing. Do not submit completed agreements, signatures, addresses or financial details in public GitHub Issues.
1. Parties and effective date
ToneCustoms representative / legal contracting party: [To be confirmed privately]
Partner / legal contracting party: [To be confirmed privately]
Effective date: [Date]
Agreement term: [Start and end date, or agreed termination arrangement]
2. Purpose and scope
Collaboration type: [Server / Creator / Developer / Community / Other]
Project description: [Specific scope]
Deliverables and owners:
| Deliverable | Responsible party | Due date | Approval criteria |
|---|---|---|---|
| [Describe] | [Party] | [Date] | [Criteria] |
Any material change to scope, timeline or deliverables requires written agreement by both parties.
3. Payment, benefits and expenses
Compensation or benefits: [None / agreed amount / agreed benefits]
Payment timing and method: [If applicable]
Expenses: Each party bears its own expenses unless otherwise agreed in writing.
No free scripts, discounts, sponsorships, revenue shares, exclusive rights or priority support are implied by the relationship.
4. Script licenses and intellectual property
ToneCustoms retains ownership of its pre-existing scripts, brand and other intellectual property, subject to applicable third-party rights. Any script license remains subject to its applicable terms. This agreement does not permit redistribution, sublicensing, sharing paid source code, selling copies or transferring license access without separate express written authorization.
Ownership and permitted uses of newly created deliverables: [Specify individually, including source files, videos, graphics and documentation]
Third-party assets and dependencies: Each party is responsible for obtaining the permissions required for materials it contributes.
5. Branding, publication and publicity
Neither party may imply endorsement or use the other's protected logos, trademarks, promotional materials or likenesses beyond the permissions explicitly agreed here.
Approved branding and content: [List]
Review and approval process: [Describe]
Advertising / sponsorship disclosures: Each party must comply with applicable disclosure laws and platform requirements for paid or incentivized promotions.
6. Confidentiality and data
The parties will use confidential information only for the agreed collaboration and protect it with reasonable care, subject to agreed exceptions and applicable law.
Approved private communication channel: [Specify privately]
Personal data or customer information involved: [None / separate written data-handling terms required]
Do not share credentials, license keys or customer records in public GitHub issues.
7. Standards and compliance
Both parties will comply with applicable laws, platform terms, copyright obligations and relevant FiveM/Cfx.re requirements. Neither party may misrepresent the other's role or make unauthorized commitments on the other's behalf.
8. Termination and outstanding obligations
Termination triggers and notice: [Specify]
Outstanding payments and accepted deliverables: [Specify]
Return/deletion of confidential materials and cessation of brand use: [Specify, subject to legal retention requirements]
Termination does not automatically transfer ownership or cancel obligations that expressly survive termination.
9. Liability and disputes
Applicable law / jurisdiction: [Confirm with legal advice]
Liability allocation and any limitations: [Negotiate; legal review required]
Dispute-resolution procedure: [Negotiate]
Do not assume this template alone supplies legally adequate liability, consumer protection, privacy or dispute-resolution terms.
10. Final review checklist
- [ ] Authorized parties and signatories confirmed privately
- [ ] Scope, deliverables, due dates and acceptance criteria agreed
- [ ] Any payment, benefit or expense arrangement documented
- [ ] Existing scripts and new work have clear ownership and license terms
- [ ] Brand use, promotion approvals and disclosure requirements agreed
- [ ] Confidentiality, personal-data handling and private communication agreed
- [ ] Termination, liability and dispute terms reviewed for the relevant jurisdiction
- [ ] Required platform and third-party permissions confirmed
- [ ] Final agreement reviewed and approved before any performance or public announcement
11. Approval and signatures
Each party confirms that its signatory is authorized to enter the agreement.
ToneCustoms authorized signatory: [Name, signature, date]
Partner authorized signatory: [Name, signature, date]
Related guidance: Partnership Rules · Licensing · Support.
Status: Template only. No partnership is active until the appropriate parties approve and execute their final agreement.