Transparency
What we log
To show you what happened to each email, we keep a short record of every message for 30 days. This page lists each field, what is left out and how everything is deleted.
The message log
Every message that comes in or goes out through mxproxy writes rows to your team’s log (one per destination). Each row has:
| Field | What it is |
|---|---|
| Date and time | When it happened |
| Direction | Inbound (reached your domain) or outbound (delivery to a destination, or sending through your SMTP) |
| Sender | The envelope sender; on a forwarded delivery, the SRS address we create |
| Recipient and destination | The address on your domain and the inbox or channel it went to |
| Subject | The message’s subject, up to 255 characters |
| Size | In bytes |
| Status | Accepted, rejected, spam, delivered, deferred, failed or skipped (channel summary not sent) |
| Detail | The technical reason: the spam score, the destination server’s reply, the limit reached |
The log does not hold the message body, the attachments or the IP of whoever sent it.
How long
| What | How long |
|---|---|
| Message log | 30 days, deleted by an automatic cleanup that runs every hour |
| Message content in the delivery queue (headers, body and attachments) | Only while delivery is pending: deleted when the destination confirms delivery, or when we create the bounce (permanent refusal, or giving up after at most 5 days of retries) |
| Queue record, without content (envelope sender, recipients, status, attempts, last error, size and timestamps) | 30 days, by the same cleanup |
| Summaries sent to channels | We do not keep the summary; the message stays in the channel queue only until the summary is sent (or we give up), and then its content is deleted |
| Daily message counters (numbers only) | As long as the team exists: they enforce the plan limits |
| Server technical records (errors, refused SMTP logins with the IP and the username) | For a limited time, as the Privacy Policy says |
Note: after delivery, the queue keeps only the record without content. The forwarding time on the status page comes from it, summed across all customers. The queue itself does not show in the dashboard or the API: what you see there is the message log.
Backups
We back up the database daily. A backup is a snapshot of the day: it includes the queue and the log at that moment, including the content of messages still waiting for delivery when the copy was made. So something deleted from the database still exists in earlier copies until they rotate out of the backups.
How to see and delete it
- In the dashboard: the Logs page shows your team’s 30 days, filtered by domain and status.
- Through the API:
GET /api/v1/logs, with an API token that has the log read permission (API reference). - Deleting it early: there is no button in the dashboard, and deleting a domain does not delete its history. Ask at contato@mxproxy.dev and we delete your team’s rows.
On the website
The website uses no tracking cookies or analytics. We count visits to the tools and guides only as a number per page and day, with no IP, browser or cookie. The full list of what we keep about your account is in the Privacy Policy; the path of each message, in Do you read my email?
Frequently asked questions
How long is the message log kept?
30 days. An automatic cleanup runs every hour and deletes older rows.
Does the log keep the email’s content?
No. The log has the sender, recipient, destination, subject, size, status and a technical detail. The full content is only in the delivery queue, while delivery is pending, and is deleted when it ends; it is not shown in the dashboard.
Can I delete my log before the 30 days?
There is no button for it in the dashboard, and deleting a domain does not delete its history. Ask at contato@mxproxy.dev and we delete your team’s rows.
Do you log the IP of whoever emails me?
Not in the message log. The sending server’s IP is in the message’s own Received header, which goes on to your inbox and stays in the queue only while delivery is pending.
What about backups?
We back up the database daily. A backup holds what was in the queue and the log that day, including the content of messages still waiting for delivery, so something deleted from the database still exists in earlier copies until they rotate out.
Want to try it with your domain? The free plan needs no card. Create a free account