1. Parties and Purpose
This Triparty Agreement is structured between the Client, the Developer, and Laravelone.co.in. It applies when the Client hires a listed Developer through the platform and Laravelone.co.in acts as the platform, administrative, tracking, billing, payment collection, commission, and disbursement coordination party.
2. Platform Role
Laravelone.co.in may verify developers, approve listings, collect client payments, maintain project records, coordinate communication, track milestone or hourly status, deduct platform commission, maintain books and statements, and disburse approved payouts. Laravelone.co.in does not guarantee that every developer is suitable for every project, and the Client must evaluate the Developer's profile, listing, and proposed scope before hiring.
3. Developer Listing, Fees, and Background Verification
The Developer may list gigs after paying applicable platform fees, submitting profile details, and completing required checks. Laravelone.co.in may perform background verification, document checks, identity checks, LinkedIn/profile review, credential review, skill checks, or references before approving or continuing a listing. Approval may be revoked if information is inaccurate, unverifiable, misleading, expired, or materially incomplete.
4. Scope, Work Order, and Engagement Records
The Client hires the Developer based on a listing, project brief, scope document, milestone plan, hourly arrangement, retainer, proposal, or written work order. Scope, assumptions, exclusions, timelines, rates, acceptance criteria, support period, and deliverables should be documented before work begins. Any scope change should be recorded in writing and may require additional fees or timeline changes.
5. Project Tracking Workspace
After hiring, a tracking workspace may be opened for project records. Project-based work may include milestones, deliverables, review comments, completion evidence, and acceptance records. Hourly work may include time logs, work notes, billing cycles, screenshots or activity summaries where agreed, and client-visible tracking data. Platform records may be used to evaluate delivery, payouts, disputes, and refunds.
6. Client Responsibilities
The Client must provide accurate requirements, required access, content, technical information, approvals, timely feedback, and payment as per the agreed schedule. Client delays, incomplete requirements, blocked access, third-party provider delays, or changed business rules may affect timelines, fees, milestone acceptance, or hourly billing.
7. Developer Responsibilities
The Developer must deliver services with reasonable professional care, communicate clearly, protect confidential information, follow platform tracking and payment rules, respect open-source licenses, disclose blockers, avoid malicious code, and refrain from bypassing Laravelone.co.in for payment or direct commercial arrangements arising from platform leads.
8. Payments, Commission, and Disbursement
The Client pays Laravelone.co.in for the applicable milestone, hourly cycle, retainer, or project payment. Laravelone.co.in may deduct platform commission, taxes, TDS where applicable, gateway charges, bank charges, refunds, chargebacks, penalties, or approved adjustments before disbursing the remaining amount to the Developer. Disbursement may depend on milestone acceptance, hourly approval, settlement from the payment gateway, KYC completion, dispute status, and banking timelines.
9. Taxes, Books, Statements, and Certificates
Laravelone.co.in may maintain platform books, invoices, payment records, payout statements, commission records, tax records, and support documentation. TDS certificates or statements may be issued only where legally applicable, such as Form 16A for eligible non-salary payments or Form 16 only for salary or employment arrangements. The final treatment depends on the legal relationship, nature of payment, tax status, and advice from a qualified tax professional. Developers and Clients remain responsible for their own tax filings unless expressly agreed otherwise in writing.
10. Refunds, Chargebacks, and Payout Holds
Refunds and cancellations are governed by the Refund and Cancellation Policy and the specific project record. Laravelone.co.in may pause Developer payouts during material disputes, suspected fraud, chargebacks, duplicate payment claims, incomplete milestones, unlawful work requests, or unresolved quality complaints. Fraudulent chargebacks or payment misuse may lead to suspension and recovery action.
11. Intellectual Property
Subject to full and final payment, custom deliverables may transfer to the Client according to the work order. Pre-existing tools, reusable libraries, open-source packages, generic snippets, developer know-how, Laravelone.co.in templates, and third-party materials remain subject to their existing ownership and licenses. The Developer must disclose material third-party dependencies that may affect ownership, licensing, cost, or deployment.
12. Confidentiality and Data Protection
All parties must protect confidential information, including credentials, source code, business records, personal data, proposals, pricing, and private communications. Access must be limited to what is necessary for project delivery and revoked when no longer required. Each party must comply with applicable data protection, cybersecurity, and confidentiality obligations.
13. Non-Circumvention
The Client and Developer must not bypass Laravelone.co.in to avoid platform fees, commission, tracking, tax records, payout controls, or payment processes for leads or projects introduced through the platform. Breach of this section may result in account restriction, payout hold, listing removal, commission recovery, or other remedies available under law.
14. Dispute Resolution
Disputes should first be raised in writing with specific references to scope, deliverables, time logs, milestone status, communications, payment records, and evidence. Laravelone.co.in may facilitate review but is not required to act as a court, arbitrator, or expert unless expressly agreed in writing. Platform records may be used to decide payout holds, partial releases, refund recommendations, corrections, or administrative action.
15. Suspension and Termination
Laravelone.co.in may suspend tracking, pause payment processing, remove listings, restrict access, terminate engagement support, or hold payouts where there is suspected fraud, non-payment, misuse, confidentiality breach, unlawful work, abusive conduct, security risk, repeated complaints, or breach of this agreement.
16. Indemnity
Each party agrees to indemnify the others for losses arising from its own breach, misrepresentation, unlawful conduct, infringement, confidentiality breach, tax non-compliance, data misuse, payment fraud, or violation of third-party rights. The Developer indemnifies the Client and Laravelone.co.in for defective, infringing, malicious, or unauthorized deliverables caused by the Developer's acts or omissions.
17. Limitation of Liability
To the maximum extent permitted by law, Laravelone.co.in is not liable for indirect, incidental, consequential, punitive, loss-of-profit, loss-of-data, loss-of-business, or reputational damages. Laravelone.co.in's liability for a specific engagement is limited to the platform commission actually retained by Laravelone.co.in for that disputed engagement during the preceding three months, unless applicable law requires otherwise.
18. Force Majeure
No party will be liable for delay or failure caused by events beyond reasonable control, including natural disasters, epidemic, pandemic, fire, flood, war, terrorism, civil unrest, labor disruption, government action, court order, changes in law, internet outage, cloud provider outage, payment gateway failure, cyberattack, or third-party service disruption.
19. Governing Law and Jurisdiction
This agreement is governed by and construed in accordance with the laws of India. Any disputes arising out of or in connection with this agreement shall be subject to the exclusive jurisdiction of the competent courts in Kerala State, India.