Esrok

Data policy

What we store. What we do not store.

A plain-English explanation for Esrok breach monitoring.

What we store

  • Your account email and account verification status.
  • The email addresses you add for monitoring.
  • Verification status, check timestamps, and weekly summary timestamps.
  • Your current plan code and Stripe customer/subscription references.
  • Positive breach matches for verified monitored emails.
  • Notification records so we can show whether emails were sent or failed.

What a positive breach match means

A positive match means a configured provider or approved private source returned a breach record connected to a verified monitored email. Esrok stores the breach name, provider ID, dates when available, exposed data categories, and first/last seen timestamps.

What we do not store

  • We do not store passwords from breach data.
  • We do not store complete breach datasets.
  • We do not store non-customer emails found in breach sources.
  • We do not store payment card numbers.
  • We do not expose your monitored emails publicly.

Why we store positive matches

Positive matches are needed to prevent duplicate alerts, show your breach history, include useful weekly summaries, and prove what Esrok found for your account.

Limits of breach checks

No provider sees every breach. Esrok checks supported sources on a schedule and reports known matches. A clean result is not a guarantee that an email has never appeared in a breach.