Skip to main content
Client Engagements

Software Service Terms

General expectations for software projects. Every paid engagement should also have an agreed proposal or statement of work.

Effective: 8 October 2026 · Last updated: 8 October 2026

Order of documents: A signed proposal, statement of work or platform contract controls the specific project. If it conflicts with this page, the project-specific written agreement controls.

1. Scope & Assumptions

Deliverables, exclusions, dependencies, milestones, estimated timeline and fees should be recorded in writing before development begins. Estimates depend on the information available at the time and may change when requirements or assumptions change.

2. Client Responsibilities

The client provides timely decisions, content, access, test accounts and lawful rights to supplied materials. Delays in feedback, access or third-party approvals may move the delivery schedule.

3. Milestones, Reviews & Acceptance

Work may be delivered in reviewable milestones. The client should test each milestone and report reproducible issues within the review period stated in the proposal. A new feature or changed requirement is handled as a scope change, not a defect.

4. Fees, Invoices & Third-Party Costs

Payment schedule, currency and taxes are stated in the project agreement or marketplace contract. Hosting, domains, paid APIs, app-store accounts, messaging services, payment gateways and other third-party fees are excluded unless expressly included.

5. Changes & Additional Work

Scope changes require written agreement on their impact to cost and timeline. We will not silently add unapproved charges; equally, work outside the agreed scope is not automatically included.

6. Intellectual Property & Handover

After agreed payments are completed, the client receives the project-specific source code, assets and documentation identified in the project agreement. Pre-existing tools, reusable libraries, open-source software and third-party components remain subject to their existing ownership and licences.

7. Confidentiality & Portfolio Use

Confidential information is used only for the project and protected with reasonable care. Client names, testimonials, screenshots and private project details are published only with permission. A separate NDA may be signed when appropriate.

8. Security & Credentials

Clients should use secure credential-sharing methods and rotate temporary access after handover. No internet-facing system can be promised to be completely free of vulnerabilities. Security testing or compliance work must be explicitly included in scope.

9. Warranty, Support & Maintenance

The proposal should state any post-launch defect-support period. Ongoing maintenance, monitoring, content changes, platform updates and new features require a separate support arrangement unless included in writing.

10. Cancellation & Suspension

Either party may end work according to the project agreement. Completed work, committed third-party costs and approved milestones remain payable. Handover of paid work is provided in the form agreed for the project.

11. Platforms & Marketplace Projects

When a project originates on Upwork, Fiverr or another marketplace, communication, payments, disputes and contract rules remain subject to that platform’s current policies.

12. Contact

Questions about these terms can be sent to collegesathi10@gmail.com. These website terms do not by themselves create a project contract.

Recommended: Both parties should review and approve the project proposal before paying or starting work. Obtain independent legal advice for high-value, regulated or cross-border engagements.