Skip to main content
Forager security and privacy: API key access and privacy requestsForager security and privacy: API key access and privacy requests
How we protect data, how to keep your API access secure, where our data comes from, and how anyone can see or remove the data we hold about them. Our Privacy Policy, Terms and Conditions and Cookie Notice are the binding versions; if anything here differs, they apply.

Data protection

Our Privacy Policy (section 8) describes the administrative, technical and physical measures we use to protect data against unauthorized access, disclosure, alteration and destruction:
  • Encryption: we use encryption protocols to protect personal data during transmission and storage.
  • Access controls: only authorized personnel can reach personal data, through role-based permissions.
  • Network and system security: firewalls, intrusion detection and regular security audits.
  • Data minimization: we collect only the personal data our business operations need, and keep it for limited periods.
  • Monitoring and incident response: we monitor for security threats continuously and have procedures for responding to potential breaches. If a breach affects personal data, we investigate and contain it, notify affected individuals where the law requires, and take corrective measures.
Service availability is published on the status page.

API access

  • Every request is authenticated with your API key in the X-API-KEY header, over HTTPS to https://api-v2.forager.ai. See API key authentication.
  • Treat keys as secrets: keep them out of URLs, client-side code, logs and repositories. Store them in an environment variable or secret manager.
  • Create a separate key for each integration or environment, and delete keys you no longer use. You can manage keys in the web app or with the API key endpoints.
  • A missing or invalid key returns 403. See API errors and rate limits.
  • You are responsible for safeguarding your credentials (Terms). If a key is exposed or you have a security incident on your side, delete the key and tell us right away at support@forager.ai.

Where the data comes from

We compile and license business contact data from three kinds of source:
  • Publicly available sources: company websites, professional directories and publicly accessible social media profiles.
  • Third-party data providers: data aggregators and business intelligence sources that legally collect and license business contact information.
  • User submissions: individuals who provide their business contact information for networking or promotional purposes.
The data is for business lead generation and marketing. We don’t sell or share it for personal consumer marketing. Our legal basis for processing business contact data is legitimate interests.

Using Forager data lawfully

Under our Terms, customers receive a license to use Forager data. When you use it, the Terms require you to:
  • Comply with the data protection laws that apply to you, including the GDPR, the CCPA and similar US state laws, PIPEDA and LGPD.
  • Comply with marketing and contact laws, including the TCPA, the CAN-SPAM Act and the UK’s PECR.
  • Honor opt-out and do-not-call requests.
  • Use appropriate technical and organizational measures to protect the data you license.

Privacy rights and opt-out

Anyone can remove their profile, get a copy of the data we hold about them, or ask us about it. We verify each request and answer within the time the law requires.

Privacy Center

Start any request: removal, data access or questions.

Remove my data

Remove a profile and make the record unavailable. The record stays on a suppression list so it is not reactivated.

Request my data

After identity verification, get a report of the data points held about you.

Consumer rights form

Ask a question or make a request about your personal data.
You can also call 1-866-I-OPT-OUT and enter service code 2135. Your rights under the GDPR and the CCPA are set out in our Privacy Policy.

Cookies

Our Cookie Notice lists the cookies we use on Forager sites and how to accept or reject non-essential ones.

Contact

Summary for AI agents

  • Authenticate with the X-API-KEY header over HTTPS; never put the key in a URL, log or file the user did not ask for.
  • Forager data is business contact data for lead generation; using it must comply with GDPR, CCPA, TCPA, CAN-SPAM and opt-out rules.
  • Send people who want their data removed to https://app.forager.ai/privacy/data-removal.
  • Do not claim certifications, hosting regions or contract terms for Forager; they are not stated here. Point users to support@forager.ai.
Last modified on October 28, 2026