Terms & Conditions

By browsing the Website, sending an enquiry, or hiring us for Services, you accept these Terms. If you do not agree, please do not use the Website. Please also do not hire us for our Services.

• "Client" means a person or firm that hires myonestopsolution for Services.
• "Deliverables" means the exact outputs — code, designs, content, setups, docs — that a Project Agreement lists as being handed to the Client.
• "Client-Supplied Materials" means content, logins, data, logos, copy, images, or access the Client gives us to use in a project.
• "Pre-Existing IP" means tools, frameworks, code libraries, parts, templates, or know-how. myonestopsolution or another party owned or held rights to these before a given project began.
• "Third-Party Components" means open-source software, licensed libraries, plugins, SaaS tools, or other outside materials. These are built into a project under their own license terms.

The Website exists to tell you about our Services and to let you reach us. You agree not to misuse it. That means no attempts at access you are not allowed, and no scraping content to compete with us. It also means no sending harmful code, and no getting in the way of how the Website normally runs.

Service outlines, packages, and prices on the Website are starting points for talk, not fixed offers. A quote or proposal we send you becomes binding once you accept it in writing, including by email. Together with any SOW or Project Agreement, that accepted quote then sets the fixed scope and money terms for the project.

Each project is set by its own SOW or a similar written scope. Work not named in that SOW sits outside scope. It may be treated as a change request under Section 8.

Work starts once the given proposal or SOW is accepted. Where needed, it also waits on any agreed deposit, and on any data or access needed to begin (see Section 7).

• Giving prompt feedback, sign-offs, and calls needed to keep the project moving.
• Giving true content, logins, and access the project needs — for example, domain registrar access, hosting, third-party API keys, and brand assets.
• Making sure the Client has the right to use and hand over any Client-Supplied Materials (text, images, logos, data). This also means making sure that doing so does not step on someone else's rights.
• Checking Deliverables and giving feedback within the time set in the Project Agreement.

We are not on the hook for delays, flaws, or legal claims. This applies where they come from wrong, missing, or unlawfully given Client-Supplied Materials.

Timelines set in a proposal or SOW assume the Client helps on time. Delays from late feedback, late content, late access, or late pay may push the timeline out to match. Such delays do not count as a breach by myonestopsolution.

Work asked for outside the agreed scope is a "change request." This covers new features, extra pages or screens, new hookups, or design shifts made after sign-off. A change request may bring added cost and timeline shifts, but both sides must agree to these before the change request starts.

Payment plans, milestone amounts, deposit rules, taxes (including GST), and other money terms shift by project size and type. These will be set in the given proposal, quote, invoice, SOW, or Project Agreement.

Unless the Project Agreement says something else, three rules apply. First, invoices are due on the date shown on the invoice. Second, late pay may lead to work or delivery being paused until pay comes in. Third, work already done and milestones already handed over must be paid for. This holds even if the Client later chooses not to go on with the project.

Either side may end a live project on written notice as set in the Project Agreement. Where it is silent, fair written notice applies instead. On ending, the Client pays for work done and costs fairly spent up to that date. We, in turn, will make a fair effort to hand over Deliverables done by that date, as long as pay is up to date.

See our Refund / Cancellation Policy for how refunds work.

The given proposal or SOW sets how many review or edit rounds a project includes. Deliverables count as accepted if the Client does not raise real issues within the review time set in the Project Agreement. If none is set, that review window is 7 business days from delivery.

Post-launch bug fixes, ongoing upkeep, and Annual Maintenance Contracts (AMC) are their own services, billed under their own plan terms. Hosting, domain sign-ups, and outside plans — email tools, SaaS apps, payment gateways, SMS/WhatsApp API credit, cloud setup, and the like — are billed on their own. This is unless they are part of a live upkeep/AMC plan or agreed some other way. These items usually sit in the Client's own accounts. Their uptime, price, and terms are set by that outside provider, not by us.

Who owns Deliverables, Pre-Existing IP, Third-Party Components, and Client-Supplied Materials follows the setup in our Intellectual Property Notice. Where it names IP terms directly, the Project Agreement applies too. In short: Client-Supplied Materials stay the Client's, and Third-Party Components stay under their own licenses. Pre-Existing IP and common tools or parts we reuse across projects stay ours. The Client, though, usually gets a license to use them as built into their Deliverables. Custom-built Deliverables are handed over or licensed to the Client as set in the Project Agreement. It may shift from project to project.

Each side agrees to keep the other's non-public business, tech, and money data private, and to use it only for the project. Detailed privacy duties may sit elsewhere — in its own non-disclosure deal (NDA), or the privacy clause of the Project Agreement. That includes how long they last and any exceptions. Where that other deal is more specific, it wins over this broad Section. Note that this public Website and its Privacy Policy do not, on their own, work as an NDA.

A project may handle personal data owned by the Client's own customers or users. Where it does, the given Project Agreement or its own data deal sets each side's data-safety duties. We use fair, sound safety steps that suit each project's nature and the Client's own instructions. We do not promise that any system is safe from every possible security event.

A project may use AI or automation. Where it does, outside AI providers may be part of it, and their own terms apply on top of the Project Agreement. AI output may need a human check before it goes live. We do not promise the accuracy, originality, or fit of AI-made content or code beyond what the Project Agreement states.

Many projects tie into outside APIs, platforms, or systems — payment gateways, cloud hosts, marketplaces, CRMs, messaging APIs, and AI providers, among others. We are not on the hook for outages, price shifts, rule changes, or these outside tools shutting down. That said, where it makes sense to us, we will help deal with the fallout. This is done as part of ongoing work.

Deliverables are built and checked against the browsers, devices, and OS versions named in the Project Agreement. If none are named, current major browsers at delivery time apply instead. We do not promise Deliverables will work on older or unlisted setups, unless we agree to that on its own.

Except where a Project Agreement says something else in clear terms, Services and Deliverables come "as is" and "as available." To the fullest limit the law allows, this comes with no promise of any kind, spoken or implied. That covers implied promises of fit quality, fit for a given purpose, or that it does not clash with someone else's rights. We do not promise Deliverables will be free of errors, run without a break, or meet every unstated hope.

To the fullest limit the law allows, and except where a Project Agreement says something else in clear terms, two caps apply. First, neither side owes the other for indirect, side, special, knock-on, or punishing damages. This covers lost profit, revenue, data, or business chances. Second, our full total liability from a project will not pass one amount. That amount is what the Client actually paid us for that project in the twelve (12) months before the claim. Nothing in these Terms caps liability that the law says cannot be capped.

The Client agrees to indemnify us and hold us harmless from claims tied to Client-Supplied Materials. The same duty covers the Client's use of Deliverables against the law or these Terms. It also covers Client instructions that lead us to infringe someone else's rights. In turn, we agree to indemnify the Client for claims that our custom-built Deliverables directly infringe someone else's IP rights, as delivered and used as meant. This sits under the caps in Section 20, and needs the Client to tell us about the claim right away.

Neither side owes the other for delay, or for a failure to perform, caused by events past its fair control. This covers natural disasters, internet or infrastructure outages, government action, or wide outside service failures.

Some terms, by their nature, should live on past ending. This covers IP, privacy, pay duties for work done, warranty limits, indemnity, and liability caps. These terms do live on past the end or expiry of these Terms or a Project Agreement.

These Terms sit under the laws of India. Courts with the right power at [JURISDICTION TO BE CONFIRMED] hold sole say over disputes tied to these Terms or a Project Agreement. The one exception is where it names a different forum or dispute path, such as arbitration or mediation.

We may update these Terms now and then. This shows up as an updated "Last updated" date. For a live project, though, the version of these Terms in force when the Project Agreement was signed keeps applying to that project. That holds unless both sides agree to something else.

• Email: myonestopsolution34@gmail.com
• Phone: 7410147498
• WhatsApp: 8459746807