Terms of service
Two different things live on this page: the terms for using this website, and the standing basis on which we work. A signed contract for a specific project always overrides this page.
Using this website
You may read, print and quote from this site with attribution. You may not copy the site wholesale, republish it as your own, or use it to train a model that reproduces it. The text, structure and images on under2.com belong to Under2 Company Limited unless a page says otherwise.
Everything on this site is published in good faith and may be out of date. Nothing here is an offer capable of acceptance, a warranty, or advice for your specific situation. Price ranges are planning figures, not quotations.
How work is agreed
Nothing binds either side until there is a written quotation, accepted in writing or by email. That document names the scope, the price, the payment milestones and the date. Where this page and that document disagree, the document wins.
- You describe the problem. We reply in writing with an approach and a range.
- A discovery step produces three documents: what the system must do, what it explicitly will not do in this phase, and how both sides will know it works.
- A fixed quotation follows, with the out-of-scope list written down.
- Work proceeds in visible increments against that scope.
- An acceptance gate has to pass before anything goes live.
- Support or handover, whichever the contract says.
A list of what a project will not do is not defensive paperwork. It is the only way both sides can agree later on whether something is a fix or a new piece of work, without either side feeling misled.
Changes to scope
Requests that fall outside the agreed scope are welcome and are quoted separately rather than absorbed silently or refused outright. We will tell you the cost and the effect on the date before doing the work, not after.
If a change would put the launch date at risk, we say so at the point you ask, and the decision is yours.
Payment
Project work is invoiced against the milestones in the quotation. Platform subscriptions are invoiced in advance for the period stated in the agreement. Payment gateway and bank charges are passed on at cost and shown separately, never marked up.
Invoices are payable within the period stated on them. Work on a late account may be paused, and if it is we will tell you before it happens rather than letting a deadline slip without explanation.
Who owns what
| Type of work | Ownership on final payment |
|---|---|
| Custom build | Yours, including the repository, once the final invoice is paid |
| Content and images you supplied | Yours throughout |
| Content we wrote for you | Yours on final payment |
| Under2 platform products | Ours, licensed to you for the term of the agreement |
| Generic components and libraries reused across clients | Ours, licensed to you perpetually for use in the delivered system |
| Third-party software in the build | Its own licence, listed in the handover |
Which model applies to your project is stated in the quotation. We do not leave ownership ambiguous and then argue about it at the end.
Support, and the limits of it
A support agreement states response times and what it covers. Without one, support is best-effort, and we say that rather than implying a commitment we have not made.
Under2 does not control the availability of banks, payment gateways, app store review, third-party booking platforms, channel managers, or the hosting a client chooses to run on. Where one of those fails we will help, but we cannot warrant their uptime.
Liability
Our liability under any engagement is limited to the fees paid for that engagement in the twelve months before the claim. We are not liable for lost profit, lost bookings or indirect loss.
This is the standard position. It is negotiable for larger engagements and is settled in the contract, not on this page.
Ending an engagement
Either side can end a project engagement with written notice. Work completed and in progress up to that point is invoiced, and everything built to that point is handed over — code, content, credentials and data — under the ownership terms above.
For platform subscriptions the notice period is in the agreement. Your booking, customer and product data is exportable in a standard format on request, during the term and after it. An exit that is difficult on purpose is not something we would want to be on the other side of, so we do not build one.
Law
Governing law
These terms and any engagement are governed by the law of Vietnam, and the courts of Vietnam have jurisdiction, unless a signed contract says otherwise.
This page takes effect on 9 September 2026. Changes are published here with a new effective date.
What travel operators ask us most
Is a price on this website binding?
No. Ranges published on this site are planning figures. Only a written quotation for your project is binding, and it states exactly what is included.
Do we own the code you write for us?
For a custom build, yes, on final payment, and the repository is handed over. Platform products remain ours and are licensed to you, which is what makes a subscription price rather than a build price possible.
The quotation says which of the two applies before you sign anything.
What happens if we want to leave?
Your data is exported in a standard format and the notice period in the agreement applies. We do not hold data hostage and we do not charge an exit fee.
Can these terms be negotiated?
Yes, for engagements where it is proportionate. Liability caps and support terms in particular are commonly adjusted, and the negotiated version is what governs.
Read next
Tell us what you are trying to run
What you sell, what you use today, and what is breaking. You get a written answer with an approach and a price range - not a brochure.