Terms of Service

These Terms of Service govern your use of asematic.com and any work you commission from Asematic Technologies Private Limited ("Asematic", "we", "us"), a company registered in India and operating from Bhubaneswar, Odisha. By using this site or engaging us, you accept them.

Where a specification, statement of work or master services agreement signed by both parties says something different from this page, that signed document governs. These terms fill the gaps it leaves; they do not override it.

They are written for businesses. If you are commissioning work on behalf of a company, you confirm you are authorised to bind it. Nothing here is intended to limit any right you hold as a consumer that cannot be limited by agreement.

This website is published for information. There are no user accounts, no logins and nothing to subscribe to — the only thing you can submit is an enquiry form. You may read, print and share these pages freely.

What you agree not to do

• Attempt to gain unauthorised access to the site, its hosting, or any system connected to it.
• Probe, scan or test the site's security without our written permission.
• Send automated traffic that degrades the service for others, or submit forms by script.
• Scrape and republish our written content as your own — see Section 03.
• Use the site for anything unlawful, or to transmit malware.

We aim to keep the site available but do not guarantee uninterrupted access. We may change, suspend or withdraw any part of it without notice. It is provided as it stands.

The writing, design, photography, diagrams, logos and code that make up asematic.com belong to Asematic or to the people we licensed them from, and are protected by Indian and international copyright law. The Asematic name and mark are ours.

This section covers our own marketing website. It has nothing to do with the software we build for you — Section 09 governs that, and the answer there is that you own it.

You may quote short extracts with attribution and a link. You may not reproduce a page wholesale, or use our content to train a model that reproduces it as its own. If you would like to reference something at greater length, ask us — we usually say yes.

Anything you send us through a form or by email — a brief, a document, a message — stays yours. You grant us only the permission needed to read it, reply to it, and quote it internally while we work out whether we can help.

Nothing on this site is an offer capable of acceptance, and no page here quotes a price. An engagement exists only when we have both signed a specification, and not before.

The specification is written so you could hand it to another company and get comparable quotes. You are free to do exactly that. We would rather lose the work at that stage than be chosen on a document nobody could check.

Standalone audits and discovery engagements are available and are quoted separately. Where one is bought on its own, it is chargeable and its own scope says so.

The specification defines the work. Anything not named in it is out of scope — not refused, just not yet priced.

When you want something added or altered, we price the change and give you a revised delivery date before starting it. You decide whether to proceed. We do not begin chargeable work you have not approved, and we do not present a change as an invoice after the fact.

The same applies in reverse: if something in the specification turns out to be unnecessary, we say so and take it out rather than building it to protect the quote.

The price is fixed against the specification and billed against the milestones named in it. We do not bill hourly, and we do not require a retainer before beginning.

If an invoice is materially overdue we may pause work after giving you written notice and a reasonable chance to settle it. We will not withhold anything you already own — your repository and accounts are in your name and stay accessible to you throughout, including during a dispute.

Most projects that slip do so waiting on something only the client can provide. Naming those things is not a way of shifting blame; it is how the timeline is kept honest.

• A single named decision-maker who can approve work without a committee.
• Content, brand assets and credentials by the dates the specification sets.
• Feedback at each review stage, consolidated, within the agreed window.
• Access to any existing system we have to integrate with.
• Confirmation that anything you supply is yours to supply.

Where a delay on your side pushes the schedule, the delivery date moves by that much and we tell you at the time rather than at the end. Prolonged silence — a month or more with no response on a live project — lets us close the engagement under Section 14 and invoice for work completed.

Indicative durations are published on this site — roughly six to nine weeks for a website, twelve to sixteen for a SaaS product or CRM. They describe typical projects, not a commitment on yours. The date that binds is the one in your signed specification.

Neither party is liable for delay caused by something outside its reasonable control: an outage at a third-party provider, a change in law, a natural event, or a failure of infrastructure we do not operate. We will tell you as soon as we know and agree a revised date with you.

You own the source code, design files and documentation we produce for you, from the first commit — not on final payment, and not at handover.

This is the commitment we make everywhere else on this site, so it is written here as a term rather than left as marketing. Work is carried out in your repository and your accounts from the start, which is what makes the ownership real rather than a promise to transfer something later.

The one carve-out, stated plainly

We arrive with our own general-purpose building blocks — internal libraries, boilerplate, deployment scripts and the like — which we reuse across clients and continue to own. You receive a perpetual, irrevocable, royalty-free licence to use, modify and distribute them as part of your project, including if you later move to another team. What you cannot do is extract them and resell them as a standalone product.

This carve-out does not reach anything specific to your business: your logic, your data model, your designs and your content are yours outright.

We claim no lien over your work for non-payment. An unpaid invoice is a debt to be recovered as a debt, not a reason to hold your repository hostage.

Most projects depend on services we do not run — a host, a payment gateway, a mapping or messaging API, an app store. We will tell you which ones your project needs before you commit to it.

Those services are governed by their own terms, billed by them to you, and changed at their discretion. We are not responsible for their pricing, availability, or a decision by an app store to reject or remove a submission. Where such a change forces rework, it is handled as a scope change under Section 05.

Each of us will keep the other's non-public information confidential, use it only for the project, and protect it as carefully as our own. This holds for three years after the engagement ends, and indefinitely for anything that is a trade secret.

It does not apply to information that is already public, that the receiving party already held, that is independently developed without reference to it, or that must be disclosed by law — in which case we will tell you first if we are permitted to.

Where we process personal data on your behalf, you are the Data Fiduciary and we act on your instructions. Our own data handling is set out in the Privacy Policy.

We warrant that the work will be performed with reasonable skill and care, and that on delivery it will materially do what the specification says it does.

For 30 days after a deliverable is accepted, we correct defects in it at no charge — a defect being a failure to match the specification, not a request for something the specification did not cover. Report one and we will fix it.

Beyond that, we make no warranty that software will be error-free or uninterrupted, and we do not warrant any specific commercial outcome. In particular, no ranking, traffic level, conversion rate or revenue figure is promised by any page on this site or by any proposal, and none is guaranteed by us. Ongoing maintenance is available as a retainer and is quoted separately.

Neither party is liable to the other for indirect or consequential loss, or for loss of profit, revenue, goodwill, business opportunity or data, however it arises.

Our total liability arising out of an engagement, whether in contract, tort or otherwise, is capped at the total fees you have paid us for that engagement in the twelve months before the claim.

Nothing in this section limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot lawfully be limited.

Either of us may end an engagement on 30 days' written notice, or immediately if the other commits a material breach and fails to remedy it within 15 days of being told.

What happens then

• You pay for work completed and accepted up to that date, and for any third-party cost already committed on your instruction.
• We hand over everything in a state another team can pick up — which is mostly already done, since the work lives in your repository.
• You keep everything Section 09 says you own. Termination does not claw any of it back.
• The confidentiality, ownership, liability and governing-law sections survive.

We would rather tell you early that an engagement is not working than carry it to a deadline that will not be met. If we reach that view, you will hear it from us first.

Once a project is publicly live, we may name you as a client and show screenshots of what any member of the public can already see, in our portfolio and case studies.

We never publish anything confidential — no metrics, no internal screens, no commercial terms — without asking you first. If you would prefer we did not mention the work at all, tell us and we will not. Saying no costs you nothing and changes nothing else.

We may update this page. The effective date at the top always reflects the version you are reading, and the version in force when you signed your specification is the one that governs that engagement.

A change that materially affects a live engagement does not take effect on that engagement unless you agree to it.

These terms and any engagement under them are governed by the laws of India, without regard to conflict-of-law rules. The courts at Bhubaneswar, Odisha have exclusive jurisdiction.

Before either of us files anything, we agree to raise the issue in writing and give the other 30 days to resolve it. Most disagreements on a software project are about expectations rather than law, and are settled by re-reading the specification together.

Questions about these terms, about a quote, or about anything on this page go to the same place. hello@asematic.com is read by the people who can answer, and we reply within one business day.