Skip to content
MsgFlex Legal
Legal Center Privacy Terms Refunds Contact
Log in Get started

Privacy

Privacy Policy

Last updated: 17 November 2026 · Applies to MsgFlex website and SaaS

This Privacy Policy explains how MsgFlex processes personal and business-related information when you use our website, sign-in flows, and WhatsApp Business workspace software.

Legal pages
Legal Center Privacy Policy Terms & Conditions Refund Policy Contact Us
Search this page
On this page
  1. 1. Introduction
  2. 2. Information we collect
  3. 3. WhatsApp and Meta data
  4. 4. How we use information
  5. 5. Legal bases
  6. 6. Processing roles
  7. 7. Information sharing
  8. 8. International transfers
  9. 9. Retention and deletion
  10. 10. Security
  11. 11. Cookies and analytics
  12. 12. Privacy rights
  13. 13. Children’s privacy
  14. 14. Changes
  15. 15. Contact

1. Introduction

MsgFlex is a multi-tenant WhatsApp Business SaaS product that provides inbox, CRM-style audience tools, campaigns, automations (where entitled), developer webhooks, billing, and workspace administration. In this Policy, “MsgFlex,” “we,” “us,” and “our” refer to the MsgFlex service and its operator.

[OWNER REVIEW] Confirm the full legal entity name, registered office address, country of incorporation, and any DPO/grievance officer designation before public launch filings or Meta App Review submissions that require a formal controller identity.

This Policy covers the public website, authentication pages, and authenticated SaaS application. It does not replace Meta’s or WhatsApp’s own privacy terms, which apply to WhatsApp Business accounts you connect.

2. Information We Collect

Depending on how you use MsgFlex, we may process:

Account and authentication

  • Name or display name, email address, and password hashes (passwords are not stored in plaintext).
  • Phone number when you provide it for account or business profile purposes.
  • Sign-in method metadata (for example email OTP, password session, Google Sign-In, or Firebase auth where enabled).
  • Session identifiers, CSRF tokens, and session epoch values used to keep you signed in securely.

Workspace and team

  • Workspace identifiers, roles, invitations, and membership.
  • Business profile fields you enter (such as brand name, legal business name, address, timezone, and related setup data).

WhatsApp connection metadata

  • WhatsApp Business Account identifiers, phone number IDs, connection status, and related onboarding metadata received through Meta Embedded Signup / Cloud API flows where enabled.
  • Encrypted credential material for connected accounts where credential encryption is configured (plaintext tokens are not stored).

Customer-operated CRM and messaging data

  • Contacts and conversation records associated with your workspace.
  • WhatsApp message content and delivery/status metadata processed to operate the inbox and related features.
  • Labels, attributes, segments, lists, campaign configuration, automation definitions, and consent/opt-out evidence your workspace records.

Developer and integration configuration

  • API key metadata (secrets are hashed or shown only once as designed) and webhook endpoint configuration, including encrypted signing secrets where configured.

Billing and subscriptions

  • Plan selection, trial status, subscription status, wallet balance and ledger entries, and payment intent references when billing features are used.
  • Payment provider references (for example Razorpay order/payment identifiers) when that provider is enabled — we do not intend to store full card numbers in MsgFlex.

Device and diagnostics

  • IP address, user agent / browser information, request identifiers, and application logs used for security, debugging, and reliability.

3. WhatsApp and Meta Data

MsgFlex connects to customer-owned WhatsApp Business Accounts that you authorize. MsgFlex does not claim ownership of your WABA, phone numbers, or end-customer contact lists.

  • Connection typically uses Meta Embedded Signup and related Cloud API / webhook mechanisms where enabled for your environment.
  • Through Meta APIs and webhooks, MsgFlex may receive message payloads, delivery receipts, template-related events, and account/phone metadata needed to operate the product.
  • Message content and events are processed to display inbox conversations, update delivery state, support CRM labels/attributes, and power entitled campaign or automation features.
  • You remain responsible for lawful collection and use of your end users’ data, including consent, opt-outs, and Meta WhatsApp Business Policy compliance.
  • Meta and WhatsApp publish their own terms and privacy policies. Their availability, account quality systems, template reviews, and messaging rules are controlled by Meta, not MsgFlex.

4. How We Use Information

  • Create and manage accounts, workspaces, roles, and authentication.
  • Provide inbox, CRM audience tools, campaigns, automations, and developer integrations according to your entitlements.
  • Operate customer support and in-product assistance.
  • Process billing, trials, subscriptions, wallet top-ups, and usage reporting.
  • Protect security, prevent fraud/abuse, enforce tenant isolation, and maintain service reliability.
  • Comply with legal obligations and respond to lawful requests.
  • Improve product quality using aggregated or operational signals where permitted; we do not sell personal information as a business model described in this Policy.

5. Legal Bases for Processing

Where a legal basis framework applies (for example GDPR-style regimes), we rely on one or more of the following as appropriate to the processing:

  • Consent — where you opt in or where consent is required for a specific processing activity.
  • Contractual necessity — to provide the SaaS features you request.
  • Legal obligations — where law requires retention, disclosure, or security measures.
  • Legitimate interests — where permitted, such as securing the platform, preventing abuse, and improving reliability, balanced against your rights.

Applicable bases depend on your location, your customers’ locations, and the nature of the data. This section is explanatory and not a jurisdiction-by-jurisdiction compliance certification.

6. Customer Data and Processing Roles

  • For contacts, messages, labels, campaigns, and similar customer-controlled content, MsgFlex typically acts as a service provider / processor (or equivalent) on behalf of the customer workspace.
  • The customer typically acts as controller (or equivalent decision-maker) for end-user messaging data it collects and directs MsgFlex to process.
  • For account registration, authentication, platform administration, security logs, and billing records about the customer relationship, MsgFlex may act as an independent controller.
  • Exact roles depend on applicable law and the processing circumstances. A separate data processing agreement may be required for enterprise use — mark as an owner decision if needed.

7. Information Sharing

We share information only as needed to operate MsgFlex or as required by law. Categories that may apply:

  • Meta / WhatsApp — to connect accounts, send/receive messages you initiate or receive, and process webhook events.
  • Hosting and infrastructure providers — cloud hosts and related infrastructure used to run the application and database (for example Render-hosted deployments where used).
  • Payment providers — Razorpay when configured as the payment provider; otherwise local/mock payment flows may be used for non-live environments. Refunds through the provider may be unavailable depending on configuration.
  • Email delivery providers — transactional email (for example Resend when configured) for OTP, password reset, and similar mail.
  • Identity providers — Google Sign-In or Firebase authentication when those options are enabled in your environment.
  • Legal authorities — when required by applicable law or valid legal process.
  • Corporate transactions — in connection with a merger, financing, or sale, subject to appropriate safeguards.

We do not list consumer marketing analytics vendors in this Policy because MsgFlex’s public pages do not currently ship a third-party marketing analytics pixel as a verified product feature.

8. International Data Transfers

MsgFlex may process and store information in the regions where our hosting, email, payment, and Meta infrastructure operate. We do not claim a single fixed hosting country in this Policy without owner confirmation of production region(s).

[OWNER REVIEW] Confirm production hosting region(s), any standard contractual clauses / transfer tools, and whether a specific data residency commitment is offered.

9. Data Retention and Deletion

We retain information for as long as needed to provide the Services, maintain security and audit trails, resolve disputes, and meet legal obligations.

  • Account and workspace data — retained while the account/workspace remains active and for a limited period afterward as needed for recovery, billing, or legal holds.
  • Messages and CRM records — retained according to workspace usage and product storage entitlements until deleted by authorized users or removed through an operator-supported deletion process.
  • Logs and security events — retained for operational and security periods that may vary by environment.
  • Billing records — retained as required for accounting and tax purposes.
[OWNER REVIEW] Publish numeric retention schedules (or confirm “retained while account is active + X days”) after business and counsel review. Self-service account deletion is not currently a verified in-product flow; deletion requests should be handled through support until a productized deletion path exists. Meta Data Deletion Callback configuration should be confirmed separately for App Review.

10. Security

We implement technical and organizational measures appropriate to a multi-tenant SaaS product, including:

  • Authenticated sessions with CSRF protection for browser state-changing requests.
  • Role-based workspace permissions and capability checks.
  • Tenant isolation controls so workspace data is scoped to authorized tenants.
  • Password hashing for credential accounts.
  • Fernet-encrypted storage for certain secrets (WhatsApp credentials / webhook signing secrets) when encryption is configured.
  • Request identifiers, application logging, and audit events for security and operations.

No method of transmission or storage is perfectly secure. We do not claim SOC 2, ISO 27001, or similar certification in this Policy.

11. Cookies and Analytics

  • Essential cookies / session storage — required for sign-in sessions, CSRF protection, and theme preferences stored in the browser (for example local theme selection).
  • Product analytics — in-app analytics views summarize your workspace messaging activity for authorized operators; that is first-party product functionality, not a third-party ad tracker.
  • Optional third-party marketing cookies — not described as enabled on the public marketing site in the current verified codebase.

12. Privacy Rights

Depending on applicable law, you may have rights to:

  • Access personal information we hold about you as an account holder.
  • Correct inaccurate account information.
  • Request deletion, subject to legal and operational limits.
  • Data portability where applicable.
  • Restrict or object to certain processing where applicable.
  • Withdraw consent where processing is consent-based.
  • Lodge a complaint with a supervisory authority where available.

To exercise account-holder rights, contact support@msgflex.com. If you are an end user of a MsgFlex customer, contact that business first — they control the messaging relationship.

13. Children’s Privacy

MsgFlex is a business SaaS product intended for adult operators acting for organizations. You must be at least 18 years old (or the age of majority in your jurisdiction, if higher) to create an account. We do not knowingly collect personal information from children for the purpose of offering the Services to them.

14. Changes to This Policy

We may update this Privacy Policy from time to time. The “Last updated” date will change when revisions are posted. Material changes may also be communicated in-product or by email when appropriate. Continued use after the effective date means the updated Policy applies to subsequent processing.

15. Contact and Grievance Information

  • General / privacy requests: support@msgflex.com
  • Product: MsgFlex WhatsApp Business SaaS
  • Legal Center: /legal
[OWNER REVIEW] Add dedicated privacy@ mailbox, grievance officer name (if required under applicable Indian IT rules), postal address, and response SLA if counsel advises.
MsgFlex WhatsApp SaaS

WhatsApp Business workspace for conversations, CRM, campaigns, and teams.

Product

Features FAQ Create account Sign in

Legal

Legal Center Privacy Policy Terms & Conditions Refund & Cancellation Contact Us

Support

support@msgflex.com Service health
© 2026 MsgFlex · These pages are product policies, not legal advice. v0.1.0