On this page
At a glance
- We never sell your data. Not lead data, not account data, not Google data.
- Google data follows Limited Use. It is used only for the features you see in the app, and never for advertising or to train AI models.
- We only read your Google Ads. We never change campaigns, budgets, bids or billing.
- You stay in control. Disconnect Facebook or Google at any time, and ask us to delete your data.
Who we are
AgentzPro is owned and operated by AI Digital Tamizha, which is responsible for deciding why and how personal data is processed through the Service.
| Business name | AI Digital Tamizha |
|---|---|
| Product | AgentzPro |
| Nature of work | Software as a service (SaaS) |
| Registered location | Lakshmi Nagar, Mudichur, Chennai 600028, Tamil Nadu, India |
| aidigitaltamizha@gmail.com | |
| Phone | +91 90472 27223 |
Scope of this policy
AgentzPro is a multi-tenant SaaS platform. Many independent businesses ("companies" or "tenants") use the Service under their own separate accounts. Each company may connect its own Facebook Pages to receive Meta Lead Ads leads, connect its own Google Ads accounts with Google Sign-In, set up its own Google Ads lead form webhook, create its own 99acres webhook URL, create its own MagicBricks webhook URL, and create its own webhook for leads from its own tools. Each company's data is kept separate, so one company can never see another company's data.
This policy covers all data processed through AgentzPro: data about the companies and their team members, and data about the people ("leads") who submit a company's Facebook or Google Ads lead forms, whose details the company's own tools send, or who call the company.
Information we collect
3.1 Account information
When a business signs up, we collect the company name and the name, email address and role of the owner and each team member they invite. You sign in with a one-time code sent to your email address, so we do not store passwords.
3.2 Facebook Login
When a company owner connects Facebook, we receive the basic profile information Facebook Login makes available, such as the person's name and Facebook user ID. We use it only to connect that company to Meta on its own behalf.
3.3 Connected Facebook Pages
When a company connects one or more of its Facebook Pages, we store the Page ID, the Page name and the Page access token needed to receive leads for that Page. Access tokens are stored encrypted and are used only to retrieve leads for the company that connected the Page.
3.4 Leads from Meta Lead Ads
When someone submits a Lead Ads form on a company's connected Facebook Page (including ads shown on Instagram), Meta sends the submission to AgentzPro through Meta's webhook and Graph API. It may include the person's name, email address, phone number and answers to the form's questions, together with the campaign, ad set, ad and form IDs and the ad name. This data is delivered only to the company that owns the Page and ad.
3.5 Google Sign-In and Google Ads
When a company owner connects Google Ads, they sign in with Google and see Google's consent screen listing the access we ask for. With their permission, we receive:
- Basic Google account information: the email address and Google account ID of the person who connected, so the company can see which Google account is linked;
- Google Ads account information: the list of Google Ads accounts that person can reach (including client accounts under a manager account) and their names, so the owner can choose which accounts to link. We store only the accounts the owner chooses;
- Campaign, ad group and asset group names: for each Google Ads lead, we look up the names that match the IDs in the lead, so the lead shows which campaign it came from; and
- A Google refresh token: the token Google issues for the connection, which we store encrypted. Short-lived access tokens made from it are kept in memory only while a request runs and are never saved.
We only read this data. We never create, edit, pause or delete campaigns or ads, and we never change budgets, bids or billing in any Google Ads account.
3.6 Leads from Google Ads lead forms
When someone submits a Google Ads lead form, Google sends the submission to AgentzPro through the webhook the company owner has added to that form. It may include the person's name, email address, phone number and answers to the form's questions, together with the lead ID, form ID, campaign ID, ad group ID, ad ID and Google click ID (GCLID). Every webhook has a secret key unique to the company, and the data is delivered only to that company.
3.7 Leads from your own tools (webhook)
A company owner can create a webhook URL and add it to the company's own tools, such as a website form plugin, Zapier, Pabbly or its own software. Those tools then send leads to AgentzPro. A lead may include the person's name, email address and phone number, where the lead came from (for example "Landing Page"), the tool's own lead ID, and any other answers the company chooses to send. The company decides what its tools send. Each webhook URL contains a long secret code unique to the company, and the leads are delivered only to that company.
3.8 Leads from 99acres
A company owner can create a 99acres webhook URL and ask 99acres to send the company's 99acres enquiries to it. An enquiry may include the person's name, phone number and email address, the project or property they asked about, their city, their message and 99acres's own enquiry ID. If the phone number already belongs to one of the company's leads, the enquiry is added to that lead's history instead of creating a second lead. We also keep a copy of each request exactly as 99acres sent it, with its technical headers (any passwords or keys in them are hidden), so that an enquiry that could not be saved is never lost and we can fix the problem. The company owner sees the time and reason of each failed request; the copies themselves are used only by our support team to fix a problem, and they are deleted automatically after 30 days. Each 99acres webhook URL contains a long secret code unique to the company, and the leads are delivered only to that company.
3.9 Leads from MagicBricks
A company owner can create a MagicBricks webhook URL and ask the company's MagicBricks account manager to send the company's MagicBricks enquiries to it. An enquiry may include the person's name, phone number and email address, the project or property they asked about (including MagicBricks's property ID), their city, their message and MagicBricks's own enquiry ID. If the phone number already belongs to one of the company's leads, the enquiry is added to that lead's history instead of creating a second lead. We also keep a copy of each request exactly as MagicBricks sent it, with its technical headers (any passwords or keys in them are hidden), so that an enquiry that could not be saved is never lost and we can fix the problem. The company owner sees the time and reason of each failed request; the copies themselves are used only by our support team to fix a problem, and they are deleted automatically after 30 days. Each MagicBricks webhook URL contains a long secret code unique to the company, and the leads are delivered only to that company.
3.10 Leads your team adds (call-in leads)
Team members can add a lead by hand, for example when someone calls the company. They may enter the person's name, phone number, email address, the platform and ad the person came from, the call date and notes.
3.11 Work your team does in the CRM
We store the statuses, notes, follow-up tasks, reminders and lead assignments your team records, and a timeline of changes to each lead, so your team can see the history of every lead.
3.12 Browser notifications
If a team member turns on reminder notifications, their browser gives us a push subscription (a web address and encryption keys for that browser). We use it only to send that person their task reminders, and we delete it when it stops working. Notifications can be turned off at any time in the browser settings.
3.13 Billing information
When a company subscribes, our payment partner Razorpay collects the payment details. We do not receive or store card or bank details. We keep the plan, number of seats, billing period and payment status.
3.14 Technical information
When you use the Service, we and our hosting providers automatically process technical information such as IP address, browser and device type, server logs and the actions taken in the app. We use it to run, secure and fix the Service.
How we use information
We use the information described above only to:
- provide AgentzPro to each company, including signing people in and connecting their Facebook Pages and Google Ads accounts;
- receive, show and organise each company's leads, and let its team update, assign and follow up on them;
- show which campaign, ad group or ad each lead came from;
- give each lead from Meta, Google Ads, 99acres, MagicBricks or a company's webhook an AI label (Hot, Warm or Cold) to help the company decide who to contact first. Before a lead is labelled, we remove the name, email address and phone number from the form's contact fields, as described in Section 5;
- send task reminders, account emails and team invitations;
- process subscription payments;
- keep the Service secure, find and fix problems, and improve reliability; and
- comply with the law and enforce our Terms of Service.
We use a company's lead data only to provide that company's own CRM. We never market to leads ourselves, and we never sell lead data or company data to anyone.
How we share information
We do not sell personal data. We share information only in these cases:
- Meta Platforms, Inc., to connect a company's Facebook account, receive leads from its connected Pages and comply with Meta's Platform Terms;
- Google LLC, to connect a company's Google account, read its linked Google Ads account data, and comply with Google's terms and policies;
- Service providers that process data only on our instructions to run the Service:
- Supabase, our database provider, for secure data storage;
- Vercel, our hosting provider, for running the application;
- Upstash, for queuing incoming leads so none are lost, and for rate limiting;
- Resend, for sending account emails such as team invitations;
- Cloudflare Turnstile, for checking that a sign-in comes from a real person;
- Razorpay, for processing subscription payments (see Section 13);
- Web push services run by browser makers (such as Google, Mozilla and Apple), which deliver task reminders to the browsers where notifications are turned on. Each reminder is encrypted for that browser; and
- Portkey, an AI gateway that passes a lead to an AI model provider (Google Gemini models) to produce the AI label described in Section 4. Before anything is sent, we replace the name, email address and phone number from the form's contact fields (full name, first and last name, email and phone number) with placeholders such as [NAME], [EMAIL] and [PHONE], including anywhere those same details are repeated in other answers. Only the remaining form answers, the ad name and the lead's current status are sent. For a Google Ads lead, the ad name is the campaign and ad group (or asset group) name. The model provider uses this data only to return the label and does not use it to train its models. The label is shown only to the company that owns the lead.
- For legal reasons, when required to comply with the law or to protect the rights, property or safety of AI Digital Tamizha, our customers or others.
- Business transfers, as part of a merger, acquisition or sale of assets. For Google user data, this happens only after we get your explicit prior consent.
We never share one company's data with another company, and we never share lead data with anyone for advertising or marketing.
Google user data and Limited Use
AgentzPro's 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.
6.1 What Google data we access
We ask for Google access only when a company owner chooses to connect Google Ads, and we ask only for what the Google Ads features need:
| Permission | Why we ask for it |
|---|---|
openid, email, profile | To identify the Google account that was connected and show its email address in the app. |
https://www.googleapis.com/ | Google offers one permission for the Google Ads API. We use it only to read: the list of Google Ads accounts and their names, and the campaign, ad group and asset group names for your leads, as described in Section 3.5. |
6.2 How we use Google data
We use Google user data only to provide and improve features that you can see in AgentzPro: showing which Google account is connected, letting the owner choose Google Ads accounts, showing the campaign and ad group each Google Ads lead came from, and the AI lead label described in Section 4.
6.3 How we store and protect Google data
The Google refresh token is encrypted with AES-256-GCM before it is saved. Short-lived access tokens are never saved. All data travels over encrypted HTTPS connections and is stored with our database provider, which encrypts data at rest. Google data is tied to the company that connected it and is protected by the database access rules described in Section 7.
6.4 Who we share Google data with
We transfer Google user data only to the service providers in Section 5 that we need to run the features above: Supabase (storage), Vercel (hosting) and, for the AI label, Portkey and Google Gemini (campaign and ad group names only). We transfer it otherwise only for security purposes (for example, investigating abuse), to comply with applicable law, or as part of a merger, acquisition or sale of assets after getting your explicit prior consent.
6.5 What we never do with Google data
- We never sell Google user data.
- We never transfer Google user data to advertising platforms, data brokers or other information resellers.
- We never use Google user data to serve ads, including retargeting, personalised or interest-based ads.
- We never use Google user data to determine credit-worthiness or for lending.
- We never use Google user data to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models.
6.6 Who can see Google data
Google Ads leads and account data are shown only to the team of the company that connected the Google Ads account. Our own staff do not read Google user data unless (a) you give us permission to view specific data, for example to help with a support request; (b) it is needed for security, such as investigating a bug or abuse; (c) it is needed to comply with applicable law; or (d) the data is aggregated and used for internal operations in line with applicable law.
6.7 Disconnecting Google and deleting Google data
AgentzPro has two separate controls on the Integrations page, both for the company owner:
- Disconnect Google sign-in. We revoke our access with Google and immediately delete the refresh token, the list of linked Google Ads accounts and the saved campaign and ad group names. We then can no longer read anything from Google Ads. We keep a record of which Google email address was connected and when, as connection history, until the company asks us to delete it or closes its account.
- Stop Google Ads leads. Turns off the company's lead form webhook, so new Google Ads leads are refused and not saved. Turning it back on creates a new secret key.
You can also remove AgentzPro's access at any time from your Google Account at myaccount.google.com/permissions. Leads already received, including the campaign and ad group name shown on each lead, stay in the company's CRM until the company deletes them or asks us to delete them, as described in Section 10.
Each company's data is separate
Every record in AgentzPro belongs to one company, and database-level access rules (row-level security tied to a unique company ID) are checked on every request. This is designed so that no company can view, search, export or otherwise reach another company's Facebook connections, Google Ads connections, leads or account data.
Data retention
We keep company account data and lead data for as long as the company's AgentzPro account exists, so we can keep providing the Service. If a subscription ends, the data is kept so the company can pick up where it left off. When a company closes its account or asks us to delete data, as described in Section 10, we delete it, except for limited information we must keep to comply with the law, resolve disputes or enforce our agreements.
Google refresh tokens are kept only while Google Ads is connected and are deleted on disconnect, as described in Section 6.7. Browser push subscriptions are deleted when they stop working or when you ask us to delete your data. The copies of 99acres requests described in Section 3.8 are deleted after 30 days. The copies of MagicBricks requests described in Section 3.9 are also deleted after 30 days.
Data security
We protect the information in our care with technical and organisational measures, including:
- encryption of Facebook access tokens, Google refresh tokens, webhook keys and webhook URLs with AES-256-GCM before they are saved;
- encrypted HTTPS connections for all data in transit, and encryption at rest by our database provider;
- signature checks on every lead Meta sends us, a secret key check on every Google Ads lead webhook, and a secret URL check on every company webhook;
- company-separated database access rules, as described in Section 7; and
- automatic sign-out of inactive sessions and bot checks at sign-in.
No system can be guaranteed 100% secure. If we learn of unauthorised access to your information, we will tell affected users promptly, as required by applicable law.
Your rights and deleting your data
Companies, their team members and leads can ask to access, correct or delete their personal data. Here is how to manage and delete data in AgentzPro:
- Delete leads: on the Leads page, tick the leads you want to remove and press Delete.
- Disconnect Facebook: the owner disconnects a Page on the Integrations page. You can also remove AgentzPro from your Facebook account's Business Integrations settings.
- Disconnect Google Ads: the owner disconnects Google on the Integrations page, or removes access at myaccount.google.com/permissions (see Section 6.7).
- Turn off reminders: turn off notifications for AgentzPro in your browser settings.
- Close an account or delete everything: email us at aidigitaltamizha@gmail.com from the account's email address. A lead who wants their own details removed can contact us the same way.
We reply to every request within 3 business days. If you ask us to disconnect your Google Ads account from AgentzPro, we do so within 3 business days. Once we have confirmed a deletion request, we delete the data from our systems, except where the law requires us to keep it. Deleted data cannot be recovered.
Children's privacy
AgentzPro is a business product for business owners and their staff. It is not directed at children, and we do not knowingly collect personal data from children. If you believe a child has given us personal data, please contact us so we can delete it.
Payments, cancellation and refunds
Paid plans are billed per seat, monthly or yearly, and payments are processed securely by our payment partner, Razorpay.
- Cancel anytime. You can cancel your subscription at any time. Cancelling stops future renewals, and you keep access until the end of the period you have already paid for.
- No refunds. Payments already made are not refunded, for monthly or yearly plans.
Governing law
AI Digital Tamizha is based in Chennai, Tamil Nadu, India, and processes personal data in line with applicable Indian law, including the Digital Personal Data Protection Act, 2023. This policy, and any dispute arising from it, is governed by the laws of India.
Changes to this policy
We may update this policy to reflect changes in our practices or for legal or operational reasons. When we do, we change the "Last updated" date at the top of this page. If we ever want to use Google user data in a new way, we will tell you and ask for your consent first.
Contact us
For any question or request about this policy or your personal data, including deletion requests, contact us:
See also our Terms of Service.