Skip to content

Legal

Client Agreement

This agreement outlines practical terms for clients who hire Laravel developers, buy services, request managed delivery, or make project payments through Laravelone.co.in.

Effective date: Jul 29, 2026

These documents are general website templates for Laravelone.co.in and are not legal advice. Please have them reviewed by a qualified lawyer before relying on them for production, payments, disputes, or compliance.

1. Scope of Agreement

This Client Agreement applies when a client submits a project request, hires a listed developer, purchases consulting, requests managed delivery, enrolls in a service, or makes any project-related payment through Laravelone.co.in. Specific project terms may be set out in a work order, proposal, invoice, milestone sheet, email confirmation, or project workspace.

2. Client Responsibilities

The Client must provide accurate requirements, content, technical access, credentials, brand assets, acceptance criteria, business rules, third-party account details, and timely feedback. Laravelone.co.in and assigned developers are not responsible for delays caused by missing information, late approvals, unclear requirements, unavailable stakeholders, or blocked access.

3. Project Scope and Change Requests

Only work expressly included in the accepted scope is covered by the agreed fee. Additional features, integrations, deployment work, emergency support, migrations, meetings, revisions, documentation, security reviews, performance tuning, or third-party setup may require a written change request, revised price, and adjusted timeline.

4. Payments and Taxes

The Client must pay all agreed fees, advances, milestones, retainers, hourly-cycle invoices, taxes, gateway charges, and bank charges when due. Work may not begin, continue, deploy, or be handed over until the required payment is received. Applicable GST, TDS, payment gateway charges, and other statutory charges may apply based on the transaction and legal status of the parties.

5. Milestones, Hourly Work, and Acceptance

Milestone work may be accepted when the agreed deliverable is substantially completed according to the accepted scope. Hourly work may be billed based on time logs, work notes, activity summaries, or other agreed tracking data. The Client should review each deliverable within the stated review period. If no written rejection with specific issues is received within that period, the deliverable may be treated as accepted.

6. Revisions and Defect Correction

Reasonable correction of in-scope defects may be included during the agreed review period. Cosmetic preferences, new workflows, changed business rules, third-party API changes, unsupported hosting environments, and issues caused by client modifications may be treated as additional work.

7. Client Access, Data, and Backups

The Client is responsible for maintaining backups of production systems, databases, credentials, media, business records, and third-party accounts unless expressly agreed otherwise. The Client should provide minimum necessary access and revoke or rotate credentials after completion. Laravelone.co.in is not responsible for pre-existing vulnerabilities, legacy code defects, hosting failures, or data loss outside the agreed scope.

8. Third-Party Services

The Client is responsible for third-party subscriptions, domains, hosting, SSL, APIs, payment gateways, SMS/email providers, AI APIs, app stores, licenses, and usage limits unless expressly included in the project fee. Delays or failures by third-party providers may affect delivery and are outside Laravelone.co.in's reasonable control.

9. Intellectual Property and Handover

Subject to full and final payment, the Client may receive ownership or use rights in custom deliverables expressly created for the project. Pre-existing tools, templates, libraries, open-source components, frameworks, reusable knowledge, generic snippets, and Laravelone.co.in materials remain subject to their existing ownership and licenses. Final handover may be withheld until all due amounts are paid.

10. Confidentiality

Laravelone.co.in will use reasonable care to protect confidential client information shared for project delivery. The Client must also protect platform records, private proposals, pricing, credentials, communication history, and developer information from unauthorized disclosure.

11. Suspension or Termination

Laravelone.co.in may pause or terminate work for non-payment, abusive conduct, unlawful requests, unsafe access, repeated scope changes without approval, suspected fraud, security risk, or breach of applicable terms. Amounts already paid for completed work, commenced work, third-party charges, or reserved capacity may be non-refundable as described in the Refund and Cancellation Policy.

12. Dispute Resolution

The Client should first raise disputes in writing with specific references to the agreed scope, deliverables, payment records, and communication history. Laravelone.co.in may review workspace records, milestone status, time logs, invoices, and written communications before deciding whether correction, partial refund, payout hold, or other action is appropriate.

13. Indemnity

The Client agrees to indemnify Laravelone.co.in and assigned contributors against claims arising from client-provided content, unlawful instructions, intellectual-property infringement, third-party account misuse, inaccurate information, unpaid taxes, non-payment, or breach of this agreement.

14. 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, or business interruption damages. Liability for a specific client engagement is limited to the amount paid by the Client to Laravelone.co.in for the disputed engagement during the preceding three months, unless applicable law requires otherwise.

15. Force Majeure

Laravelone.co.in is not liable for delay or failure caused by events beyond reasonable control, including natural disasters, health emergencies, cyberattacks, cloud outages, internet failures, payment gateway failures, labor disruptions, government action, legal restrictions, war, civil unrest, or third-party service outages.

16. 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.

FAQ

Frequently Asked Questions

How does Laravelone help clients hire Laravel developers? +

Clients can browse Laravel developer gigs, review service details, and start a hire request through the platform. Laravelone supports milestone or hourly tracking depending on the engagement.

What is the difference between triparty and two-party work formats? +

Triparty work is used when a client hires a listed developer through Laravelone. Two-party work is used when a client approaches Laravelone directly and Laravelone manages delivery.

Can projects be tracked by milestones or hourly logs? +

Yes. Project-based work can use milestones, deliverables, and completion records. Hourly work can use time logs, work notes, and billing-cycle records.

Does Laravelone support courses and AI implementation? +

Yes. Laravelone includes advanced Laravel courses, interview help, architecture support, and practical AI implementation services for Laravel teams.