Legal
Privacy policy
Last updated 4 November 2026
This policy explains what personal data EzzySocial handles, why, how long we keep it, and what you can ask us to do with it. It is written against India's Digital Personal Data Protection Act, 2023.
1. Who we are
EzzySocial is a product of Samurai Labs, a company registered in India at [registered office address], CIN [CIN].
Grievance officer. Under the DPDP Act we must name a person you can contact about your personal data. That is [name and designation], reachable at [grievance email]. We will acknowledge a request within [number] working days.
2. Two different roles, and the difference matters
For our own customers' account data — the business that subscribes to EzzySocial, its team members, its billing details — we are the Data Fiduciary. We decide why and how that data is processed.
For the end-customer data inside a workspace — the phone numbers, messages and consent records of the people our customer talks to — we are a Data Processor. Our customer is the Data Fiduciary and decides what happens to that data. We process it on their instructions and do not use it for our own purposes.
If you are an end customer of a business that uses EzzySocial and want your data removed, the fastest route is to ask that business. You may also contact us and we will pass the request to them and support it.
3. What we collect
From website visitors
- What you type into a form: name, work email, phone, company, team size, industry and your message.
- The wording of the consent statement you agreed to, with a timestamp, so we can show what you were told.
- Basic analytics: pages viewed, referrer, and the campaign parameters in the link you arrived through. We use cookie-light, first-party analytics and do not run advertising pixels.
From customers who subscribe
- Account and team member details, roles and permissions.
- Billing details, handled by our payment provider.
- Credentials needed to connect your WhatsApp Business Account. These are encrypted at rest and are never written to logs or error reports.
End-customer data inside a workspace
- Phone numbers and contact attributes our customer stores.
- Message content exchanged over WhatsApp, inbound and outbound.
- Consent records: when an opt-in or opt-out was recorded, through what route, and the evidence behind it.
- Delivery outcomes reported by WhatsApp, and the reason a message was not sent.
4. Why we process it
- To provide the service a customer has subscribed to.
- To send WhatsApp messages our customer instructs us to send, where we can verify a recorded consent.
- To keep a defensible record of consent, which is a legal obligation for our customers and for us.
- To protect platform quality, including refusing to send where sending would breach policy or damage a sender's number.
- To bill, support and secure the service.
- To reply to an enquiry you sent us.
5. How long we keep it
[🔴 RETENTION PERIODS NOT YET DECIDED. This section cannot be finalised until they are, and the periods stated here must match what the product actually does. Owner: Vaibhav. Linear PROD-1861]
We will state a period for each of: automation run logs, campaign audience lists, form submissions, raw WhatsApp delivery data, inbox conversation history and contact activity history.
Website enquiry data is kept for [period] and then deleted unless you become a customer.
6. Erasure, and one thing that remains
When an erasure request is honoured we delete the personal data. One thing deliberately survives: a one-way fingerprint derived from the identifier, which cannot be reversed into a phone number or a name.
Why. It is the only way to guarantee that the same person is never contacted again. Without it, an erasure would remove the very record that tells us not to message them, and the next import would quietly re-add them. The fingerprint is retained permanently, is used for nothing except suppression, and cannot identify anyone on its own.
7. Who we share data with
- Meta Platforms — to deliver WhatsApp messages. Meta processes message content as part of delivering it.
- Amazon Web Services — hosting, in the Mumbai region.
- Our payment provider, [name once chosen], for subscription billing.
- Our messaging provider, [name once chosen], to deliver sign-up verification codes.
- An AI provider, [name once chosen], if and when the assistant feature is enabled. ⚠ Conversation content would be sent to it, and we will say so here and in the product before that happens.
We do not sell personal data, and we do not share it for advertising.
8. Where data is stored
Customer and end-customer data is stored in India, in Amazon Web Services' Mumbai region. [⚠ If any processor operates outside India, including an AI provider, that transfer must be disclosed here. Owner: Vaibhav, with legal]
9. Your rights
Under the DPDP Act you may ask us to:
- tell you what personal data of yours we hold and why;
- correct or complete data that is wrong or out of date;
- erase data we no longer need to keep;
- nominate someone to exercise these rights if you cannot;
- take a grievance to our grievance officer, and then to the Data Protection Board of India if we do not resolve it.
Write to [grievance email]. We will respond within [number] working days.
10. How we protect data
- Each customer workspace is isolated at the database layer, and that isolation is verified by an automated test suite that blocks our build if it fails.
- WhatsApp credentials and two-step PINs are encrypted at rest.
- Access tokens, PINs and verification codes are never written to logs, error reports or analytics.
- Access to production data is limited to named staff and is recorded.
⚠ We do not currently hold SOC 2 or ISO 27001 certification and do not claim either.
11. Children
EzzySocial is a business tool and is not intended for anyone under 18. We do not knowingly collect data from children.
12. Cookies
See our cookie policy.
13. Changes to this policy
If we change this policy materially we will update the date at the top and notify customers by email at least [number] days before the change takes effect.