VerifyPulse

Privacy policy

Last updated 31 October 2026. VerifyPulse keeps as little as it can.

What we store

  • Account details, if you create an account: your email address, a hash of your password, your API keys and your credit balance.
  • Check history, if you are signed in: the addresses you check and their results, so your dashboard can show them.
  • Monitoring, if you use Sender Guard: your domains, your alert destination, such as a webhook URL, and snapshots of those domains' public DNS records.
  • Report inboxes, if you create one: a random code, and a short summary of each DMARC report sent to it (reporter, domain, dates, counts, sending server addresses and pass or fail). The email itself is not kept. Summaries expire after 180 days.
  • Purchases: what was bought, the amount and the payment reference. A USDC payment is also public on the Base blockchain.

Usage counts

We count requests by page or tool, status, browser or client type, referring site and country. To count distinct visitors we keep a short hash of your IP address and browser, salted with the date, so it changes daily. Rate limits use a similar hash for a short window. We do not store your IP address in these counts, and we do not record the domains or addresses you type in them. Counts are kept for 120 days.

Cookies

We set one cookie, to keep you signed in. There are no advertising or tracking cookies.

Who else handles data

  • Vercel hosts the service and Upstash stores monitoring and usage data.
  • PayPal processes card and PayPal payments. We never see your card number.
  • Facilitators settle x402 USDC payments on Base.

Your data is not sold. Domains you check are looked up in public DNS, and a check may contact that domain's public mail or web servers.

Your choices

To ask for your data to be deleted, open an issue at GitHub without posting private details, and we will arrange it from there.