Terms of Service
Last Updated: September 14, 2026
Welcome to FlowraPilot . These Terms of Service govern your use of our software, mobile apps, and platform interfaces designed to facilitate WhatsApp Business API communications.
1. The Service
FlowraPilot provides software-as-a-service tools that may help businesses manage leads, automate workflows, communicate with prospects or customers, integrate business systems, and perform other business processes.
The specific features available to you depend on your subscription plan, order form, and any separately agreed scope of work.
We may add, modify, improve, suspend, or discontinue features from time to time. We will use reasonable efforts to avoid materially reducing the core functionality of a paid Service during a subscription term.
2. Account and Access
You are responsible for:
- providing accurate account and business information;
- maintaining the confidentiality of account credentials;
- restricting access to authorized users;
- ensuring that users of your account comply with these Terms; and
- promptly notifying us of any unauthorized access or suspected security incident.
You are responsible for all activity conducted through your account, except to the extent caused by our breach of our security obligations.
You must not use the Service to violate applicable law, infringe third-party rights, distribute malicious software, interfere with the Service, or attempt to gain unauthorized access to systems or data.
3. Subscription and Fees
The Service may be offered on a monthly, annual, usage-based, or other subscription basis.
Subscription fees, implementation fees, usage charges, and other commercial terms will be specified on the applicable order form, invoice, or subscription plan.
Unless otherwise agreed:
- fees are payable in advance;
- fees are non-refundable once the applicable subscription period has commenced;
- taxes are additional where applicable;
- usage or third-party charges may be billed separately; and
- failure to pay amounts when due may result in suspension of the Service.
We may change subscription pricing for future renewal periods by providing reasonable advance notice.
4. Third-Party Services and Integrations
The Service may integrate with or depend upon third-party services, platforms, APIs, communication providers, CRM systems, cloud infrastructure, payment providers, or other external services ("Third-Party Services").
These may include, without limitation, WhatsApp, Meta, CRM platforms, messaging providers, email providers, cloud infrastructure providers, and other APIs or platforms.
Third-Party Services are operated by their respective providers and are subject to their own terms, policies, availability, and technical limitations.
FlowraPilot does not control Third-Party Services and is not responsible for:
- changes to third-party APIs or policies;
- third-party service outages or degradation;
- API rate limits;
- account suspension or verification failure;
- changes to messaging policies;
- third-party pricing changes;
- delivery failures via external pipelines;
- loss of deprecated functionalities.
We will use reasonable efforts to adapt the Service to material changes in supported third-party integrations where commercially and technically reasonable.
5. WhatsApp and Messaging Compliance
Where the Service is used with WhatsApp, Meta, or another messaging platform, the Customer is responsible for its use of that platform.
In particular, the Customer is responsible for:
- obtaining and maintaining all required user consent and opt-ins;
- ensuring that message content is lawful and appropriate;
- complying with applicable messaging, privacy, advertising, and communication laws;
- complying with WhatsApp, Meta, and other applicable platform policies;
- maintaining appropriate messaging frequency and accurate recipient lists; and
- ensuring that campaigns do not constitute spam, abuse, fraud, or prohibited activity.
FlowraPilot provides workflow and automation technology. FlowraPilot does not determine whether the Customer's particular messaging activity complies with third-party platform policies or applicable law.
The Customer acknowledges that violation of third-party policies may result in warnings, message restrictions, account suspension, number restrictions, or termination by the relevant platform. FlowraPilot is not liable for such actions.
6. Customer Data and Ownership
"Customer Data" means information, records, content, files, lead information, customer information, CRM information, messages, configurations, and other data submitted to or processed through the Service by or on behalf of the Customer.
As between FlowraPilot and the Customer, the Customer retains ownership of Customer Data.
You grant FlowraPilot a limited, non-exclusive right to host, process, transmit, reproduce, and otherwise use Customer Data solely as necessary to provide, maintain, secure, and improve the Service. We do not sell Customer Data.
You are responsible for ensuring that you have the necessary rights, permissions, notices, and lawful basis to provide Customer Data to FlowraPilot.
7. Data Retention and Deletion
We retain Customer Data for as long as reasonably necessary to provide the Service and in accordance with the applicable subscription data-handling arrangements. Following termination, we may delete data after a reasonable retention period unless laws require otherwise.
The Customer remains responsible for maintaining appropriate backups of its own business records.
8. Privacy and Security
FlowraPilot will maintain reasonable administrative, technical, and organizational safeguards designed to protect Customer Data against unauthorized access, alteration, disclosure, or destruction. No internet-based service can guarantee absolute security.
9. Custom Workflows and Customer Approval
Where FlowraPilot develops or configures a custom workflow, automation, integration, business rule, or process for the Customer, parameters may be documented in writing. The Customer is responsible for reviewing and approving the proposed workflow before production deployment.
FlowraPilot does not guarantee that a Customer-defined business process will produce commercially successful outcomes. Changes to an approved workflow may be subject to additional fees.
10. Service Availability and SLA
For paid subscription plans that include an uptime commitment, FlowraPilot targets 99.5% monthly availability of the core Service, measured monthly.
Availability Exclusions
Downtime or degradation will not count against the SLA metric where caused by:
- Scheduled maintenance communicated in advance
- Emergency maintenance required to protect systems
- Customer environment, networks, or custom setups
- Upstream Third-Party Service infrastructure failure
- Meta, WhatsApp, Gupshup, or CRM systems outages
- Global or routing internet failures outside our control
- Force majeure occurrences or regional catastrophes
- Denial-of-service or unpreventable digital attacks
- Customer pipeline misuse or breach of these Terms
- Beta, experimental, or preview feature structures
Service Credits Framework
The SLA provides service credits as the Customer's exclusive remedy for qualifying availability failures, applied against future subscription invoices:
| Monthly Availability Range | Invoice Service Credit Percentage |
|---|---|
| 99.0% to less than 99.5% | 5% of monthly subscription fee |
| 98.0% to less than 99.0% | 10% of monthly subscription fee |
| Below 98.0% | 20% of monthly subscription fee |
- Credits apply only to the explicitly affected subscription track.
- Tokens are not redeemable for cash payouts or dynamic refunds.
- Total monthly credits cannot exceed 20% of the single monthly billing cycle fee.
- Requests must be filed in writing within 14 days after the end of the target month.
11. Support
Support availability depends on the Customer's subscription tier. FlowraPilot targets initial responses to submitted logs within these priority window metrics:
| Severity | Impact Description | Target Response Window |
|---|---|---|
| P1 | Core cluster or interface unavailable for substantial user bases | 4 business hours |
| P2 | Major software functionality pathways are materially impaired | 1 business day |
| P3 | Non-critical isolated functionality bug or setup interface issue | 2 business days |
| P4 | General knowledge base question or platform feature optimization request | 3 business days |
Note: Specified metrics represent operational targets only and do not establish binding guarantees regarding complete engineering resolution timelines.
12. Customer Responsibilities
The Customer maintains full accountability over their platform footprint. The configuration, administrative assignments, and downstream operational activities executed through the subscription remains strictly within the Customer's operational scope.
Specifically, the Customer is solely responsible for:
- The explicit compliance and legality of all hosted Customer Data
- The actions and authorizations of all provisioned users and account administrators
- Securing connected third-party platform credentials and active API tokens
- Validating the accuracy of custom-configured business rules and routing rules
- Obtaining explicit permissions and required consents from message recipients
- Maintaining separate, redundant business continuity procedures and data backups
13. Acceptable Use
To preserve the security, integrity, and deliverability metrics of the shared software architecture, strict boundaries govern platform interactions. Any breach of these boundaries compromises the platform cluster environment.
Strictly Prohibited Activities
You explicitly agree that you will not use, nor permit any third party to use, the Service to:
✕Violate regional telecommunications laws or international communication regulations.
✕Infringe upon the intellectual property, copyright, data privacy, or publicity rights of others.
✕Transmit malicious payloads, worms, trojans, tracking vectors, or destructive code.
✕Execute phishing strategies, identity fraud, spoofing campaigns, or targeted brand harassment.
✕Broadcast unsolicited communications, deceptive advertisements, or explicit spam campaigns.
✕Attempt to bypass firewalls, security configurations, or reverse engineer platform runtime packages.
✕Interfere with node operations or compromise cluster stability via abusive API looping patterns.
✕Deploy automation tools in clear violation of upstream Third-Party Service terms and rules.
FlowraPilot reserves the right to immediately isolate workloads or temporarily suspend instances where structural security threats, system abuse, or material hazards to the network ecosystem are detected. Where commercially practical, advanced notification parameters will be provided.
14. Intellectual Property
FlowraPilot and its licensors retain all exclusive rights, title, and interest in the core infrastructure ecosystem. Except for the explicitly limited operational usage permissions granted within these Terms, absolutely no ownership parameters shift to the Customer.
Protected Proprietary Assets Including, but not limited to:
Custom Workflows Exception Rule: Unless explicitly codified otherwise in a separate signed scope of work document, the delivery of custom workflow configurations or tailored integration deployments does not transfer ownership of FlowraPilot's underlying software, components, frameworks, or reusable tools. Customer Data remains strictly the property of the Customer.
15. Feedback
We welcome suggestions, optimization insights, feature recommendations, or other feedback concerning the refinement of our platform ecosystem.
16. Confidentiality
During the course of account onboarding and platform execution parameters, either party may receive proprietary or confidential business context from the other side ("Confidential Information").
▪Restricted Purpose: Each party will utilize the received Confidential Information strictly to execute their role or receive the designated application workflows.
▪Standard of Care: Both sides must protect the other party's data using reasonable care profiles that are at least as stringent as those applied to their own high-priority assets.
▪Access Control: Boundaries restrict information access solely to employees, secondary engineering contractors, or professional legal advisers who explicitly need to verify data metrics.
Exclusion Parameters: Confidentiality obligations do not encompass context that becomes publicly accessible without protocol breach, information already known prior to execution, data independently generated, or parameters requested via state court orders, provided advanced legal notification targets are matched.
17. Warranties and Disclaimers
FlowraPilot will provide the Service using reasonable skill and care.
Except as expressly stated in these Terms, the Service is provided on an "as is" and "as available" basis to the maximum extent permitted by applicable law.
FlowraPilot does not warrant that:
- the Service will be uninterrupted or error-free;
- every workflow will achieve a particular business result;
- automated outputs will always be accurate;
- leads or customers will be generated;
- conversion rates or revenue will increase;
- Third-Party Services will remain available;
- third-party APIs will remain unchanged; or
- the Service will satisfy every particular business requirement unless expressly agreed in writing.
The Customer remains responsible for evaluating automated results and determining whether they are suitable for its particular business use.
18. Limitation of Liability
If the Customer has not paid any fees during that period, FlowraPilot's aggregate liability will not exceed the fees actually paid during the applicable subscription period.
This limitation applies to all causes of action and theories of liability, including contract, tort, negligence, statutory claims, and otherwise, except to the extent such limitation is prohibited by applicable law.
19. Exclusion of Indirect and Consequential Damages
Without limiting the foregoing, FlowraPilot will not be liable for losses arising from:
- missed leads;
- missed sales opportunities;
- incorrect lead qualification;
- incorrect lead routing;
- lost customers;
- failed campaigns;
- messaging restrictions;
- account suspension by a third-party platform;
- business interruption; or
- commercial decisions made using automated workflows or outputs,
except to the extent such exclusion is prohibited by applicable law.
20. Third-Party Platform Liability
The Customer acknowledges that certain aspects of the Service may depend upon third-party infrastructure and platforms.
FlowraPilot will not be responsible for losses caused by a third party's:
- outage;
- API failure;
- policy change;
- rate limitation;
- account suspension;
- number or sender restriction;
- data loss;
- security incident;
- service discontinuation; or
- change to technical functionality.
Where reasonably possible, FlowraPilot may assist the Customer in identifying or resolving issues involving a Third-Party Service, but such assistance does not make FlowraPilot responsible for the third party's performance.
21. Indemnification
The Customer agrees to defend, indemnify, and hold harmless FlowraPilot, its affiliates, officers, employees, and contractors from third-party claims, losses, liabilities, damages, and reasonable expenses arising from:
- Customer Data;
- Customer's unlawful use of the Service;
- Customer's violation of these Terms;
- Customer's violation of applicable messaging or platform policies;
- Customer's failure to obtain required consent or authorization; or
- Customer's infringement of third-party rights.
FlowraPilot will promptly notify the Customer of an indemnifiable claim and provide reasonable cooperation at the Customer's expense.
22. Suspension
FlowraPilot may temporarily suspend access to the Service where reasonably necessary because of:
- non-payment;
- security threats;
- unlawful activity;
- abuse;
- violation of these Terms;
- excessive usage that materially affects the Service; or
- requirements imposed by a Third-Party Service.
Where reasonably practicable, we will provide advance notice and an opportunity to remedy the issue.
Suspension will be limited to the scope reasonably necessary to address the relevant issue.
23. Termination
Either party may terminate a subscription in accordance with the applicable order form or subscription terms.
Either party may terminate these Terms for material breach if the breach remains uncured for 30 days after written notice, unless a different cure period is required by applicable law or is specified in an order form.
Upon termination:
- Customer's right to use the Service will end;
- outstanding fees become payable;
- each party will return or delete confidential information where appropriate; and
- Customer Data will be handled in accordance with the data-retention provisions above.
Sections concerning intellectual property, confidentiality, payment obligations, disclaimers, indemnification, limitations of liability, dispute resolution, and other provisions that by their nature should survive termination will survive termination.
24. Changes to the Terms
We may update these Terms from time to time.
For material changes, we will provide reasonable notice through the Service, email, or another appropriate communication channel.
The updated Terms will apply from the effective date stated in the notice.
Continued use of the Service after the effective date constitutes acceptance of the updated Terms, to the extent permitted by applicable law.
25. Force Majeure
Neither party will be liable for failure or delay in performing its obligations where the failure or delay results from circumstances beyond its reasonable control, including natural disasters, war, terrorism, civil unrest, government action, internet or telecommunications failures, power failures, epidemics, pandemics, labor disputes, or failures of third-party infrastructure.
The affected party will use reasonable efforts to mitigate the impact and resume performance as soon as reasonably practicable.
26. Governing Law and Dispute Resolution
These Terms will be governed by the laws of India, without regard to conflict-of-law principles.
The parties will first attempt in good faith to resolve disputes through discussions between authorized representatives.
If a dispute cannot be resolved through good-faith discussions, the dispute will be subject to the dispute-resolution mechanism and courts/arbitration jurisdiction specified in the applicable order form.
[INSERT AGREED JURISDICTION / ARBITRATION SEAT, E.G. BENGALURU, KARNATAKA]
Nothing in this section prevents either party from seeking urgent injunctive or equitable relief from a court of competent jurisdiction.
27. General
These Terms, together with applicable order forms, subscription terms, and other documents expressly incorporated by reference, constitute the agreement between the parties concerning the Service.
If there is a conflict between these Terms and a signed order form, the order form will control to the extent of the conflict.
The Customer may not assign its rights or obligations under these Terms without FlowraPilot's prior written consent, except in connection with a merger, acquisition, or sale of substantially all of its assets.
FlowraPilot may assign these Terms in connection with a merger, acquisition, corporate restructuring, or sale of the relevant business.
If any provision is held invalid or unenforceable, the remaining provisions will remain in effect.
Failure to enforce a provision does not constitute a waiver.
These Terms do not create a partnership, joint venture, agency, employment, or fiduciary relationship between the parties.
28. Contact
For questions concerning these Terms or the Service, please contact:
FlowraPilot
Email: hello@flowrapilot.com
Address: Hustlehub, 17th Cross, 14th Main, HSR Layout, Bangalore, Karnataka 560102.
Service Commitment Summary
For convenience, the principal operational commitments under these Terms are:
| Core Service availability | 99.5% monthly target |
| SLA remedy | Service credits, not damages |
| Maximum monthly SLA credit | 20% of applicable monthly subscription fee |
| Customer Data | Owned by Customer |
| Third-party platforms | Outside FlowraPilot's operational control |
| Custom workflows | Subject to written scope and Customer approval |
| Aggregate liability cap | Fees paid during preceding 6 months |
| Consequential damages | Excluded to the maximum extent permitted by law |
| WhatsApp/platform compliance | Customer responsibility for content, consent, and usage |