Terms & Conditions

These terms cover two things: your use of zevoraenterprise.pro, and the general footing on which Zevora Enterprise takes on client work. People often take a page like this to be the contract. It is not. For any actual project, the quotation, proposal, statement of work or signed agreement we settle with you carries the commercial terms, and on any point where it and this page disagree, it wins.

The Website Comes With a Few Rules

Using the site means accepting these terms

Continuing to use this website is your acceptance of these terms. If you would rather not accept them, the answer is to stop using the site. The page may be revised from time to time; whichever version is live on the day of your visit is the one that applies.

What the site may not be used for

You are welcome to read, print and pass on pages, whether for your own reference or while weighing up whether to work with us. The following are off limits:

• breaking into, or attempting to break into, the site, the hosting behind it, its source code or anything linked to it;
• scanning, probing, scraping or load-testing the site hard enough to degrade it for other visitors;
• planting malware, or anything else built to damage or disrupt the site or the people using it;
• lifting a substantial part of the site to republish or sell, or claiming our material as your own work;
• filling in the enquiry form with invented details, under a false identity, or as a channel for unsolicited sales pitches;
• conduct on the site that an applicable law or regulation forbids.

We can limit or cut off access to the site if that is needed to protect it, the people who visit it, or our business.

The content on it is ours

Copyright and related laws protect the words, layout, design, graphics, illustrations and code that make up this website, all of which belong to Zevora Enterprise or are used under licence. Reading, printing and sharing a page is fine. Copying large parts of the site into a publication of your own, or passing our material off as yours, is not.

Descriptions are information, not offers

Our pages describe services, technologies and ways of working so that you know what we do. They do not amount to an offer you can accept, nor to a quotation, price, cost or time estimate, nor to a promise that a given job is one we can take. Prices and delivery timelines are absent from the whole site for a simple reason: neither can be given honestly before we have read a brief.

Nothing Is Agreed Until It Is Written Down

An enquiry commits nobody

Writing to us, by the form or by email, creates no obligation for either party. We are free to turn down an enquiry, or not to quote, and need not explain why. Any proposal or estimate we produce reflects what we knew when we wrote it, lasts for the validity period printed on it, and can be revised if the real requirement turns out to differ from the one described. Personal details in an enquiry are handled as set out in our Privacy Policy.

Until scope is agreed in writing and both parties have accepted a quotation, proposal or contract, no work starts.

Scope is whatever the proposal says

What gets built, how it behaves, what is included and what is expressly left out are all fixed by the proposal or statement of work. If that document does not mention something, it is not in scope. A need that only appears later is treated as a change, not quietly absorbed.

Fees are set engagement by engagement

Every project or engagement is quoted on its own. The fee, what it pays for, the milestones, when invoices are raised, the currency and the taxes that apply are all stated in the relevant quotation, proposal or contract. Unless the document states that tax is included, taxes and statutory levies are charged in addition to the quoted fee. Bank and currency-conversion charges on a payment fall to the person paying. When an invoice goes unpaid beyond the agreed period, we can stop work and hold back further deliveries until it is settled.

This website cannot take a payment, because there is no checkout, cart or payment gateway on it. Card details are something we will never request, either by email or through the enquiry form.

A Project Runs on Obligations on Both Sides

Your side of the work

No development project succeeds on one side’s effort alone. When you engage us, you take on the following:

• requirements that are accurate, and prompt word from you when they change;
• the content, brand files, data and other inputs we need, together with confirmation that you have the right to use them;
• access to what the work touches, for example code repositories, hosting, developer accounts, domains and test devices, held in your own name wherever the platform insists on it;
• safe keeping of credentials, and removal of any access that is no longer needed after the work is finished;
• one named contact with the authority to answer our questions and take decisions;
• timely review of what we deliver, with feedback and approvals gathered into one reply, so that progress does not stall on a pending decision;
• compliance with whatever rules your regulator, platform or industry applies to software you release.

When a hold-up is caused by information, access or an approval we are still waiting for, the timetable and any knock-on cost are adjusted as the applicable agreement provides.

Changes are costed before they are made

Requirements shift during most projects, and that is expected. Any request that adds to the agreed scope, takes something out of it or materially reshapes it is a change. We will put its effect on effort, cost and schedule in writing, and the change goes ahead when you confirm. Until you do, we keep working to the scope already agreed.

Dates are estimates; acceptance is defined

A delivery date in a proposal is an honest estimate, resting on the scope known when it was written and on the assumption that what we need from you arrives on time. It is not a guarantee. Handover for review follows the method in the applicable agreement, which also sets the review window, the acceptance criteria and the procedure when a defect is reported.

Confidentiality runs both ways

In the course of working together, each party may see the other’s confidential material, from plans and data to source code, pricing and technical detail. Each will share it only with people who need it for the work, and will use it for the engagement alone. Excluded from this is anything that became public without a breach, was known beforehand, was developed independently, or has to be disclosed by law or by a competent authority. The duty continues after the engagement is over.

Platforms make their own decisions

A project may rest on services outside our control, such as app stores, cloud platforms, payment gateways, maps, push notifications and analytics tools. Each provider’s own terms apply, and you agree to them directly with that provider. Their decisions are not ours to answer for, including review outcomes, account suspensions, changes of policy or price, withdrawn features and outages. When a platform moves the goalposts after delivery, the work to catch up is a new piece of work.

Ownership Follows Payment, and Upkeep Is Extra

Deliverables made for you

The applicable agreement decides how rights in deliverables made specifically for you are assigned or licensed to you, and this normally happens once that work has been paid for in full. Before then, the deliverables are ours. We may refer to the type of work in general terms, but your name, your materials and your confidential details stay unpublished unless you give written permission.

Our own tools stay ours

Material we already had remains ours: our tools, frameworks, libraries, code patterns, templates, scripts and general know-how, along with any such material we create or refine while working for you. If some of it ends up inside a deliverable, you receive whatever licence is needed to use, run and adapt that deliverable for its intended purpose. We remain free to bring our general skill, experience and methods to other clients’ work.

Third-party components carry their own licences

Very little software is written entirely from scratch. Open-source and commercial libraries, SDKs, fonts, plugins, cloud services and APIs from other suppliers are normally part of it, and each comes under its supplier’s licence, which binds you as the user of the finished product. Recurring fees, subscriptions and per-seat licences for such components are yours to pay unless the applicable agreement provides otherwise, and the account usually sits in your name.

Maintenance is a separate arrangement

Building software and looking after it are different services. Maintenance, support, hosting and monitoring are provided only when the applicable agreement includes them, and that agreement then sets what is covered and how requests are logged and prioritised. If no such arrangement exists, we owe no continuing duty to watch, update or maintain software after delivery, although we are happy to quote for further work if you ask.

Advertising Work Has Conditions of Its Own

Risk Is Shared, and Capped

What we warrant

Our promise is that the work will be done with reasonable skill and care by people competent to do it, and that what we deliver will match the written specification in every material respect. We make no promise that software will never fail or pause, that every fault can be cured, that it will suit every device, browser and operating system now or in future versions, or that it will deliver a particular commercial outcome. So far as the law allows, we exclude every warranty, condition and term not written here, whether statute would imply it or anything else would.

Where liability stops

Some liability cannot lawfully be excluded or limited, such as liability for fraud or fraudulent misrepresentation, and nothing here tries to. With that exception:

• indirect and consequential losses are excluded, and so are lost profit, revenue, business, goodwill and expected savings, and lost or corrupted data, whatever caused them;
• across an engagement, the most we can be liable for is the cap written into the applicable agreement or, where it sets none, the fees you have actually paid us for the specific work the claim concerns;
• the website comes as it is, and relying on it or on anything published there is your own risk, as explained in our Disclaimer.

Your indemnity to us

You will cover us for claims, losses, liabilities and reasonable costs that result from content, data, materials or instructions you give us, from putting a deliverable to a use that was never agreed, from breaking these terms, or from breaking a third party’s licence or platform policy.

Events beyond anyone’s control

If something genuinely outside a party’s reasonable control causes delay or failure, that party is not liable for it. Think of fire, flood or other natural events, war, epidemic, strikes, civil unrest, government action, cyber attacks, or failures of power, telecoms and the internet. The party affected lets the other know as early as it reasonably can, and picks the work back up as soon as it is able to.

Endings, Disputes and the Fine Print

Suspending or ending an engagement

Ending an engagement follows whatever the applicable agreement says about it, and either party may do so on those terms. Three things allow us to pause work: an overdue invoice, access or information we need but cannot get, or a risk that carrying on would breach a law or a platform policy. Ending it does not cancel the bill for work already done or for costs properly incurred before the end date. On request, each party returns or deletes the other’s confidential material, keeping only what the law requires it to keep, and the provisions of these terms intended to outlast the engagement remain in force. Our Refund & Cancellation Policy explains how cancelling affects money already paid.

Indian law, and the courts at Rajkot

Indian law governs these terms and every engagement between us. Disputes fall within the exclusive jurisdiction of the courts at Rajkot, Gujarat, although either party may go to another court for urgent relief to protect intellectual property or confidential information. Neither party will start proceedings without first raising the problem in writing and making a genuine effort to resolve it directly.

Standard clauses

• Which document wins. If a signed agreement, contract, statement of work, proposal or quotation deals with something this page also deals with, that document takes priority as far as they conflict. Scope, deliverables, fees, milestones, payment schedule and timelines are settled in that document alone.
• Whole agreement. Together, the applicable agreement and these terms are the complete agreement on their subject, and they supersede what was said or written about it beforehand.
• Severability. Should any provision be found invalid or unenforceable, that provision drops out and everything else continues to apply.
• No waiver. A right that goes unenforced for a while is still a right.
• Assignment. Rights and obligations under an engagement cannot be handed to someone else without the other party’s written agreement, and that agreement will not be withheld unreasonably.
• Independent contractor. Our status is that of an independent contractor, and no partnership, joint venture or employment arises from these terms.
• Notices. A written notice can be emailed to contact.zevora@gmail.com, or delivered to whatever address the applicable agreement records for you.

Revisions to this page

We change these terms when our services, the website or the law make it necessary, and the date at the top marks the current version. An engagement you have already agreed is unaffected by later edits here: the document signed at the time continues to govern it.