Terms of Service
Effective Date: January 23, 2026 • Version 2.4
100% IP Ownership
Complete source code, Git repositories, designs, and architectural assets transfer to your organization upon milestone payment.
30-Day Launch Warranty
Every custom engineering release includes 30 days of proactive bug fixing and SLA monitoring at zero additional charge.
Milestone-Based Billing
No opaque retainers. Invoices are strictly tied to agreed sprint milestones, live demo approvals, and code reviews.
Zero Vendor Lock-in
We write clean, modular, and extensively documented TypeScript and Docker code so your internal teams can easily maintain it.
Acceptance & Scope of Agreement
By accessing Bintrix Tech services or approving an engineering proposal, you agree to these Terms of Service. All specific software engineering scopes, deliverables, sprint schedules, and payment schedules are formally governed by an individual Statement of Work (SOW) executed between Bintrix Tech and the client organization.
Engineering Deliverables & Code IP Transfer
Bintrix Tech operates on a full transparency, zero vendor lock-in principle. Upon fulfillment of the milestone invoice associated with a sprint or deliverable:
- 100% perpetual ownership of all authored source code, database schemas, and configuration scripts is transferred to the client.
- Full administrator permissions to Git repositories (GitHub/GitLab) and cloud environments (AWS/Vercel/Supabase) are handed over.
Payment Schedules & Milestone Sign-Off
Engineering invoices are issued against defined milestones. The client has 5 business days following sprint demo delivery to review and provide acceptance or specify bug remediation items before milestone finalization.
30-Day Post-Launch Warranty Period
All custom platforms engineered by Bintrix Tech include 30 consecutive days of warranty support starting on the official production deployment date. During this period, our engineering team fixes any discovered functional defects within the agreed SOW scope at no additional cost.
Limitation of Liability
Neither party shall be liable for indirect, incidental, punitive, or consequential damages. The total aggregate liability of Bintrix Tech for any claims arising out of an engagement shall not exceed the total fees paid by the client under the specific Statement of Work in the preceding 3 months.
Legal Contact & Inquiries
If you have questions regarding legal agreements, custom MSA negotiations, or vendor onboarding requirements, contact our corporate contracts desk:
Frequently Asked Contract Questions
Q1.Who owns the intellectual property and source code created during a project?
You do. Upon receipt of agreed milestone payments, Bintrix Tech assigns 100% full intellectual property rights, repository commits, and design source files to your company with zero residual claims.
Q2.How are project milestones and revisions managed?
Every engagement is outlined in a formal Statement of Work (SOW) with scheduled sprint reviews. Revisions within agreed scope are incorporated during sprint cycles, while scope expansions are estimated through standard change-order addendums.
Q3.What does the 30-day post-launch warranty include?
The standard 30-day warranty covers remediation of software defects, unexpected bugs, and deployment regressions relative to the agreed project acceptance criteria.
Q4.What payment terms and billing models do you support?
We support milestone-based fixed-price contracts for well-defined scopes, as well as dedicated monthly sprint retainer models for agile, evolving product roadmaps. Payment methods include international wire transfers (SWIFT) and corporate bank transfers.
Q5.How is confidentiality maintained throughout the engineering contract?
Confidentiality clauses in our Master Services Agreement (MSA) remain legally binding indefinitely, ensuring all trade secrets, business strategies, and codebase structures remain strictly protected.
Ready to partner with a team that guarantees 100% IP ownership?
Let's discuss your product roadmap and build a custom, milestone-driven technical specification.