Privacy policy
Last updated 14 October 2026
Sabhi Leads is a lead-management platform operated by Sabhi Digital. This page explains what personal data passes through it, why, who else sees it, how long it is kept, and how to have it corrected or erased.
1. Who is responsible for your data
Sabhi Leads is used by advertising clients of Sabhi Digital — businesses running lead-generation campaigns on Facebook and Instagram. Two different relationships matter here, and they carry different responsibilities.
- If you enquired with a business
- That business is the Data Fiduciary for your information. They decide why it is collected and what happens to it. Sabhi Digital is their Data Processor — we run the software that holds it, and we act on their instructions. Requests about your data are best sent to that business first; we will also pass any request we receive to them, and help them act on it.
- If you use the platform
- For the accounts of client staff and Sabhi Digital staff who sign in, Sabhi Digital is the Data Fiduciary.
2. What personal data the platform holds
- Identity and contact
- Name, phone number, email address.
- Location
- City, state, postcode and country, where the lead form asked for them.
- Your answers
- The responses you gave to the questions on the advertiser’s lead form — for example a course you were interested in, a budget range, or a preferred callback time. These vary entirely by advertiser.
- Advertising context
- Which Facebook or Instagram Page, campaign, ad set, ad and form the enquiry came from, and whether it was paid or organic. This contains no information about you personally.
- Contact history
- Calls placed and their outcome, WhatsApp messages exchanged, emails sent, notes written by the sales team, which stage of their process you reached, and when.
- Files
- Any document the advertiser’s team attaches to your record — for example a form you emailed them.
- Account data (staff only)
- For people who sign in: name, work email, role, password (stored only as a hash), two-factor secret, and a log of their actions in the system.
3. Where it comes from
- Meta lead forms. When you submit an Instant Form on a Facebook or Instagram ad, Meta notifies us and we retrieve the answers you gave. This is the main source.
- The advertiser. They may import a spreadsheet of existing contacts, or add an enquiry by hand after a phone call or a walk-in.
- Their own website or systems. An advertiser can connect a form on their site to send enquiries in through our API.
- You, when you reply. If you reply to a WhatsApp message, the content of that reply is stored against your record.
4. Why it is held
- So the advertiser’s sales team can contact you about the enquiry you made.
- So they can keep track of that conversation rather than calling you twice or not at all.
- So they can measure which of their advertising produced enquiries worth having — see section 5.
- To meet legal and record-keeping obligations, including keeping an audit trail of who accessed what.
The platform does not use your data to build advertising profiles, and it is never sold or rented to anyone.
5. What is sent back to Meta
This is worth stating precisely, because it is the part people assume the worst about.
When you move through the advertiser’s sales process — for example from a new enquiry to a qualified one — the platform reports that milestone to Meta’s Conversions API, so Meta’s advertising system learns which enquiries were genuinely useful and shows the ads to more people like that.
- What Meta receives
- Irreversible SHA-256 hashes of your name, phone number, email and city — not the values themselves — plus the milestone reached and when.
- What Meta does not receive
- Your readable contact details, your answers to the advertiser’s form questions, your notes, your call history, or anything a member of the sales team wrote about you.
- Why hashes
- Meta can match a hash to an account it already holds without us disclosing the underlying value. It cannot be reversed to recover your phone number.
7. Google and YouTube accounts
A client can connect their Google account so the platform can publish posts they have approved to their YouTube channel and Google Business Profile, and show them how those posts performed. This section covers only that data. Sabhi Leads uses the YouTube API Services; Google’s handling of the same data is described in the Google Privacy Policy, and using these features means agreeing to the YouTube Terms of Service.
- What is accessed
- The email address of the Google account that connected, to show which account posts. YouTube: permission to upload videos, used only to publish a video the client approved, at the time they scheduled; and read access to identify the channel and read a published video’s view, like and comment counts. Business Profile: permission to read the client’s business locations, publish posts to them, read the reviews customers leave on them, and post the reply a member of the client’s team writes and sends.
- What is stored
- An encrypted refresh token (AES-256) so scheduled posts can go out without the client signing in each time; the account email; which permissions were granted; for each published post its YouTube or Google id, its link, and its view, like and comment counts; and each Google review’s public reviewer name, star rating, text and the client’s reply.
- How long
- Counts are refreshed every six hours for thirty days after publishing. While any are held they are re-confirmed with YouTube at least every thirty days; they are deleted if the video no longer exists, if access could not be re-confirmed for thirty days, or as soon as the connection ends. Reviews are deleted 180 days after they last changed. The token and email are deleted when the connection is removed.
- What it is not used for
- Google account data is used only to publish what the client approved and to report on it to that client. It is not sold, not used for advertising, not shared with anyone else, not used to train AI models, and not read by people except where the client asks us to look into a problem, for security, or where the law requires it.
Limited Use. Sabhi Leads’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Removing access. Disconnecting Google on the client’s page in Sabhi Leads revokes the connection at Google immediately, deletes the stored token, and deletes the YouTube counts. Access can also be removed at any time from the Google account’s security settings page; the platform notices at its next use of the connection and deletes the YouTube counts then, and in any case within thirty days.
Deletion and questions. To have data obtained through Google deleted, or to ask about it, write to rajveer@sabhidigital.com. It is deleted within seven days. Deleting it here does not delete anything published on YouTube or Google Business Profile, which stays under the client’s control there.
8. LinkedIn accounts
A client can connect their LinkedIn company page so the platform can publish posts they have approved there. This section covers only that data. LinkedIn’s own handling of it is described in the LinkedIn Privacy Policy. Posts planned for X and Pinterest are published by hand; the platform does not connect to those accounts.
- What is accessed
- The name and member id of the person who connected, where LinkedIn provides them, and permission to publish posts to company pages that person administers, used only to publish a post the client approved, at the time they scheduled.
- What is stored
- Encrypted access and refresh tokens (AES-256) so scheduled posts can go out without the client signing in each time; the account name and id; which permissions were granted; and for each published post its id and link.
- How long
- Tokens, account name and id are deleted as soon as the connection is removed. A published post’s id and link are kept with the post’s record in the client’s content calendar.
- What it is not used for
- LinkedIn data is used only to publish what the client approved. Nothing is read from the page’s followers, messages or feed. It is not sold, not used for advertising, not shared with anyone else and not used to train AI models.
Removing access. Disconnecting LinkedIn on the client’s page in Sabhi Leads cancels the connection at LinkedIn and deletes the stored tokens. Access can also be removed at any time from the account’s connected-apps settings on LinkedIn. Deleting it here does not delete anything published, which stays under the client’s control there.
9. How long it is kept
- Enquiries
- Twenty-four months by default, counted from when the record was created. Each advertiser can set a shorter or longer period for their own workspace. When the period passes, the record and everything attached to it is deleted automatically.
- Import files
- The staged rows from a spreadsheet upload are discarded within days.
- Audit records
- Kept longer than the data they describe, because their purpose is to show who accessed something after it has gone. They record the action, not your contact details.
- Staff accounts
- Until the account is removed by the organisation that created it.
10. How it is protected
- All traffic is encrypted in transit with HTTPS, and the site is served under a strict transport policy.
- Access credentials and integration tokens are encrypted at rest with AES-256.
- Each client’s data is isolated at the database level by row-level security, so a fault in the application cannot expose one client’s enquiries to another.
- Access inside a client’s workspace follows their own policy — by default a sales agent sees only the enquiries assigned to them.
- Signing in supports two-factor authentication with recovery codes.
- Every consequential action is written to an append-only audit log that cannot be edited or deleted, including by us.
- Uploaded files are stored privately; they are never publicly addressable.
No system is perfectly secure. If a breach affects your data we will notify the affected advertiser and the Data Protection Board of India as the DPDP Act requires.
11. Your rights
Under India’s Digital Personal Data Protection Act, 2023, you may:
- Ask what is held about you and receive a copy.
- Have it corrected if it is wrong, incomplete or out of date.
- Have it erased where it is no longer needed for the purpose you gave it for.
- Nominate someone to exercise these rights if you are unable to.
- Raise a grievance and receive a response.
How to exercise them. Contact the business you enquired with — they are the Data Fiduciary and can act immediately. If you do not know who that is, or they do not respond, write to us at rajveer@sabhidigital.com with enough detail to find your record — the phone number you enquired with is usually enough. We respond within thirty days.
Step-by-step instructions for erasure are on the deleting your data page.
12. Children
The platform is not intended for children, and advertisers using it must not run lead campaigns directed at children. If we learn that a record belongs to a child, it is deleted.
14. Where the data is held
Data is stored on servers in a data centre operated under contract by our hosting provider. Where an advertiser has enabled an integration described in section 6, data reaches that provider’s own infrastructure, which may be outside India — Meta, WhatsApp and Google being the main examples.
15. Changes to this policy
If this policy changes materially, the date at the top of the page changes and clients are notified. Continued use after that constitutes acceptance.
16. Contact and grievances
- Operator
- Sabhi Digital, India
- Privacy contact
- rajveer@sabhidigital.com
- Grievance officer
- Reachable at the address above. We acknowledge a grievance within seven days and respond within thirty.
- If unresolved
- You may complain to the Data Protection Board of India under the DPDP Act, 2023.