Guide
Public inbox privacy, retention, and safety limits
The biggest rule for public inboxes is simple: if the message would be risky for a stranger to read, do not send it there.
Best for: Anyone considering temporary mail for privacy-minded or test workflows.
Public means publicly readable
A public temporary inbox can be opened by anyone who knows or guesses the address. That makes it convenient for testing, but unsuitable for secrets.
Retention is short, not private
Zumasia auto-purges messages after 8 hours. Short retention reduces leftover test data, but it does not make an inbox private while messages exist.
Safe patterns
Use generated test data, non-sensitive signup flows, and addresses that are easy for your team to trace during QA.
- Avoid account recovery and financial services.
- Do not receive personal documents.
- Do not treat public inboxes as secure storage.
FAQ
Are public temporary inboxes private?
No. They are public by design and should only receive non-sensitive messages.
Does auto-purge protect sensitive messages?
No. Auto-purge removes old content, but messages can be public before deletion.
What should I use public inboxes for?
Use them for QA, disposable signup checks, and short-lived non-sensitive workflows.