Privacy Policy Risk Scanner - GDPR and CCPA Evidence API

What does Privacy Policy Risk Scanner do?

Build a source-linked privacy-policy checklist before a vendor review. This Actor finds language about data-subject rights and how information is kept or transferred, with available GDPR/CCPA references and public privacy-contact strings. Open the Actor to inspect its input and pricing.

Start with one website

1. Paste one public URL into the Input tab, preferably the relevant policy or resource page.
2. Keep evidence enabled and set a run spending limit that covers both event fees below.
3. Run the check, then inspect its sources and errors before expanding the list.

Example input with one public source URL checked on 27 October 2026. Current responses and coverage may differ:

{
  "startUrls": [
    {
      "url": "https://apify.com/privacy-policy"
    }
  ],
  "maxPagesPerSite": 3,
  "concurrency": 1,
  "requestTimeoutSecs": 10,
  "includeEvidence": true
}

Read the evidence

Read the quoted policy context rather than interpreting a keyword match as a satisfied legal requirement. riskFlags identify configured missing or present signals within the checked pages, not a finding that a business has violated privacy law.

Field	How to use it
status, confidence	Signal-detection status and a heuristic score, not a probability of correctness.
extracted.policyFiles, contacts	Detected policy-file locations and available public contact strings.
findings	Short source snippets when includeEvidence is enabled.
coverage, errors	Request/download limits and problems affecting what was checked.

Export JSON or CSV with retrievedAt and your source notes so a later comparison retains its original context.

Scope and limits

Phone strings are conservative candidates from visible text or telephone links. Unusual formats and extensions may be omitted; numbers are not verified.

The output is not a GDPR/CCPA compliance verdict, a legal opinion or evidence that a DSAR process works. The Actor does not submit access requests or examine internal data practices.

Checks use static public responses, without browser execution or login. Each site is bounded by 20 seconds, 1 MiB downloaded and 4 MiB decoded text; redirects and failed requests consume maxPagesPerSite attempts. Submit at most 100 combined URL/domain entries, including duplicates. An undetected signal is not proof of absence.

Pricing and spending control

Event fees are $0.002 per attempt (website-processed) plus $0.018 per useful report (privacy-report): $0.02 when both apply. Check the Pricing tab for the current rates. The report fee requires FOUND or PARTIAL with useful detected signals or extracted evidence. Failed or empty resource probes do not qualify; ordinary NO_SIGNAL/FETCH_FAILED output incurs only the attempt fee.

Budget for both fees before starting a website, and check the Pricing tab for platform terms and plan charges. Review RUN_SUMMARY before repeating billing/output uncertainty, because a retry is a new chargeable check.

Responsible use and support

Use permitted public targets and review their terms. Send a sanitized input through the Issues tab for support or a scope discussion.