Privacy Policy

Last updated: 13 November 2026 · Spirality Solutions Private Limited · Bizdaptive

1. Who we are

Bizdaptive is operated by Spirality Solutions Private Limited, 18A, Durairaj Street, Gandhi Nagar, Chennai, Tamil Nadu 600087, India. Our Meta app may appear on Facebook as “Spirality AI”; it is the same Bizdaptive service described here. This policy explains how we handle information when you use our product, website, and messaging channels connected through Meta (WhatsApp, Facebook Messenger, Instagram).

2. Information we process

  • Account data: name, email, workspace membership, and role permissions
  • Customer conversation data: WhatsApp, Messenger, and Instagram messages, button taps, read and delivery receipts, attachment metadata, and contact names, handles, and phone numbers
  • Facebook Page tokens for the Page a workspace admin connects, stored encrypted. The browser does not receive the token
  • Lead Ads form answers for that Page, including the name, phone number, and the campaign or ad name when Meta includes them
  • Ad account data for the account that workspace connects: account name, campaign names and status, and recent spend, clicks, and impressions
  • When a workspace admin turns on Meta conversion tracking, CRM stage-change events with hashed contact identifiers are sent to that workspace's own Meta dataset (pixel), not to other customers
  • Technical data: logs, device/browser basics, and delivery status needed to operate the service

3. How we use information

  • Provide inbox, CRM, and support workflows for your business
  • Deliver and receive messages on channels you authorize (including Meta APIs)
  • Improve reliability, security, and optional AI-assisted drafts inside your workspace
  • Comply with law and prevent abuse

4. Meta / Instagram / WhatsApp data

A workspace admin connects their own Facebook Page with Facebook Login. Facebook Login provides the user's public profile (name) and app-scoped Facebook user ID, used only to identify the person connecting and to list their Pages and ad accounts. We do not request email from Facebook Login. We store the app-scoped Facebook user ID on each connected Page connection, on the workspace Meta Ads connection, and on data-deletion request records, so we can match Meta deletion and deauthorization callbacks to the right stored tokens. We store the connecting person's Facebook name on the Meta Ads connection only. We store that Page access token encrypted and use it only for that workspace: to list the Page and its Instagram professional account, subscribe the Page to webhooks, and send the Messenger and Instagram replies a teammate writes. Incoming messages, button taps, and read or delivery receipts are saved in that workspace inbox.

For Lead Ads, we fetch the form answers Meta sends for that Page and save them as a contact and an enquiry in the same workspace. A lead needs a phone number. For Ads, we read that workspace’s ad account name, campaign list, campaign status, and recent spend, clicks, and impressions. An admin can pause or resume a campaign on that account. Creating an ad stays in Meta Ads Manager.

We do not sell message content, lead form answers, or ad account data. Another workspace cannot read them. The Page token and the Ads login token are removed when an admin disconnects in Settings, then Channels (Disconnect on the Facebook or Instagram card) or Settings, then Connections for Meta Ads, when that Facebook user removes Bizdaptive under Facebook settings, and when Meta calls our data-deletion callback.

5. Sharing

We share data with providers that run the product under contract: Vercel (hosting), Supabase (database, Mumbai, India region), Resend (email), Groq (optional AI-assisted drafts), and Meta for WhatsApp, Facebook Messenger, and Instagram delivery. We do not sell personal data.

When a teammate asks for an AI-assisted draft, the relevant message text is sent to Groq only to generate that draft. It is not used to train Groq's or any other provider's models. A person reviews and sends the draft; the AI does not message your customers on its own.

6. Retention

Page tokens and the Meta Ads login are deleted as soon as the workspace disconnects them, or when Facebook tells us the person removed the app or asked for data deletion. Messages, contacts, and lead enquiries stay in the workspace after a token is removed, because the business still needs them to serve that customer. They remain while the workspace is active.

A Facebook data-deletion callback clears those tokens and records a confirmation code. It leaves workspace records such as enquiries in place. To delete conversation, contact, and enquiry data, email us as described on bizdaptive.app/data-deletion. A code on that page shows whether the Facebook token revocation is completed or pending. We also keep records the law requires, such as tax invoices.

7. Your choices

Workspace admins can disconnect WhatsApp, Facebook, Instagram, and Meta Ads in Settings. Disconnect revokes the stored token for that workspace and stops new messages and leads from that connection. Removing Bizdaptive in Facebook settings, or Meta’s data-deletion callback, does the same for every workspace that Facebook user connected. End customers may also use Meta, Instagram, and WhatsApp privacy controls for those platforms.

8. Contact

Privacy questions: info@spiralitysolutions.com. How the product may be used is in the terms of service.