Data Use Policy

This Data Use Policy describes how LeadSnipper Technologies processes data you and your contacts provide when using LeadSnipper, SocialSnipper, and related payment flows. It works together with our Privacy Policy and Terms of Service.

1. Roles: controller vs processor

• For your account and billing data, we act as the data controller.
• For lead lists, campaign recipients, and LinkedIn content you upload or approve, you are the controller and we act as a processor on your instructions.

2. Contact and lead data (LeadSnipper)

• You may import contacts via CSV, API, or integrations. You represent that you have a lawful basis to process each contact.
• We store leads in our secure database, run format and duplicate checks, and optionally verify emails via Reoon or similar services you enable.
• Unverified leads are not treated as send-ready until you complete verification steps in the product.
• You may export or delete lists from your account. Account deletion requests are handled per our Privacy Policy.

3. Email sending and AWS SES

• Campaign content and recipient addresses are transmitted to AWS SES (or your connected BYO-SES account) solely to deliver mail you authorize.
• Delivery events (sent, bounce, complaint, open/click where enabled) are stored for analytics, compliance, and deliverability protection.
• We do not sell recipient data to third parties.

4. LinkedIn data (SocialSnipper)

• SocialSnipper is built on LinkedIn's official APIs. We do not scrape LinkedIn profiles or messages.
• Data accessed may include your profile identifier, organization pages you manage, draft and scheduled posts, media you upload, and performance metrics for content you publish through the Service.
• We do not store LinkedIn passwords. OAuth tokens are stored securely and can be revoked by you via LinkedIn or by disconnecting in settings.
• LinkedIn data is used only to: (a) generate and schedule content you approve; (b) publish on your behalf; (c) show analytics; and (d) operate approval channels you connect (e.g. Telegram or WhatsApp).

5. Public web and enrichment data

Where features process publicly available business information from URLs you submit, we respect robots.txt and site terms. We do not bypass paywalls, authentication, or technical access controls. You are responsible for lawful use of enriched data in your jurisdiction.

6. Analytics and product telemetry

We collect usage events (feature adoption, errors, performance) to improve the Service. Marketing site analytics are privacy-oriented where possible. We do not use your lead lists for unrelated advertising.

7. Payment data

Subscription and checkout data are processed by Razorpay. We receive transaction IDs, amounts, and status — not full card numbers. See Razorpay's privacy notice for their processing practices.

8. Retention

• Active account data: retained while your account is open.
• Campaign and lead data: retained per your settings and plan; deleted or anonymized after account closure except where law requires retention.
• Security logs: typically retained for a limited period (e.g. 90–180 days) unless needed for an investigation.

9. Deletion and portability

Submit deletion or export requests to privacy@leadsnipper.com. We will verify your identity and respond within applicable legal timeframes. Takedown requests for specific content: support@leadsnipper.com.

10. GDPR, UK GDPR, and India DPDP

We support data subject rights and processor obligations under GDPR/UK GDPR where applicable, and align with India's Digital Personal Data Protection Act (DPDP) for Indian users. Data Processing Agreements (DPAs) are available on request for business customers at privacy@leadsnipper.com.

11. Sub-processors

Key sub-processors include AWS (hosting and email), Razorpay (payments), Reoon (verification when enabled), LinkedIn (SocialSnipper publishing), and notification providers you connect. An up-to-date list is available on request.

12. Contact

Data use questions: privacy@leadsnipper.com.