Privacy statement

How Samuel handles your email tests.

Samuel is built to be useful without being creepy. This page explains what gets stored, how long it sticks around, and what the public test-link trade-offs are.

Retention 24h Public report life
Purpose 1 Deliverability testing
Sharing No sale No data brokering
Control You Choose what to send

What Samuel stores

  • The test token and generated email address for each check.
  • The message headers and body needed to analyse deliverability.
  • Derived report data such as spam-risk score, link count, authentication results, and findings.
  • The public results URL associated with that test.

How long it stays

  • Public result pages stay live for 24 hours.
  • After that, the test should be treated as expired and cleaned up by the scheduled cleanup task.
  • If a cleanup job has not run yet, short-lived residual files may still exist briefly on the server before removal.

What Samuel does not promise

  • It does not replace legal advice, privacy advice, or a full enterprise mail-audit.
  • It does not guarantee inbox placement with Gmail, Microsoft, Yahoo, or any other provider.
  • It does not make your message private from anyone who already has the public results link.

Public-link caution

  • Samuel uses public results URLs so you can re-open a test quickly from any device.
  • Anyone with that link can view the report while it is still live.
  • The report does not show the full email body by default, but it can show sender details, the subject line, scores, and derived findings from the message.
  • Samuel also stores the raw message on the server while it analyses the test and until cleanup removes it.
  • For that reason, avoid using Samuel for confidential, health, legal, payroll, or highly sensitive mail unless you are comfortable with the public-link model and short-term server-side storage.

Third-party checks

Samuel may perform DNS lookups such as SPF, DKIM, DMARC, MX, and blacklist lookups to build the report. Those checks query public internet infrastructure rather than sending your full email body to outside scoring providers by default.

Your choice

You decide which message to forward or upload. If you do not want content analysed, do not send it to Samuel. For sensitive testing, use a redacted copy or a purpose-made sample email.

What this means for you

This page explains how Samuel works today. Before you test a real email, make sure you are comfortable with the 24-hour public results link and the short-term server-side storage used to analyse the message.

Plain-English version: Samuel is here to inspect deliverability, not to become your long-term message archive.