Effective and last updated: 23 September 2026
This Privacy Policy explains how Lead Shikaari ("Lead Shikaari", "we", "us", or "our") collects, uses, stores, protects, and shares information when you use the Lead Shikaari Chrome extension, website, APIs, and related automation services at leadshikaari.co.in and api.leadshikaari.co.in (together, the "Service").
The data controller for the Service is Lead Shikaari. Privacy questions and requests can be sent to support@leadshikaari.co.in with [Privacy] in the subject line.
When you turn on automation, the extension reads content from the IndiaMART seller pages open in the tab you selected. This can include buyer and company names, location, email address, phone number, product, quantity, requirement message, order value, lead date, buyer/profile signals, and the IndiaMART page URL. It uses this information to filter and score leads and to perform the lead-contact action you requested.
When a lead is purchased/contacted, or when an account uses the direct-enquiry integration, some or all of that lead information is transmitted over HTTPS to Lead Shikaari's Microsoft Azure services. Depending on the enabled features, it may be stored in Azure PostgreSQL, Blob Storage, Table Storage, and Logic App workflow history and may be sent through Meta's WhatsApp Cloud API to deliver lead alerts, retry failed alerts, route leads to configured sales recipients, and send configured buyer greeting/follow-up messages.
The extension does not collect your IndiaMART password or authentication cookies and does not read pages outside the IndiaMART domains declared in its manifest.
While automation is enabled on an IndiaMART tab, the extension can access:
The extension does not monitor general browsing history and does not access non-IndiaMART page content.
If the account uses the IndiaMART direct/push-enquiry integration, IndiaMART sends us an enquiry identifier, type, buyer name, company, email, phone, location, product, subject, requirement message, timestamps, and other webhook fields. We store the original and normalized payload, routing recipient, delivery status, retry count, and error information for deduplication, routing, support, and delivery auditing.
We do not receive or store full card numbers, CVVs, bank-account credentials, or UPI PINs. Those are entered on and processed by Razorpay.
Hosting and application logs may include request time, route, status code, IP address and user agent supplied to the hosting platform, extension version, masked contact identifiers, account/transaction/message identifiers, errors, and stack traces. We use these logs only to operate, secure, and troubleshoot the Service.
We use information only to provide, maintain, secure, and improve Lead Shikaari's disclosed lead-automation purpose, including to:
We do not use user or lead data for personalized advertising, retargeting, creditworthiness, lending, or sale to data brokers.
The extension uses chrome.storage.local for account/session tokens, license/device identifiers, account/phone and subscription caches, automation settings, product keywords, pacing/usage ledger, selected tab/URL, failure counters, announcement/update state, and—if sending temporarily fails—a pending lead-delivery queue. Small filter markers can also be stored in the IndiaMART page's local storage.
This information remains in that Chrome profile until removed by the extension, logout, data clearing, or uninstall. Anyone with access to your unlocked browser profile may be able to access local extension data.
We use Microsoft Azure services, primarily in India, including Azure Functions, Azure Database for PostgreSQL, Logic Apps, Blob Storage, Table Storage, and Application Insights. These services store account, device, subscription, usage, payment-reference, direct-enquiry, lead-routing/follow-up, messaging, delivery, and diagnostic records. Azure workflow execution history can contain workflow inputs and outputs.
| Information | Retention approach |
|---|---|
| Local extension data | Until logout/removal, successful queue delivery, browser/site-data clearing, or uninstall. |
| Signup and reset records | Signup codes expire after 15 minutes and reset links after 60 minutes. Expired rows cannot be used but may remain in the restricted database until maintenance cleanup or a verified deletion request. |
| Account, licence, device, subscription, configuration, and usage records | While the account is active and afterward as needed to close the account, resolve disputes, prevent abuse, and meet legal obligations. |
| Lead, direct-enquiry, greeting/follow-up, retry, and WhatsApp delivery records | While needed for routing, deduplication, delivery, support, security, and operational auditing. Some database, Blob, and Table Storage records have no universal automatic expiry and may remain until operational cleanup or a verified deletion request. |
| Payment/transaction records | For the period required by applicable tax, accounting, payment-dispute, and anti-fraud laws. |
| Application/workflow diagnostic history | Generally up to 90 days, subject to configured Azure retention, backup cycles, security investigations, and legal holds. |
After a verified deletion request, we delete or de-identify data no longer required. Information may remain in restricted backups until their normal cycle expires; legally required and payment-dispute records may be retained for the required period.
We do not sell personal or lead information. We share only the minimum information needed with the following parties:
Microsoft processes Service data for hosting, databases, workflows, lead retry/follow-up storage, and diagnostic monitoring. This can include account and lead data, phone/email data, payment references, and technical logs. See Microsoft's Privacy Statement.
For enabled WhatsApp features, Meta receives the destination number and message content. Message content can contain an IndiaMART buyer's name, company, location, email, phone, product, requirement, quantity, order value, and date. Meta returns message IDs and send/delivery/read/failure events. See the WhatsApp Privacy Policy.
Razorpay receives account name/email, selected plan, amount/currency, billing cycle, and transaction context to present checkout and process payment. Razorpay returns payment/subscription identifiers and statuses. See Razorpay's Privacy Policy.
Microsoft Logic Apps and the connected GoDaddy SMTP service process recipient email, name where used, subject/body, signup code, password-reset link, and subscription/account notification content solely to send transactional email. See GoDaddy's Privacy Policy.
Lead details may be delivered to WhatsApp numbers and sales recipients configured for the account and, for configured buyer follow-up, to the lead's phone. Authorized Lead Shikaari administrators can access account, subscription, usage, payment-reference, enquiry, and delivery information for support, security, billing, and aggregate operations.
We may disclose information when required by applicable law or valid process; to investigate security, fraud, spam, or abuse; or as part of a merger, acquisition, or sale of assets, subject to applicable notice/consent requirements.
We do not share data with advertising networks, data brokers, information resellers, or lenders.
Authorized personnel may access identifiable information only when necessary to provide support with your permission, investigate security/abuse, comply with law, operate billing, or perform internal operations using aggregated or de-identified data where practical. Access is restricted to personnel who need it for those purposes.
Lead Shikaari's use and transfer of information received through Chrome extension and Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
No service can guarantee absolute security. Do not share account credentials, license keys, or one-time codes.
Subject to applicable law, you can request access, correction, deletion, restriction, objection, or a portable copy by emailing support@leadshikaari.co.in with [Privacy] in the subject. We may ask you to verify account ownership.
You can also stop automation; remove/disable WhatsApp numbers; disable a direct-enquiry integration; log out; clear extension storage; uninstall the extension; and ask us to delete lead, enquiry, delivery, and account records not required for legal, security, or payment-dispute purposes.
We respond within the time required by applicable law. Provider backups and workflow history are removed as their normal retention cycles expire.
IndiaMART lead information can identify a buyer who is not the Lead Shikaari account holder. By enabling processing, you instruct us to process that information for your lead-management workflow. You are responsible for using and contacting leads in accordance with IndiaMART's terms and applicable privacy, telemarketing, and messaging laws, including honoring opt-outs.
Core Azure resources are primarily hosted in India. Microsoft, Meta, Razorpay, GoDaddy, and their subprocessors may process information in other countries under their own infrastructure and legal obligations.
The Service is intended for business users aged 18 or older. We do not knowingly collect personal information from children. Contact us if you believe a child supplied information.
We may update this policy when the Service or legal requirements change. We will update the effective date and provide additional notice in the extension, website, or by email when a change is material.
Lead Shikaari Privacy Support
Email: support@leadshikaari.co.in
Subject prefix: [Privacy]