Skip to content
VILOHITTECH Back to site

Legal — 02

Terms of Use

The rules for using this site and the terms on which we take on work — including what happens when a payment gateway, messaging provider or AI model is part of the build.

Last updated: 7 September 2026 Applies to: vilohittech.in and our client engagements

On this page

  1. About these terms
  2. Who you are contracting with
  3. Our services and how engagements work
  4. Fees, taxes and payment
  5. Your responsibilities
  6. Intellectual property
  7. Confidentiality
  8. Third-party services: payments, messaging, cloud
  9. AI features and generated output
  10. Acceptable use of this website
  11. Warranties and disclaimers
  12. Limitation of liability
  13. Indemnity
  14. Term, suspension and termination
  15. Force majeure
  16. Governing law and disputes
  17. Changes to these terms
  18. Contact

01About these terms

These terms govern your use of vilohittech.in and, where no signed agreement says otherwise, the services we provide. By using this site or engaging us, you accept them.

A signed proposal, statement of work or master services agreement always wins. Where such a document conflicts with these terms, that document applies to the engagement it covers, and these terms fill the gaps.

02Who you are contracting with

  • Entity: Vilohit Technology Private Limited
  • Place of business: HSR Layout, Bengaluru, Karnataka 560102, India
  • GSTIN: 29AAKCV0202C1ZR
  • Email: hello@vilohittech.in

“We”, “us” and “Vilohit Tech” mean that entity. “You” and “client” mean the person or company using this site or buying our services. If you accept these terms for a company, you confirm you are authorised to bind it.

03Our services and how engagements work

We provide product design and software engineering services: discovery, UI/UX, mobile and web development, backend and cloud engineering, AI/LLM integration, and post-launch support.

  • Scope comes from a written document. Every engagement starts with a proposal or statement of work that lists deliverables, assumptions, timeline and price. Anything not listed is out of scope.
  • Changes go through change control. New requirements are quoted before they are built. We will not silently absorb scope, and we will not silently drop it.
  • Estimates are estimates. Dates assume you provide inputs, approvals and access when agreed. Delay on your side moves our dates by at least the same amount.
  • We may use subcontractors for specialist work. We remain responsible for their output and bind them to the same confidentiality obligations.
  • Acceptance: unless the statement of work says otherwise, a deliverable is accepted if you do not report a material defect in writing within 10 business days of delivery.

04Fees, taxes and payment

Prices are quoted per engagement — fixed price for a defined scope, or a monthly/sprint rate where the roadmap is still moving. We do not publish rate cards because the number depends on scope, stack and timeline. Ask us and you will get a written quote.

  • Quotes are valid for 30 days and are exclusive of GST and other applicable taxes, which are added at the prevailing rate.
  • Typical structure: 40% advance, 40% at milestone, 20% on delivery. The statement of work sets the actual schedule.
  • Invoices are payable within 15 days. Late amounts may attract interest at 1.5% per month.
  • Third-party costs — cloud hosting, app-store fees, gateway charges, paid APIs, model usage, licences, SMS/WhatsApp charges — are yours, billed at cost or paid by you directly.
  • We may suspend work on an engagement whose invoice is more than 15 days overdue, after written notice.
  • Bank charges, payment-gateway fees and currency conversion costs on your payment are yours.

Refunds and cancellations are covered in our Refund & Cancellation Policy.

05Your responsibilities

  • Give us accurate requirements, and a named decision-maker who can approve work.
  • Provide access — accounts, repositories, test data, third-party credentials — needed to do the work, and revoke it promptly when we hand over.
  • Review and respond to deliverables within the agreed window. Silence stalls a project.
  • Make sure you have the rights to everything you give us: content, logos, fonts, data sets, third-party code. You confirm that our agreed use of it will not infringe anyone's rights.
  • Comply with the law that applies to your product — licensing, financial regulation, consumer protection, data protection. We build what you specify; we are not your compliance function, and for anything regulated (trading, lending, payments, health) you must take your own regulatory advice.
  • Own your production environment after handover, including backups, keys and monitoring, unless you have bought a support retainer from us.

06Intellectual property

What you get

On full payment of all amounts due for an engagement, we assign to you the intellectual property in the deliverables built specifically for you under that engagement — source code, designs and documentation. Until then, you have a licence to use them for evaluation and internal testing only.

What we keep

  • Our pre-existing know-how, tools, libraries, boilerplate and internal frameworks, and any general improvement to them. You get a perpetual, worldwide, royalty-free licence to use those components as embedded in your deliverables.
  • The right to reuse general skills, techniques and ideas learned on the engagement, without using your confidential information.

Open source and third-party components

Deliverables may include open-source and commercially licensed components. Those stay under their own licences, and we will list the material ones on request. You are responsible for continuing to comply with them, including any licence fees after handover.

Publicity

We may describe the work at a high level in our portfolio and use your name and logo as a client, unless the contract says we may not. We never publish confidential details, metrics or code without your written approval. Tell us in writing at any time and we will take it down.

07Confidentiality

Each side will keep the other's non-public information confidential, use it only for the engagement, protect it as carefully as its own confidential information, and limit access to people who need it and are bound by equivalent obligations.

This does not apply to information that is public through no fault of the receiver, was already lawfully known, is independently developed, or must be disclosed by law — in which case the receiver gives notice first, where it is lawful to do so.

These obligations continue for three years after the engagement ends, and indefinitely for trade secrets and personal data. We will sign your NDA if you prefer your own form.

08Third-party services: payments, messaging, cloud

Most products we build depend on services neither of us controls: payment gateways, banks and UPI rails, SMS/WhatsApp/email providers, cloud platforms, map and identity APIs, app stores and AI model providers.

  • Their terms apply to you. Where an integration runs under your merchant, sender or developer account, you contract directly with that provider and must comply with its terms, KYC/onboarding requirements and acceptable-use rules. We can implement to the documented API; we cannot grant, guarantee or preserve your account with them.
  • Approval is theirs, not ours. Gateway onboarding, DLT sender-ID and template registration, WhatsApp Business verification and app-store review are decided by those providers. We will prepare what they ask for, but we cannot promise an outcome or a date.
  • Outages and changes are outside our control. We are not liable for a provider's downtime, failed or delayed settlement, chargebacks, price increases, rate limits, deprecated APIs, policy changes, account suspension or data loss on their side. Where a provider makes a breaking change after handover, adapting to it is new work, quoted separately.
  • Regulated activity stays yours. Handling money, credit, securities, insurance or health data may require licences and audits. You are the regulated party; you are responsible for obtaining and keeping those approvals and for the correctness of regulatory reporting. Our software is a tool, not a licence.
  • PCI scope. We build integrations so that card data is entered on the gateway's hosted page or SDK and never touches your servers or ours. If you insist on a flow where card data reaches your systems, you accept the PCI-DSS obligations and audit costs that follow, and you must tell us in writing.
  • Messaging consent is yours. You are responsible for having a lawful basis and, where required, prior opt-in for the messages your product sends, and for honouring opt-outs. Penalties for unsolicited messaging fall on the sender of record.

09AI features and generated output

Where we build AI features — content generation, assistants, classification, summarisation — you should understand and accept the following:

  • Model output can be wrong, biased, out of date or duplicative, even with good prompts and retrieval. Output is a draft, not a verified fact; if accuracy matters, keep a human in the loop. We build the review step when you ask for it.
  • You decide what data goes to a model provider and under which of their plans. We will implement the provider and configuration you approve, including no-training and retention settings where the provider offers them.
  • Rights in AI-generated output can be uncertain in law and vary by jurisdiction. We do not warrant that generated text, images, audio or code is original, non-infringing or protectable.
  • Usage-based model costs are yours, and they vary with traffic. We will build cost controls and alerts, but we do not underwrite your model spend.
  • You will not use what we build to generate unlawful content, to impersonate real people or organisations, or in any way that breaches the model provider's usage policies.

10Acceptable use of this website

You agree not to:

  • probe, scan or test the vulnerability of this site, or breach its security, except as invited in section 13 of our Privacy Policy;
  • scrape, mirror or reuse the site's text, design or code beyond normal browsing, or use it to train a model, without our written permission;
  • send us malware, or use our forms and email for spam, bulk solicitation or anything unlawful;
  • misrepresent who you are or which company you represent.

All content on this site — text, layout, code, logos and the Vilohit Tech name — belongs to us or our licensors. You may link to it and quote short extracts with attribution.

11Warranties and disclaimers

We warrant that we will perform our services with reasonable skill and care, by suitably experienced people, and that deliverables will materially conform to the agreed specification for 30 days after acceptance. Our remedy for a breach of that warranty is to fix the defect at no charge — report it in writing within the warranty period.

That warranty does not cover problems caused by:

  • changes made by you or a third party to the deliverables after handover;
  • your infrastructure, data, content or configuration;
  • third-party services, APIs, devices or OS versions changing or failing;
  • use outside the agreed specification or documented environment.

Beyond that warranty, and to the extent the law allows, this site and our services are provided “as is”. We do not warrant that software will be error-free or uninterrupted, that it will meet requirements you never told us about, or that it will produce any particular commercial result. We give no warranty about the accuracy of AI-generated output.

12Limitation of liability

Nothing here limits liability that cannot be limited by law — including liability for death or personal injury caused by negligence, or for fraud or fraudulent misrepresentation.

Subject to that:

  • neither side is liable for indirect or consequential loss, or for lost profit, revenue, business, goodwill, anticipated savings, or loss or corruption of data, however caused;
  • our total liability arising out of or in connection with an engagement is capped at the fees you actually paid us for that engagement in the 6 months before the claim arose;
  • we are not liable for losses arising from third-party services as described in section 08, from your failure to keep backups, or from your use of a deliverable after you or someone else modified it;
  • any claim must be brought within 12 months of the date you became aware of the facts giving rise to it.

13Indemnity

You will indemnify us against claims, losses and reasonable costs arising from: content, data or materials you supplied; your use of a deliverable in breach of these terms or of any law; your breach of a third-party provider's terms; regulatory action relating to your business activity; and messages your product sends without a lawful basis or required consent.

We will indemnify you against a third-party claim that a deliverable we built, used as agreed and unmodified, infringes that party's intellectual property in India — provided you tell us promptly, let us handle the defence, and cooperate. This does not apply to open-source or third-party components, to your own content, or to combinations or modifications we did not make. Our liability under this indemnity is subject to section 12.

14Term, suspension and termination

  • Either side may terminate an engagement for convenience on 30 days' written notice, unless the statement of work says otherwise.
  • Either side may terminate immediately if the other commits a material breach and does not fix it within 15 days of written notice, or becomes insolvent.
  • On termination you pay for work performed and costs committed up to the termination date. See the Refund & Cancellation Policy for how advances are treated.
  • On termination we hand over the code and assets you have paid for, delete or return your confidential data within 30 days on request (except records we must keep), and revoke our access to your systems.
  • Sections on confidentiality, IP, liability, indemnity and governing law survive termination.

15Force majeure

Neither side is in breach for a delay or failure caused by something beyond its reasonable control — natural disaster, war, civil unrest, epidemic, strike, failure of power or internet infrastructure, government action, or a large-scale outage at a cloud, payment or telecom provider. The affected side will notify the other and resume as soon as it reasonably can. If the event lasts more than 60 days, either side may terminate the affected engagement.

16Governing law and disputes

  • These terms and any engagement are governed by the laws of India.
  • We will first try to resolve any dispute by discussion between senior people on both sides within 30 days.
  • If that fails, the dispute goes to arbitration by a sole arbitrator under the Arbitration and Conciliation Act, 1996. The seat and venue is Bengaluru, Karnataka, and the language is English. The award is final and binding.
  • The courts at Bengaluru, Karnataka have exclusive jurisdiction over anything not subject to arbitration, including interim relief.

17Changes to these terms

We may update these terms. The version on this page when you engage us is the version that applies to that engagement; changes do not alter a signed statement of work. We update the “last updated” date on any change, and continued use of the site after that means you accept the new version.

18Contact

  • Email: hello@vilohittech.in
  • Address: Vilohit Technology Private Limited, HSR Layout, Bengaluru, Karnataka 560102, India

See also our Privacy Policy and Refund & Cancellation Policy.

Privacy Policy Terms of Use Refund & Cancellation Delete Your Data Contact
VILOHITTECH

Product engineering studio. HSR Layout, Bengaluru.

Privacy Terms Refunds Delete Your Data Contact
Services Work Process Stack Contact

© 2026 Vilohit Technology Private Limited.
CIN U62099KA2024PTC185886 · GSTIN 29AAKCV0202C1ZR

hello@vilohittech.in