Terms of service

Who these terms apply to

These terms cover the work Planorah Technologies does for you — websites, mobile and TV apps, CRM and custom software, integrations, and the Google presence work that goes with them. They apply from the moment you accept a quote, whether by email, on WhatsApp or in a signed document.

Where you and we have signed a separate project agreement, statement of work or NDA, that document governs and these terms fill in anything it does not mention. Planorah Technologies is a software studio based in Ludhiana, Punjab, India.

Quotes and estimates

We quote a fixed price against a written scope — a document listing the screens, the features, the platforms we will ship to, and the things explicitly excluded. The price covers what that document says and nothing implied around it. If a requirement is not written down before work starts, it is a scope change rather than an oversight on our part.

Quotes are valid for thirty days from the date we send them. After that we may re-issue at a different price, usually because third-party costs such as hosting, developer accounts or API plans have moved. A quote is an offer, not a booking — your place in our schedule is held when the first milestone payment reaches us.

Any timeline in a quote is our honest estimate based on the scope as written and reasonable responsiveness on your side. It is a commitment we work hard to hold, not a guarantee, and it moves if the scope grows or approvals stall.

Payment

Projects run on milestones set out in the quote. The usual split is 40% to begin, 30% when the build reaches a version you can test, and 30% on handover before the work goes live. Longer projects are broken into more milestones so the work never runs far ahead of the payments, or behind them.

Invoices are payable within seven days unless the quote says otherwise. Amounts are in Indian rupees and exclusive of GST and bank charges, which are added where they apply. We may pause a project where an invoice is more than fifteen days overdue, and we will tell you before we do rather than quietly stop working.

Milestone payments already made are not refundable, because they pay for work already done. Where we have not started, we return what you paid.

Scope changes

A scope change is anything that adds to, removes from or materially alters what the agreed scope describes — a new screen, a new integration, another platform, a rule that changes how an existing feature behaves, or a redesign of something already approved. Fixing a defect in what we built is never a scope change.

Small adjustments such as copy edits, spacing, swapping an image or adding a field to an existing form, we absorb without paperwork. Anything larger is written up as a change note stating the extra cost and the effect on the launch date. We do not begin that work until you approve the note in writing, and it appears as its own line on the invoice.

What we need from you

Your side of a project affects the launch date as much as ours does. Specifically we need:

• Content — text, logos, images, product data and anything else that has to appear, in a usable format.
• Access — logins or admin rights for hosting, domains, developer accounts, payment gateways and any system we have to connect to.
• A decision-maker — one named person who can approve a design and answer questions without assembling a committee.
• Timely feedback — consolidated comments on each review within five working days.

Where you supply content, you confirm you hold the rights to use it. If a delay on your side runs past two weeks, we may reschedule the remaining work around other commitments and revise the launch date. We will flag that when it starts to matter, not afterwards.

Ownership of the work

On receipt of the final payment, everything we made specifically for you becomes yours outright — source code, design files, database schema and documentation, delivered into your own repository and accounts. There is no ongoing licence fee and nothing is held back as leverage.

Two carve-outs, stated plainly. First, we keep ownership of our own general-purpose libraries, components and internal tooling that existed before your project; you receive a perpetual, irrevocable, royalty-free licence to use and modify them as part of your software. Second, third-party open-source components stay under their own licences, which we list at handover. Until final payment is made, the work remains ours.

We may describe the project and show screenshots in our portfolio. Ask us not to and we will not.

Third-party services

Most projects depend on services we do not run — hosting, app stores, payment gateways, the WhatsApp Business API, Google, mapping, SMS and email providers. You contract with those providers directly and pay their fees at their price. We never mark them up, and their terms, uptime and pricing changes are theirs rather than ours.

We are not responsible for a third party changing its API, its pricing or its rules, or for an app store rejecting or delaying a submission on grounds outside our control. We will do the work to get a submission through. Where a change at a third party forces part of the system to be rebuilt, that is quoted as new work.

The 30-day fix window

For thirty days after the work goes live, we fix defects at no charge. A defect is the software not behaving the way the agreed scope says it should — broken flows, errors under normal use, layouts that fail on a device we committed to supporting. You report it, we fix it, with no limit on how many.

The window does not cover new features, changes you decided on after launch, content updates, training beyond the handover session, or problems caused by someone else editing the code, changing a third-party service or altering server configuration. Those are quoted as normal work. After thirty days, support continues on a monthly retainer or hourly, whichever suits you better.

What we warrant, and what we do not

We warrant that the work will be performed with reasonable skill and care by people competent to do it, that it will match the agreed scope, and that we have the right to hand it over to you. That is a real commitment and we stand behind it.

We do not warrant that any software is free of every defect, that it will run without interruption, or that it will produce a particular commercial result — more traffic, more sales, a specific search ranking. Nobody honest warrants those things, and you should be wary of anyone who does.

Our total liability for anything arising out of a project is limited to the amount you have paid us for that project. Neither side is liable to the other for indirect or consequential loss, including lost profits, lost business, lost data or lost goodwill. Nothing here limits liability for fraud, or for anything that cannot lawfully be limited under Indian law.

Confidentiality

We treat what you tell us about your business as confidential and we do not discuss it outside the people working on your project. We will sign your NDA or send you ours, and we are glad to do that before you describe the idea rather than after. Confidentiality survives the end of the project.

The same runs in the other direction: our quotes, pricing and internal documents are confidential to you.

Ending a project

Either side can end a project in writing. If you end it, you pay for the work completed to that point plus anything already committed on your behalf, and we hand over everything produced so far along with the accounts and access — even where the project is unfinished. If we end it, which has to be for a serious reason such as non-payment or being asked to do something unlawful, you pay only for completed work and the handover is the same.

Nothing about ending a project takes your accounts, domains or data away from you. They were in your name throughout.

Governing law

These terms, and any project carried out under them, are governed by the laws of India. The courts of Punjab, sitting at Ludhiana, have exclusive jurisdiction over any dispute arising from them.

Before either side goes near a court, both agree to spend thirty days trying to settle the matter in conversation. In our experience that has always been enough.

These are our standard terms, written to be read rather than survived. Where a signed project agreement, statement of work or NDA between us says something different, that document takes precedence over this page. This is a plain-language account of how we work and not legal advice — if a project matters enough to you, have your own lawyer read the agreement before you sign it.