Privacy Policy

1. Who this policy covers

This Privacy Policy explains how Sendzoy, a multi-tenant WhatsApp Business SaaS product by Ahanya IT Solutions (“the Platform”), processes personal and business data when you create an account, operate a workspace (organization), connect WhatsApp Business accounts, manage contacts, send or receive messages, or contact support.

Where a formal operator or billing identity is published on this site, it comes from configured Platform Info (legal/business name and support contacts). Brand attribution to Ahanya IT Solutions does not by itself invent registered-entity status. Placeholder contact values are never shown publicly.

2. Roles and responsibilities

You (the customer organization) decide which contacts to store, which campaigns and Live Chat messages to send, and how your team uses the workspace. You are responsible for obtaining any consent required under applicable law for messaging those contacts.

Meta Platforms / WhatsApp act as independent services for WhatsApp Business connectivity, template review, business verification, phone number status, delivery, and messaging policy enforcement. The Platform cannot override Meta decisions.

3. Data we process

• Account and user data: name, email, password hash (if set), Google account identifier (if you use Google sign-in), legal acceptance timestamp and policy version, role/permission membership, and login-related security events.
• Workspace data: organization profile, settings (such as branding, timezone, business hours), plan and subscription records, invoices, and billing notes created by platform administrators.
• WhatsApp account identifiers: phone number IDs, WABA identifiers, connection status, and related metadata required to call Meta APIs for your workspace.
• Contacts and CRM-related fields: phone numbers, names, emails, tags, lead statuses, sources, notes, custom fields, and opt-out flags.
• Messaging content and operational records: templates, campaign metadata, conversation and message records, delivery/read/status events from webhooks, canned replies, agent assignments, and messaging-balance ledger entries.
• Technical and operational logs: application logs, webhook ingestion events, queue job outcomes, and API request logs where the developer API is used — retained for security, debugging, and abuse prevention.

4. Why we process data

We process data to provide the SaaS product: authenticate users, isolate tenant workspaces, connect WhatsApp via Meta, send and receive messages you initiate, enforce plan limits, charge messaging balance for outbound usage, show history and analytics available in product, prevent abuse, and provide platform support when you contact us.

5. Tenant separation

The product is multi-tenant. Workspace data is segregated using organization scoping and access controls in the application. This describes the product architecture; it is not a security certification, audit attestation, or compliance badge.

6. Sharing

WhatsApp/Meta receive the message content, template content, and account identifiers required to deliver WhatsApp traffic you request. Hosting, email, and infrastructure providers that power the deployment may process data as processors under our direction. We do not sell contact lists.

7. Retention

We retain account, workspace, messaging, billing, and log data for as long as needed to operate the service, meet legal obligations, resolve disputes, and maintain security. You may request deletion of workspace content subject to backup, legal hold, and Meta-side records outside our control. For request steps, see User Data Deletion Instructions.

8. Your choices

Workspace users can manage contacts, opt-outs, templates, and team access inside the product according to their permissions. Contact platform support using the configured support details when available. For Meta account or template decisions, you must work through Meta’s tools and policies.

9. Changes

We may update this policy. The policy version shown on this page identifies the current text. Material changes to registration consent are reflected in the stored policy version for new acceptances.