TERMS & CONDITIONS

Clear terms for working with Nimble Technology.

These Terms describe the general conditions that may apply when you use our website, engage our services, commission development work or use Nimble Technology products.

Last updated: 24 September 2026Website · Services · Products

HOW THESE TERMS WORK

A signed proposal, order, invoice or service agreement may contain project-specific commercial terms.

Project-specific written terms take priority where they directly conflict with these general Terms.

Third-party platforms such as Meta, Google and WhatsApp also operate under their own terms and policies.

Products under testing may change before wider release.

No advertising, growth, ranking, revenue or business result is guaranteed unless expressly stated in writing.

Privacy and data processing are also governed by our Privacy & Data Policy.

ON THIS PAGE

Acceptance

01 · ACCEPTANCE

Using the website, products or services may make these Terms applicable to you.

These general Terms apply to the extent relevant to your interaction with Nimble Technology.

By using the Nimble Technology website, you agree to use it lawfully and consistently with these Terms.

When you purchase or request a service, the applicable proposal, quotation, invoice, statement of work or written agreement may form part of the contractual terms.

When you create or use an account for a Nimble product, additional product-specific terms, usage rules or privacy notices may also apply.

If you act for an organisation, you represent that you have appropriate authority to act on its behalf.

PROJECT-SPECIFIC TERMS

If a signed proposal or other written agreement contains terms that specifically conflict with these general Terms, the project-specific written terms will normally govern that particular matter.

02 · WEBSITE

Use of the Nimble Technology website

Website information is provided for general information about Nimble Technology, its capabilities, services and products. Product descriptions, feature previews, examples and illustrations may evolve over time.

You must not attempt to disrupt, attack, scrape abusively, reverse-engineer restricted systems or bypass website security.

You must not use website forms to distribute malware, spam, fraudulent content or unlawful material.

Information on the public website does not itself constitute a binding quotation, guaranteed specification or professional advice unless expressly stated.

03 · SERVICES

Services may include design, development, automation, marketing and technology work.

Technology services

Website development, software development, SaaS systems, internal tools, APIs, integrations, maintenance and related engineering.

Automation

Business workflows, WhatsApp integrations, API automation, CRM connections, notifications and operational systems.

Digital growth

Digital marketing, campaign management, landing experiences, performance reporting and related growth services.

Design & strategy

UI/UX, product structure, user journeys, visual interfaces, creative work and related consulting.

04 · SCOPE

The agreed scope is defined by the applicable commercial document.

A proposal, quotation, invoice, statement of work, email confirmation or other written agreement may define what is included in a project.

Deliverables, phases, features, timelines, revisions and prices should be interpreted according to the applicable written scope.

Features, integrations or deliverables not included in the agreed scope may require a separate quotation or change request.

Estimates may need adjustment where requirements materially change or previously unknown technical conditions are discovered.

Verbal conversations are useful for planning but should not override a clear written scope unless the change is subsequently confirmed.

05 · CUSTOMER RESPONSIBILITIES

Projects depend on timely, accurate and authorised customer input.

Provide accurate information, content, approvals, access and feedback reasonably required to perform the work.

Ensure that material, data, brands, images, databases and accounts supplied to Nimble may lawfully be used for the requested purpose.

Review deliverables and communicate material errors or requested changes within the workflow agreed for the project.

Maintain appropriate internal backups of important original materials unless backup responsibility is expressly included in the service.

Comply with applicable laws and third-party platform rules relating to the customer business, products, advertising and data.

CUSTOMER DELAYS

A project schedule may move where required content, approvals, credentials, payments, decisions or other customer dependencies are delayed.

06 · ACCOUNT ACCESS

Access to business accounts should be authorised and limited to what is necessary.

Customers should preferably provide official user, administrator, partner, delegated or OAuth access rather than sharing primary passwords.

This may apply to Meta Business Manager, Facebook, Instagram, Google Ads, Google Analytics, Google Business Profile, YouTube, hosting, domains, CRM systems, repositories and similar platforms.

The customer represents that it has authority to provide access to any account or system supplied to Nimble.

Access may be revoked or reduced when the relevant work is complete or no longer requires that level of permission.

PASSWORDS, OTPs AND SECRET KEYS

Customers should not send passwords, OTPs, UPI PINs, banking passwords, recovery codes, private keys or similar high-risk secrets through general website forms.

07 · DEVELOPMENT

Software and website development involves technical dependencies and evolving requirements.

Development scope

Functionality, pages, modules, integrations and technical deliverables are governed by the agreed project scope.

Existing systems

Where Nimble works with existing code, databases or third-party systems, unknown technical conditions may affect effort, timing or compatibility.

Development environments may differ from final production infrastructure.

Software may require ongoing maintenance because operating systems, browsers, APIs, dependencies and third-party services continue to change.

Migration, major upgrades, legacy remediation or work outside the original scope may be separately chargeable.

Acceptance criteria and testing procedures may be defined in the applicable proposal or project agreement.

08 · UI / UX & CREATIVE

Design is an iterative process within the agreed revision scope.

Initial concepts, wireframes, mockups, prototypes and creative directions may change during the design process.

The number of included revisions, where limited, should be defined by the relevant proposal or service package.

New concepts or material changes after approval may be treated as additional scope.

Final implementation may vary slightly across browsers, devices, operating systems, fonts or third-party rendering environments.

09 · DIGITAL MARKETING

Marketing services depend on market conditions, platform systems and customer inputs.

Nimble may provide campaign strategy, creative, advertising account management, landing pages, lead-generation workflows, reporting, social-media support or other digital marketing services.

Advertising budgets paid to platforms are generally separate from Nimble service fees unless expressly stated otherwise.

Customers remain responsible for the truthfulness and legality of claims relating to their products, services, prices and offers.

Campaign strategy and targeting may evolve based on performance, audience response and platform changes.

Reporting may rely on data supplied by advertising and analytics platforms and can be affected by attribution limitations, privacy controls or tracking restrictions.

10 · THIRD-PARTY PLATFORMS

Meta, Google, WhatsApp and other platforms control their own services.

Platform control

Third-party companies control account eligibility, APIs, billing, verification, ad review, limits, suspensions, policies and feature availability on their platforms.

External changes

APIs, pricing, permissions and technical behaviour may change or be discontinued without Nimble controlling the change.

Use of those platforms remains subject to their then-current terms, policies, developer requirements, advertising standards and privacy documentation.

11 · ADVERTISING RESULTS

Advertising and marketing outcomes are not guaranteed.

NO GUARANTEED ROAS, LEADS OR SALES

Unless a specific guarantee is expressly agreed in writing, Nimble does not guarantee a particular number of leads, sales, conversions, followers, rankings, impressions, revenue, return on advertising spend or other business result.

Results can depend on product-market fit, price, competition, geography, advertising budget, creative quality, website experience, sales follow-up and many other factors.

An advertisement approved previously may later be rejected, restricted or affected by a platform policy update.

Account suspension or platform enforcement decisions are ultimately made by the relevant third-party platform.

12 · AI & AUTOMATION

AI output and automated decisions require appropriate human oversight.

AI-generated text, analysis, images, recommendations or other outputs may contain errors, omissions or unexpected results.

Customers should review important AI output before using it for legal, financial, medical, employment, compliance or other consequential decisions.

Some AI or automation functions may depend on third-party providers and remain subject to their availability, limits and terms.

Automation should not be treated as a substitute for customer oversight where human review is reasonably required.

13 · NIMBLE PRODUCTS

Different Nimble products may be at different stages of development.

ConversiaX

ConversiaX is presented as a live Nimble product. Account plans, enabled features, messaging access, usage limits and platform dependencies may be governed by additional product terms.

Skoler

Skoler is currently described as testing / coming soon. Previewed functionality is not a promise that every feature will be available unchanged in the final release.

Arovia

Arovia is currently described as testing / coming soon. Healthcare functionality may require additional compliance, privacy and customer agreements before wider production use.

PRE-RELEASE PRODUCTS

Testing, beta, early-access or coming-soon products may contain incomplete functionality, temporary limitations or material changes before commercial release.

14 · SUBSCRIPTIONS & LICENCES

Product access may depend on the applicable plan, licence or subscription.

Product plans may differ by features, users, limits, integrations, storage, support or usage allowances.

Subscription prices and billing periods should be shown in the applicable order, invoice or product plan.

A customer receives only the access and licence rights expressly granted for the relevant product.

Accounts may not be resold, transferred or shared beyond authorised users unless the applicable product terms allow it.

15 · HOSTING, DOMAINS & CLOUD

Domains, hosting, cloud and external infrastructure may involve third-party costs.

Hosting & cloud

Hosting, servers, cloud databases, email, storage, backups and other infrastructure may be supplied by third-party providers.

Domains & licences

Domain registrations, renewals, SSL products, plugins, APIs, software licences and other external services may have separate provider charges and renewal conditions.

Unless expressly included, third-party renewal fees are separate from Nimble development or service fees.

Customers should ensure recurring third-party services remain paid where continued operation depends on them.

Provider outages or discontinued services may affect systems even where Nimble has implemented the integration correctly.

16 · PAYMENTS

Payment obligations are defined by the relevant quotation, invoice or subscription.

Project payments

Projects may use advance payments, milestones, monthly billing, retainers or another payment schedule described in the applicable commercial document.

Taxes & third-party fees

Applicable taxes and separately identified third-party costs may be charged where required by law or the agreed project terms.

Work may begin only after any required initial payment and dependencies have been received.

Delivery, production deployment or continued service may depend on payment of amounts that are due.

Nimble may pause affected work or services after reasonable notice when material invoices remain overdue.

17 · REFUNDS & CANCELLATION

Refund and cancellation treatment depends on the type and stage of work.

CHECK YOUR PROPOSAL OR PLAN

A project proposal, product plan, invoice or signed agreement may include specific cancellation or refund rules. Those specific terms should be reviewed first.

Payments for work already completed, delivered milestones or services already consumed are not automatically refundable.

Approved third-party purchases such as advertising spend, domains, hosting, licences, APIs or external subscriptions may be non-refundable or governed by the third-party provider.

If a project is cancelled after work begins, charges may remain due for work performed and non-cancellable commitments already made.

Refund eligibility for unused product subscription periods, where offered, will follow the applicable product plan or written agreement.

Nothing in these Terms removes any mandatory refund or consumer right that cannot lawfully be excluded.

18 · CHANGES & REVISIONS

Changes after scope approval may affect time and cost.

Minor clarifications within the existing scope may be handled as normal project work.

New modules, substantial redesigns, new integrations or changes to previously approved requirements may require additional estimation.

Rework caused by customer-requested changes after approval may be chargeable where it falls outside included revisions.

Change requests can affect the delivery schedule of both the changed work and dependent work.

19 · COPYRIGHT & OWNERSHIP

Ownership depends on what existed before the project and what the agreement grants.

Customer materials

The customer normally retains rights it already owns in its logos, trademarks, content, business data and other pre-existing materials.

Nimble materials

Nimble may retain ownership of pre-existing frameworks, internal tools, reusable libraries, generic components, techniques, templates and know-how unless otherwise agreed.

Ownership or licence rights in custom final deliverables should be determined by the relevant proposal or project agreement.

Source-code transfer is not automatically implied merely because a hosted system or software service has been delivered.

Where ownership transfer is agreed, it may be conditional on full payment of the applicable project amounts.

Third-party software, fonts, images, plugins, APIs and open-source components remain subject to their original licences.

20 · CUSTOMER CONTENT

Customers must have the right to use material they provide.

Customers represent that they have the necessary rights, permissions or licences for content supplied for publication or processing.

This includes logos, photographs, video, music, copy, databases, trademarks, customer lists and third-party creative material.

Nimble may rely reasonably on customer instructions regarding ownership or permission unless there is an obvious reason to question them.

21 · THIRD-PARTY SOFTWARE

External software and open-source components remain subject to their own licences.

Projects may use frameworks, packages, APIs, SDKs, libraries, plugins, fonts or other third-party technology. Those components may carry separate licensing obligations, usage limits, fees or attribution requirements.

Nimble does not obtain ownership of third-party technology merely by integrating it, and the customer does not receive broader rights than the relevant third-party licence permits.

22 · CONFIDENTIALITY

Non-public project information should be handled responsibly.

Each party should use reasonable care with confidential business, technical or commercial information received for the project.

Confidential information should be used only for legitimate work, administration, support or legal obligations related to the engagement.

Information already public, independently developed or lawfully obtained from another source may not be confidential in the same way.

More specific confidentiality obligations in an NDA or signed agreement take priority for that engagement.

23 · PRIVACY

Personal information is also governed by the Privacy & Data Policy.

Our Privacy & Data Policy explains how information may be collected, stored, processed and shared across Nimble websites, products and services.

Read Privacy & Data Policy

24 · SECURITY

Security is a shared responsibility.

Nimble

Nimble aims to use reasonable technical and operational safeguards appropriate to the service and information involved.

Customer

Customers are responsible for securing their accounts, passwords, authorised users and devices.

Providers

Third-party infrastructure and service providers are responsible for the security of their own platforms under their applicable terms.

No internet-connected system can be guaranteed completely secure or continuously available.

25 · SUPPORT & WARRANTY

Support, maintenance and warranty depend on the applicable service arrangement.

A project may include a defined support or defect-correction period where specified in the proposal.

Ongoing maintenance, content updates, new features, infrastructure administration or third-party updates may require a separate maintenance arrangement.

A defect is different from a new feature, changed requirement or issue caused by a third-party change.

Nimble cannot warrant uninterrupted operation of external platforms, APIs, hosting providers or internet infrastructure outside its control.

26 · SUSPENSION & TERMINATION

Services or access may be suspended or ended in certain circumstances.

Either party may end a project or recurring service according to the applicable written agreement or plan.

Nimble may suspend affected work or product access for material non-payment, security threats, unlawful activity or serious misuse.

Where reasonably possible, notice may be provided before a non-emergency suspension.

Ending a service does not automatically cancel amounts already due, completed work or non-cancellable third-party costs.

27 · ACCEPTABLE USE

Nimble systems must not be used for unlawful or abusive activity.

Do not use Nimble products or services for fraud, malware, unauthorised access, harassment, unlawful surveillance or illegal content.

Do not intentionally overload, attack, bypass limits or interfere with systems or other users.

Messaging, advertising and marketing features must be used in accordance with applicable laws and the relevant platform rules.

Nimble may investigate suspected misuse and take proportionate action where required to protect systems or users.

28 · DATA, EXPORTS & BACKUPS

Data availability and backup responsibilities depend on the product or service.

Product data

Export, deletion, retention and account-closing processes may differ between products and plans.

Backups

Backup scope, frequency and restoration capability depend on the infrastructure and service arrangement in use.

Customers should maintain copies of important source materials and business-critical information where appropriate.

Data may not remain recoverable indefinitely after account termination or deletion.

Any special data-export or migration requirement should be agreed before service termination where practicable.

29 · LIABILITY

Technology and business services involve risks that cannot be completely eliminated.

LIMITATIONS APPLY ONLY TO THE EXTENT PERMITTED BY LAW

Nothing in these Terms is intended to exclude or limit a liability or statutory right that cannot lawfully be excluded.

Nimble is not responsible for losses caused solely by customer instructions, unauthorised customer activity or information the customer failed to disclose where that information was reasonably necessary.

Nimble cannot control third-party outages, ad-platform decisions, API removals, policy changes, internet failures or external service suspensions.

To the maximum extent permitted by applicable law, Nimble should not be responsible for indirect, incidental or consequential losses arising solely from matters outside the agreed responsibility of the service.

Any project-specific limitation or liability cap contained in a signed agreement will apply to that engagement according to its terms.

30 · CUSTOMER-SUPPLIED MATERIAL & CLAIMS

Each party remains responsible for matters within its control.

Subject to applicable law and any more specific written agreement, a customer may be responsible for claims arising from unlawful content, misleading business claims, materials supplied without necessary rights, unauthorised account access requested by the customer, or unlawful use of the delivered system.

Nimble remains responsible for its own obligations to the extent required by the applicable agreement and law.

31 · EVENTS OUTSIDE REASONABLE CONTROL

Some delays or interruptions may be caused by events outside either party's reasonable control.

This can include major internet or cloud outages, natural disasters, government action, significant platform shutdowns, cyber incidents, labour disruption, infrastructure failure, war, civil disturbance or other extraordinary events that could not reasonably be prevented by the affected party.

The affected party should use reasonable efforts to reduce the impact and resume performance where practicable.

32 · GOVERNING LAW

These Terms are intended to operate under the applicable laws of India.

Unless a different governing law or dispute process is agreed in a specific written contract, these Terms are governed by the applicable laws of India.

Subject to applicable law and any written dispute-resolution agreement, disputes may be submitted to courts having competent jurisdiction in India.

PROJECT CONTRACTS MAY BE MORE SPECIFIC

Larger development, SaaS, data-processing or enterprise engagements may use separate agreements containing more specific jurisdiction, dispute-resolution, arbitration or governing-law provisions.

33 · CHANGES TO TERMS

These Terms may change as Nimble services and products evolve.

Check the updated date

Material changes should be reflected on this page. Existing signed contracts remain subject to their own amendment rules.

34 · CONTACT

Questions about these Terms?

Contact Nimble Technology

If your question relates to a specific proposal, invoice, product account or project, include enough context for us to identify the relevant engagement.

Contact Nimble

WORK WITH NIMBLE

Have a project or service question?

Share your requirement and we can define the specific scope and commercial terms for the engagement.

Start a conversation