Privacy Policy — Indiamart Lead Notifier

Effective date: August 9, 2026

Indiamart Lead Notifier ("the extension") is a Chrome extension that monitors a seller's IndiaMART account for new buy leads matching the seller's saved filters, automatically claims (purchases) matching leads on IndiaMART, sends the seller a phone notification with the buyer's contact details, and — if the seller chooses to connect it — logs each purchased lead as a row in a Google Sheet the seller specifies. This policy explains what data the extension collects, how it is used, and who it is shared with.

1. Information We Collect

Information you provide directly:

• Your Google account email address, used to sign in and identify your account.
• The phone number(s) you register to receive lead alerts.
• Your lead filter settings (minimum price, minimum quantity, maximum lead age, states, keyword filters).
• Basic device information (device name/type) for each computer or phone you register, so we can enforce your device seat limit.
• If you enable Google Sheets export: the URL of the specific Google Sheet, and the tab name within it, that you choose to send purchased-lead rows to.

Information collected from IndiaMART on your behalf:

When the extension is running, it reads new buy-lead data from your own, already-logged-in IndiaMART seller session and — for leads that match your filters — automatically purchases them using your IndiaMART account balance. In the course of doing this, it collects:

• The buyer's name and mobile number
• The buyer's city and state
• The product/lead title, requested quantity, and approximate order value

This data originates from your IndiaMART seller account, not from the buyer directly, and is collected solely to notify you about leads you have already chosen to purchase.

Separately, for every lead the extension observes — not only the ones it purchases — it keeps a local record of: the lead's title, city, state, category, approximate order value, quantity, and how long ago it was posted; whether it matched your filters and, if not, why; and the filter settings that were active at the time. This lead history does not include the buyer's name or mobile number unless that specific lead was purchased.

Authentication data:

• A Google-issued identity token, used to verify your sign-in and link your registered devices to your account.
• If you enable Google Sheets export: a separate Google-issued OAuth access token, requested only when you click "Connect Google Sheets," used solely to write purchased-lead rows to the specific sheet and tab you provided.

2. How We Use This Information

We use the information described above only to:

• Detect and automatically purchase IndiaMART buy leads matching your filters
• Deliver phone notifications about purchased leads
• Verify your sign-in and enforce your subscription/device seat limits
• Persist your settings between sessions
• If enabled: append a row (purchase date/time, product title, approximate order value, quantity, buyer name, buyer mobile, city, state) to the Google Sheet tab you specified, each time a lead is purchased
• Sync your lead history (every lead observed, matched or not, together with the filter settings active when it was seen — never the buyer's name or mobile number unless that lead was purchased) to a private spreadsheet automatically created in your own Google Drive, for your own record-keeping and any analysis you choose to do with it

We do not use this data for advertising, profiling, or any purpose unrelated to the above.

2a. Google Sheets Access (Google API Services User Data)

If you choose to enable Google Sheets export, the extension requests your permission via Google's OAuth flow using the https://www.googleapis.com/auth/drive.file scope. This is a per-file scope: it grants the extension access only to the single spreadsheet you explicitly pick through Google's file picker, or that you create from within the extension — never blanket access to your Google Drive or to any other file in your account. This access is used exclusively to:

• Confirm that the tab you named exists in the spreadsheet you picked (creating it if it does not);
• Write a header row into that tab if it is empty; and
• Append one row per purchased lead to that tab.

The extension does not read, browse, list, or modify any other spreadsheet, tab, or file in your Google account, and does not use this access for any purpose beyond writing the purchased-lead rows described above. You can revoke this access at any time from your Google Account permissions page, or by clearing the connected sheet in the extension's settings.

Indiamart Lead Notifier's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

2b. Google Drive Lead History Sync (Google API Services User Data)

The extension also uses the same https://www.googleapis.com/auth/drive.file scope described in Section 2a to automatically create and maintain a spreadsheet named "IndiaMART Lead History" in your own Google Drive — no separate permission or file picker step is needed, since drive.file already covers files the extension creates itself. This access is used exclusively to:

• Create that spreadsheet the first time this feature runs, if it does not already exist;
• Write its header row; and
• Append one row per lead the extension has observed — the fields listed in Section 1, and never the buyer's name or mobile number unless that lead was purchased.

This sync runs automatically (roughly once every 24 hours, and when you open the extension if more than 24 hours have passed since the last sync), and can also be triggered manually from the extension's panel. As with Section 2a, the extension does not read, browse, list, or modify any other spreadsheet, tab, or file in your Google account, and this data is written only to a spreadsheet in your own Google account — never to a server we operate. You can revoke this access at any time from your Google Account permissions page, which disconnects both this feature and the Sheets export in Section 2a, since they share the same OAuth grant. The Limited Use and Google API Services User Data Policy commitments in Section 2a apply equally here.

3. Where Data Is Stored

• On your device: lead history (every lead observed, not only purchases) and app settings are stored locally in your browser (IndexedDB / chrome.storage.local).
• Firebase Realtime Database (Google Cloud): your account's leads, registered devices, and entitlement status are stored here so alerts can reach your phone in real time.
• Your own Google Sheet (purchased leads): if you enable Sheets export, purchased-lead rows are written directly to the specific Google Sheet you provided — a spreadsheet in your own Google account, not one we host or control.
• Your own Google Drive (lead history): the "IndiaMART Lead History" spreadsheet described in Section 2b is created and stored in your own Google Drive — likewise not hosted or controlled by us.

4. Third-Party Services

The extension shares data with the following service providers, solely to deliver the features described above:

• Google Firebase — authentication and real-time data storage.
• Expo Push Notification Service (exp.host) — delivers push notifications (including the buyer's name/city/state) to your registered phone(s).
• IndiaMART (seller.indiamart.com) — the source of lead data and the destination of lead-purchase requests, made using your own authenticated session.
• Google Sheets API (sheets.googleapis.com) — used to write purchased-lead rows into the spreadsheet tab you specified (Section 2a), if you enable Sheets export, and to maintain the "IndiaMART Lead History" spreadsheet in your own Drive (Section 2b).

We do not sell, rent, or transfer this data to any other third party, and we do not use it to determine creditworthiness or for lending purposes.

5. Data Retention and Deletion

Lead history and settings are retained until you clear them or uninstall the extension. To request deletion of data associated with your account (including Firebase-stored lead history and device registrations), contact us using the details below.

6. Security

Data in transit is sent over HTTPS. The extension never asks for or stores your IndiaMART password — it acts within your existing, already-authenticated browser session.

7. Children's Privacy

This extension is intended for business use by IndiaMART sellers and is not directed at children.

8. Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with a revised effective date.

9. Contact Us