BirbalOS
Legal

Privacy Policy

Effective date / last updated: 19 November 2026
App / product name: BirbalOS
Website: https://birbalos.com

Request data deletion

Any user of BirbalOS (including business account users and people whose data we process through our Meta / WhatsApp integration) can request access, correction, or deletion of their data by emailing privacy@birbalos.com with the subject “Data deletion request”. See Section 11 for full details, timelines, and what we delete.

1. Introduction and scope

This Privacy Policy explains how BirbalOS (“BirbalOS”, “we”, “us”, or “our”) collects, uses, stores, shares, retains, and deletes personal information and Platform Data when you:

  • Visit our websites, including birbalos.com
  • Create or use a BirbalOS account (web app, mobile web, or related applications)
  • Book a demo, contact sales, or use customer support
  • Connect Meta / Facebook / WhatsApp Business Platform accounts to BirbalOS
  • Send or receive messages, media, or other content through BirbalOS on WhatsApp or other connected channels
  • Are an end customer or contact of a business that uses BirbalOS

By using BirbalOS, you acknowledge this Privacy Policy. If you do not agree, do not use the Service. Our processing is designed to align with applicable law, including India’s Digital Personal Data Protection (DPDP) Act and, where applicable, the EU/UK GDPR, and with Meta Platform Terms for apps that use WhatsApp Business Platform APIs.

2. Who we are and how to contact us

Product: BirbalOS — an AI-powered customer experience (CX) and marketing automation platform built around WhatsApp and related channels.

Privacy contact (all privacy and deletion requests):
Email: privacy@birbalos.com
Web: https://birbalos.com/privacy

We respond to verified privacy requests as described in Section 11.

3. Roles: controller vs processor

  • Website, marketing, and account administration: BirbalOS is the data controller for information we collect about visitors, demo leads, and account users (for example email, phone, company name, billing).
  • Customer conversation and CRM data inside a business workspace: The business customer that operates the BirbalOS workspace (the “Client”) is typically the controller of end-customer / contact data. BirbalOS acts as a processor / service provider and processes that data only to provide the Service as instructed by the Client and as described here.
  • Meta Platform Data: When we access data through Meta / WhatsApp APIs on behalf of a Client, we process that Platform Data to operate messaging and related features for that Client, in accordance with Meta Platform Terms, WhatsApp Business policies, and this Privacy Policy.

4. What data we collect

We collect the categories of data listed below. Exact fields depend on which features you enable and which integrations you connect.

4.1 Account and business user data

  • Full name, work email address, phone / WhatsApp number
  • Company / organisation name, role or job title
  • Login credentials (passwords are stored hashed; we never store plaintext passwords)
  • Team membership, roles, and permissions (including SSO identifiers when SSO is enabled)
  • Billing name, billing address, tax identifiers, payment method tokens (card numbers are handled by our payment processors; we do not store full payment card numbers)
  • Support tickets, emails, and chat history with BirbalOS support

4.2 Demo and marketing data

  • Work email and WhatsApp / phone number submitted on demo or contact forms
  • Optional business details you provide in sales conversations
  • Email / WhatsApp engagement related to our own marketing (opens, clicks), where permitted

4.3 End-customer / contact data (processed for Clients)

When a Client uses BirbalOS, we may process data about that Client’s customers, leads, and contacts, including:

  • Name, phone number, WhatsApp identifier / WhatsApp profile name
  • Message content (text), media (images, audio, video, documents), location shares, and interactive replies (buttons, lists, forms)
  • Conversation metadata (timestamps, delivery / read status where available, message IDs, conversation IDs)
  • Tags, notes, lead scores, deal stages, custom fields, and CRM records created or synced in BirbalOS
  • Consent / opt-in and opt-out status for messaging where tracked in the product
  • Order, catalog, cart, and payment-link status information generated through in-chat commerce features
  • Data imported from Client-connected systems (CRM, e-commerce, sheets, ads, helpdesk, payment tools)

4.4 Technical, device, and usage data

  • IP address, approximate location derived from IP
  • Browser type and version, device type, operating system
  • Pages viewed, referring URLs, session activity, feature usage events
  • Log files, diagnostic data, crash reports, and security audit logs (logins, exports, permission changes)
  • Cookie and similar identifiers (see Section 9)

4.5 How we collect data

  • Directly from you — forms, account setup, settings, uploads, support
  • Automatically — when you use the website or app (logs, cookies, analytics)
  • From Meta / WhatsApp APIs — when a Client connects a WhatsApp Business Account and messages flow through BirbalOS
  • From integrations — CRMs, stores, payment providers, and other tools a Client authorises
  • From team members of a Client — when they add contacts, notes, or campaigns

5. Meta Platform Data and WhatsApp data

BirbalOS integrates with the official WhatsApp Business Platform (and related Meta developer products) so Clients can send and receive business messages. Depending on the permissions granted to our app, we may access and process the following Platform Data:

  • WhatsApp Business Account (WABA) identifiers, phone numbers, display names, and business profile information
  • Message templates and template status
  • Inbound and outbound message content and media exchanged with end users
  • Webhook events (delivery, read receipts where available, user replies, errors)
  • Contact phone numbers and WhatsApp user identifiers associated with those conversations
  • Business asset and permission metadata needed to manage messaging on behalf of the Client
  • Any other data explicitly returned by Meta APIs for permissions such as whatsapp_business_messaging and whatsapp_business_management that the Client has authorised

How we process Meta / WhatsApp Platform Data:

  • To deliver, receive, store, display, and sync WhatsApp conversations inside BirbalOS
  • To power chat flows, broadcasts, routing, CRM sync, analytics, and AI replies that the Client enables
  • To maintain message history, audit logs, and operational reliability
  • To troubleshoot delivery issues and comply with Meta / WhatsApp policies and applicable law

What we do not do with Platform Data:

  • We do not sell Platform Data
  • We do not use Platform Data to build unrelated advertising profiles or to contact people outside the Client’s messaging relationship, except as needed to provide the Service the Client requested
  • We do not share Platform Data with other Clients
  • We process Platform Data only as described in this Privacy Policy, as instructed by the Client, and as allowed by Meta Platform Terms and WhatsApp Business policies

6. How and why we use data

PurposeExamples of data used
Provide and operate BirbalOS (inbox, CRM, flows, broadcasts, payments links, analytics)Account data, conversation data, WhatsApp Platform Data, integration data
Authenticate users and enforce role-based access / SSOLogin credentials, SSO IDs, roles, audit logs
AI replies, intent detection, lead scoring, language detection, suggested responsesMessage content, CRM fields, conversation history
Respond to demos, sales, and support requestsContact details, support content
Billing and subscription managementBilling details, usage metrics needed for invoicing
Security, fraud prevention, abuse detectionIP, device data, logs, account activity
Improve product reliability and features (aggregated / de-identified where practical)Usage events, diagnostics
Send product / service notices and permitted marketingEmail, phone / WhatsApp (opt-out available)
Comply with law, Meta terms, and lawful requestsRelevant records as required

Legal bases (where GDPR or similar frameworks apply) include: performance of a contract, legitimate interests (securing and improving the Service), consent (where required, for example certain cookies or marketing), and legal obligation.

7. AI processing

BirbalOS includes optional and default AI features (for example automated replies, intent / sentiment detection, lead qualification, routing suggestions, and flow assistance). When enabled for a workspace:

  • Message content and related CRM context may be processed by our AI systems and/or contracted AI sub-processors to generate outputs for that Client
  • AI is used to provide the features the Client turns on — not to sell conversation content
  • Clients remain responsible for reviewing AI outputs that affect their customers where human oversight is appropriate
  • We require contractual and technical safeguards from AI providers consistent with the sensitivity of the data

8. How we share data

We share personal information / Platform Data only in these situations:

  • Service providers / sub-processors — cloud hosting, databases, email / SMS delivery, payment processing, error monitoring, analytics, and AI infrastructure providers who process data on our instructions under confidentiality and data-protection terms
  • Meta Platforms, Inc. and WhatsApp — to send and receive messages and operate WhatsApp Business Platform features the Client connects
  • Integrations the Client connects — for example Shopify, WooCommerce, HubSpot, Zoho, Salesforce, Razorpay, Stripe, Google Sheets, Zapier, and similar tools authorised by the Client
  • Within the Client’s organisation — team members with access to the Client’s BirbalOS workspace according to roles set by the Client
  • Legal and safety — when required by law, regulation, legal process, or to protect rights, safety, and integrity of users, the public, or BirbalOS
  • Business transfers — in connection with a merger, acquisition, financing, or sale of assets, with protections and notice where required

We do not sell personal information or Meta Platform Data. We do not share Platform Data with third parties for their independent marketing.

9. Cookies and similar technologies

We use cookies, local storage, and similar technologies to:

  • Keep you signed in and maintain session security (essential)
  • Remember preferences such as theme (functional)
  • Understand site and product performance (analytics)
  • Measure marketing effectiveness where used (performance / advertising cookies, if enabled)

You can control cookies through your browser settings. Blocking essential cookies may prevent login or core product functions from working.

10. Data retention

  • Account and workspace data: retained while the account is active and for a limited period afterward needed for billing, disputes, backups, and legal obligations
  • WhatsApp conversation / Platform Data: retained to provide message history and Service features for the Client, and deleted according to Section 11 when deletion is required or requested
  • Marketing leads: retained until you opt out or we no longer have a legitimate need, subject to legal retention
  • Security logs: retained for a limited period for security and abuse investigation
  • Aggregated / de-identified data: may be retained for analytics and service improvement when it can no longer identify a person

11. Data deletion and user rights

How to request deletion (available to all users who can access BirbalOS, and to individuals whose data we process):

  1. Email privacy@birbalos.com with subject line “Data deletion request”
  2. Include: your name, the email / phone number associated with your BirbalOS account or WhatsApp conversations, your company name (if any), and a clear description of what you want deleted
  3. We may verify your identity before fulfilling the request to protect against unauthorised deletion

Business end customers should first contact the business (Client) that messaged them, because that Client controls the customer relationship. If you are unsure who the Client is, email us and we will help route the request.

11.1 What we delete

Upon a valid deletion request (or when deletion is otherwise required), we delete or irreversibly anonymise personal data and Meta Platform Data associated with the request from production systems, including account profile data, conversation content we store, media we store, and related CRM records we control — except where retention is required by law or needed to resolve disputes, enforce agreements, or maintain security (in which case we limit further processing).

11.2 When we delete Platform Data

Unless applicable law requires retention, we delete Meta Platform Data as soon as reasonably possible when:

  • A user (or, for Client data, the Client or an affected user) requests deletion
  • A user no longer has an account with BirbalOS
  • A Client closes their BirbalOS workspace / account
  • Retaining the Platform Data is no longer necessary for a legitimate business purpose consistent with Meta Platform Terms and this Policy
  • Meta requests deletion for the protection of users
  • We stop operating the product or service through which the Platform Data was obtained
  • Deletion is required by applicable law or regulation

Deletion from active systems is completed as soon as reasonably possible and generally within 30 days, and in any event not more than 120 days (including cascading deletion from backups where feasible). Aggregated or de-identified data that cannot reasonably be associated with a person, browser, or device may be retained.

11.3 Other rights

Depending on your location, you may also have the right to:

  • Access a copy of your personal data
  • Correct inaccurate data
  • Restrict or object to certain processing
  • Data portability
  • Withdraw consent where processing is based on consent
  • Lodge a complaint with a supervisory / data protection authority

To exercise these rights, contact privacy@birbalos.com.

12. Security

We implement technical and organisational measures designed to protect data, including:

  • TLS encryption for data in transit
  • Encryption at rest for stored data
  • Role-based access controls and optional SSO
  • Audit logging of sensitive actions (logins, exports, permission changes)
  • Least-privilege access for staff and sub-processors

No method of transmission or storage is 100% secure. Please use strong unique passwords, enable available security features, and notify us immediately of suspected unauthorised access.

13. International transfers

BirbalOS is operated with a primary focus on customers in India and globally. Data may be stored or processed in India and in other countries where we or our sub-processors operate. Where required, we use appropriate safeguards for cross-border transfers. Enterprise plans may offer India and/or EU data residency options.

14. Children’s privacy

BirbalOS is a business / B2B service and is not directed to children under 18. We do not knowingly collect personal information from children. If you believe a child has provided us personal data, contact privacy@birbalos.com and we will take appropriate steps to delete it.

15. Changes to this policy

We may update this Privacy Policy from time to time. The “last updated” date at the top will change when we do. For material changes, we will provide additional notice as appropriate (for example via email or an in-product notice). Continued use of BirbalOS after an update means you acknowledge the revised Policy.

16. Contact

For privacy questions, data access requests, or data deletion requests:

BirbalOS Privacy
Email: privacy@birbalos.com
Privacy Policy URL: https://birbalos.com/privacy
Website: https://birbalos.com