The commercial terms, without the fog.
- EFFECTIVE
- 1 August 2026
- BILLING
- Milestones or monthly, 15-day terms
- CODE OWNERSHIP
- Yours, in your repository
- JURISDICTION
- Surat, Gujarat, India
Who these terms bind
These terms govern use of softieons.com and any engagement with Softieons Technology, a software studio registered in Surat, Gujarat, India. Where you have signed a proposal, statement of work, master services agreement or product subscription with us, that document takes precedence over anything written here.
Nothing on this website — page copy, price ranges, timelines or portfolio outcomes — is an offer or a guarantee. Only a written quotation signed by both sides is.
Quotes, scope and change requests
Every project begins with a written scope: the screens, roles, integrations and deliverables included, and the things explicitly excluded. Our quotation is valid for 30 days and assumes the scope as written.
Work that falls outside that scope is a change request. We estimate it, tell you what it does to the timeline, and wait for your approval in writing before building it. Nothing gets added to an invoice as a surprise.
Payment, milestones and GST
Standard billing, unless your contract says otherwise:
- Fixed-scope projects: an advance to begin, then milestone invoices against agreed deliverables.
- Dedicated teams and retainers: monthly, invoiced in advance of the month worked.
- Invoices are payable within 15 days. GST is charged as applicable and shown separately on every invoice.
- Third-party costs — hosting, licences, ad spend, store fees, SMS or WhatsApp message charges — are yours, billed at cost or paid by you directly.
- Persistent non-payment pauses work. We give notice in writing before anything stops, and we never hold your live systems hostage.
What we need from you
Projects slip on availability far more often than on engineering. We ask for one named decision-maker, feedback within five working days of each demo, and the content, credentials and third-party access we list at kickoff.
Where a delay in those items pushes the timeline, the schedule moves by that much, and a project idle for more than 60 days may be re-quoted at current rates.
Who owns what
On full payment, all custom code, designs and assets built specifically for you are yours — source in your repository from the first sprint, hosting and store accounts in your name, and handover including the data model and deployment steps.
We retain ownership of our pre-existing frameworks, internal libraries, tooling and our five licensed products, along with anything generic we would reuse on other projects. You get a perpetual right to use those components as embedded in your system. Open-source dependencies remain under their own licences.
Product subscriptions
Residieons, Travelieons, Chatieons, Accountieons and Shipieons are licensed on a subscription. You get the right to use them for your business for the subscription term; you do not get ownership of the software, and you may not resell, sublicense or reverse-engineer it.
Data your team enters remains yours and is exportable on request at any time. Subscriptions renew unless cancelled with 30 days notice; on closure we export your data and delete it within 90 days. Messaging products are also subject to Meta and WhatsApp Business policies, which we do not control.
Third-party services
Most builds touch services we do not own — payment gateways, Meta and Google platforms, courier and mapping APIs, SMS providers, app stores. We build to their documented behaviour, but their pricing, policies, review decisions and outages are theirs.
Where such a change breaks something we built, fixing it is normal chargeable work unless it falls inside the post-launch window or an active retainer.
Testing, launch and the support window
Every project is tested in-house before release and shown on staging from week two. On launch you get 30 days in which defects — anything that does not behave as the agreed scope says it should — are fixed at no charge.
New features, changes of mind, third-party breakages and content edits are not defects. After the window, most clients move to a care and growth retainer covering hosting, monitoring, small features and campaigns.
Confidentiality and portfolio use
Both sides keep the other’s commercial and technical information confidential, during the engagement and after it. We are happy to sign your NDA.
We would like to show the work, but only with your permission: we ask before naming you, publishing a screenshot or quoting a number, and we publish outcomes as you approve them. Say no and the project simply does not appear.
Warranties and limits of liability
We warrant that work is performed with reasonable skill and care by qualified people, and that deliverables materially match the agreed scope. We do not warrant that software will be free of every defect, or that any specific business result — traffic, rankings, leads or revenue — will follow.
To the extent permitted by law, our total liability for any claim is limited to the fees you paid us for the deliverable in question in the preceding twelve months, and neither side is liable for indirect or consequential loss, including lost profit or lost data where backups were available. Nothing here limits liability for fraud, wilful misconduct or anything that cannot be limited by law.
Ending an engagement
Either side may end an engagement with 30 days written notice. You pay for work completed and costs already committed; we hand over source, credentials, documentation and any work in progress within 15 days of the final invoice being settled.
Either side may end it immediately for material breach that is not fixed within 15 days of written notice. We would rather tell you early that a project is not working than let it drift.
Governing law and changes
These terms are governed by the laws of India, and the courts at Surat, Gujarat have jurisdiction. Before either side litigates, we agree to attempt resolution in good faith — a conversation between principals first, mediation second.
We may update these terms; the effective date above changes when we do, and active clients are notified by email. The version in force is the one published when your contract was signed.