Neutral notice
No sensitive content in the inbox
MailCerty keeps the content behind a control step. The message and its attachments are only displayed after successful validation.
Illustrative preview · all names and statuses are fictional.
CONFIDENTIAL MESSAGE
A sensitive email should not disclose its content in a transferable notification. MailCerty separates the notice from protected content.
PROTECTED CONTENT
A notification does not reveal the message. MailCerty keeps the content behind the selected access step, then records a successful access separately from the send.
Sensitive content and attachments are not placed in the forwarded alert.
The recipient completes the required code or confirmation step.
The file distinguishes delivery of the notice from access to the content.
To camille@example.com · protected content
PROTECTED CONTENT — VISUAL JOURNEY
The email notification contains no sensitive body or attachment. The recipient completes the configured access check before MailCerty displays the protected message.
No sensitive content in the inbox
Controlled code or configured step
Successful access is timestamped
Event linked to the original message
MESSAGE PRIVACY
The recipient journey keeps notice, access and acknowledgement visibly separate.
The notification does not expose confidential content.
The recipient completes the required control step.
Documents follow the same journey as the message.
Relevant successful and failed access attempts are dated.
WHAT MAILCERTY RECORDS
Availability depends on the selected journey and on facts actually returned by the mail infrastructure or completed by the recipient.
| Function | Recorded fact | Availability |
|---|---|---|
| Original message and headers | Linked to the evidence reference | Every mode |
| Attachment fingerprints | SHA-256 per document | Every mode |
| Sending timestamp | Observed when MailCerty receives the message | Every mode |
| Delivery-server response | Recorded when returned by the receiving infrastructure | When available |
| Protected content access | Successful controlled access only | Protected modes |
| Explicit acknowledgement | Voluntary recipient confirmation | Acknowledgement mode |
| Identity journey | Planned ID Nixa result and separate certificate | Not enabled in production |
| Evidence certificate | PDF timeline and technical references | Every completed file |
| Integrity verification | Fingerprints can be checked against the exported file | Every completed file |
| Workspace tracking | Search, status, quotas and downloads | Account workspace |
FIVE EVIDENCE LEVELS
The interface makes the difference between transport evidence, controlled access, acknowledgement and identity verification explicit.
| Capability | Discreet proof | Notified copy | Protected content | Acknowledgement | ID Nixa delivery · planned |
|---|---|---|---|---|---|
| Recipient notified | — | ✓ | ✓ | ✓ | Planned |
| Content kept behind access control | — | — | ✓ | ✓ | Planned |
| Explicit recipient action | — | — | Access | Acknowledgement | Planned |
| Identity check | — | — | — | — | Planned |
| PDF evidence file | ✓ | ✓ | ✓ | ✓ | Planned |
The ID Nixa MailCerty production integration is not enabled yet. This column describes the target journey only.
FROM MESSAGE TO EVIDENCE
Discreet proof, notice, protected content, acknowledgement or registered electronic mail (LRE).
Use MailCerty from the workspace, Outlook, Thunderbird or an evidence address.
Message, recipients and attachments receive one evidence reference.
No account is required to access the delivery page.
No opening or acknowledgement is claimed before it actually occurs.
Search the workspace and download the available PDF certificate.
REAL-WORLD EXAMPLES
Each scenario names the sender’s action, the recipient’s journey and what the evidence file can show.
The notification contains no sensitive file; the content stays behind the configured check.
The log separates the notice, code validation and actual access to protected content.
The intended recipient receives instructions to open the file after the configured access check.
Successful access is dated and linked to the message; a code alone is not described as civil identity verification.
The sender prepares the message and files in their usual tool, then selects confidential delivery.
The evidence file keeps the content reference and observed access events together.
No. The notice directs the recipient to protected access.
No. Use ID Nixa registered electronic mail (LRE) when identity verification is required.
Yes. They remain linked to the controlled content.
MAILCERTY
The Free plan provides essential email evidence. Business and On-Premise scopes can be reviewed with our team.