Data handling
You upload an email; that deserves a precise answer about what happens to it. This page states what is kept, what is never kept, and what is redacted — matching what the code enforces today, including the parts that are still honest work-in-progress.
Never persisted
- Raw message body — the HTML and text content of your email is parsed transiently to extract resources and is not retained after parsing.
- Attachments — attachment bytes are not stored anywhere in SendProofs tables.
- The .eml file itself — the upload is read, size-checked and parsed; the raw source is not written to the database.
What a report keeps
- Envelope basics
- Subject (up to 500 characters), sender address, message id and timestamps.
- Resource URLs
- The extracted link and image URLs, and the final URL after redirects. The canonical stored copies are encrypted at the application level; encryption keys are required for the service to boot.
- Display copies
- Redacted versions of those URLs for rendering reports, plus the redirect chain hop by hop, also redacted.
- Link text
- Short snippets of the visible link text (up to 200 characters) so you can recognize which link is which.
- Check evidence
- Status codes, warnings, error codes, durations and check timestamps.
Redaction in visible reports
Report views show redacted URLs: recognized token-like path segments — long mixed
alphanumeric strings and UUIDs — the segment following a sensitive keyword such as
unsubscribe or token, and every query value except the five
standard utm_* keys are replaced with [REDACTED]. Redaction is
pattern-based: it reliably hides the common token shapes, but it is not a promise that
every secret in every URL format is caught. The canonical URLs stay encrypted at rest
regardless of what the display copy shows.
What leaves SendProofs
Bounded requests to eligible public destinations from your email, identified as
SendProofs/0.1 — described in full in the
security model. Recognized action links are never
requested. No recipient data is involved at any point: the input is one test email that
you sent to yourself.
Retention — the honest state
Reports are kept so you can revisit evidence. Per-plan retention windows are defined, but scheduled automatic deletion is not yet active — we would rather tell you that than claim a deletion behavior that is not running. If you need a report or an entire workspace removed now, write to vmarcetic@bytecode.hr and it will be deleted manually. This page will change when automated retention ships.
Boundaries
- No compliance certifications are claimed on this page — see security.
- Uploading an email is your action — make sure you are entitled to upload it. The intended input is a test campaign you sent to your own inbox.
- The formal terms live in the privacy notice and terms.
Questions about a specific field?
Ask — precise answers about stored data are part of the product.