Terms of Service
Last Updated: November 2026 · Tushar Labs Studio, New Delhi
1. Engagement Structure
Tushar Labs operates as an independent technical studio delivering bespoke websites, full-stack software, and automated AI workflows. Every engagement begins with a clear scope specification and mutual sign-off before active engineering commences.
2. Payment Structure & 50% Advance Policy
Standard Studio Milestone Terms:
- 50% Initial Advance: Required prior to architectural kickoff, UI wireframing, and repository provisioning. Work initiates only after advance receipt.
- 50% Final Settlement: Payable upon project completion, demonstration on staging, and prior to final source code handover / live DNS migration.
* Milestone-based payment schedules may be defined for enterprise software engagements exceeding ₹1,00,000 upon mutual agreement.
3. Project Timelines & Scope Estimation
All delivery timelines mentioned across the website or proposals are working estimates. Actual delivery schedules depend strictly on:
- The full depth, complexity, and custom API requirements of the client's project.
- Client response turnaround times for assets, copy, approvals, and third-party credentials.
- Third-party service dependencies (e.g., payment gateway KYC, domain verification, OpenAI API limits).
We do not issue arbitrary rigid delivery guarantees; we prioritize architectural integrity, security, and real-world performance over rushed, fragile code.
4. Scope Changes & Revisions
Each fixed-scope project includes standard iterative revisions within the mutually agreed technical brief. Any major feature additions, architecture pivots, or new integration requests outside the original scope will be billed under an amendment or separate phase.
5. Intellectual Property & Code Ownership
Upon full receipt of the final payment, 100% intellectual property rights, customized frontend/backend source code, and assets created specifically for the project transfer completely to the client. Tushar Labs retains the right to display the completed work in its portfolio and case studies unless restricted by a formal NDA.
6. Maintenance & Post-Launch Support
Standard builds include handover documentation and deployment verification. Ongoing server maintenance, cloud backups, dependency updates, and feature additions are managed through dedicated monthly retainer packages available separately.