Scrape.Email policy center

Cookie Notice

Scrape.Email uses essential session storage and privacy-conscious first-party analytics. Optional Meta marketing cookies remain off unless you opt in.

Essential session cookie

The signed Scrape.Email session cookie authenticates customer and administrator requests. It is HTTP-only, uses SameSite protections, and is Secure in production. It is necessary for the workspace and cannot be disabled while signed in. Logging out or clearing it ends the browser session.

First-party analytics storage

Scrape.Email assigns random visitor and session identifiers in local and session storage to distinguish visits without placing analytics identifiers in third-party systems. The analytics service records page paths, campaign attribution, device characteristics, engagement, and clicks on controls; it does not record form values, passwords, message contents, or API credentials. Network IP addresses are encrypted at rest and visible only to authorized administrators.

Reliability and security telemetry

First-party runtime reporters may send page, error, performance, and traffic events needed to diagnose failures, understand product use, prevent abuse, and measure service reliability. Global Privacy Control and browser Do Not Track signals disable the first-party traffic tracker. Do not place API keys, webhook secrets, SMTP credentials, or unnecessary lead data in browser storage, URLs, or diagnostic reports.

Optional Meta marketing cookies

With your opt-in only, the Meta Pixel (ID 1219153286899205) loads on the site and may use third-party cookies or similar browser storage to measure advertising and site visits. It is off by default. Choosing Accept all records your choice in a first-party preference cookie; choosing Essential only keeps optional Meta tracking off. You can change your choice using Cookie settings at any time. Essential sign-in cookies remain active because they are required to provide the service. Global Privacy Control or Do Not Track disables optional Meta tracking and overrides a prior opt-in. We also send a server-side Purchase event through Meta Conversions API only when the payment provider has verified a paid transaction and the checkout record confirms your marketing consent. That event contains the purchase amount, currency, order identifier, and SHA-256-hashed email, not raw email or phone. Meta may process information under its own privacy terms.

Effective and last updated: September 11, 2026. Dv8 Media Publishing operates Scrape.Email. Contact waconzy@live.com for legal, privacy, billing, or support requests.