Written and reviewed by the team operating TempMail Cloud. Product claims are checked against our live service and our editorial standards.
A TempMail Cloud inbox is not publicly readable merely because someone knows its email address. Access can come from mailbox credentials, an authorized owner-account session or an active share link whose permission checks pass. Creating a public-link share deliberately changes who can read the mailbox.
Private from whom?
| Person or access route | What matters |
|---|---|
| A sender who knows the address | Knowing the address alone does not open the inbox |
| Someone with the mailbox password | They may be able to open that mailbox |
| Someone using an authorized owner account | The account can open its owned inboxes |
| Someone with an active public share link | The link permits a read-only view of the shared mailbox |
| A restricted-share recipient | They must sign in with the permitted registered account email |
| The service operator | Server-held data remains subject to operation, administration and the privacy policy |
Read-only sharing does not make message contents harmless. A reader can copy an OTP, reset URL or text even though the interface does not let them delete mail or change the password.
A practical privacy check before using an inbox
Confirm the full address and save the credentials somewhere protected. Review whether the mailbox is owned by your account and whether any share links are active. Use a dedicated low-risk inbox for a reviewer instead of sharing one that also receives personal recovery messages.
For example, a QA reviewer given a restricted link can see stored test messages and later messages arriving in that same inbox. The link is not limited to the email selected when it was created. Deactivate it after the review and use a different mailbox when you need a different access boundary.
Browser storage also matters
The browser may retain mailbox session references and known passwords for convenience. Leaving that browser profile accessible to someone else can expose access even when the server stores password hashes. A password hash on the server is not a promise that no credential exists anywhere in the browser.
Avoid public computers for reusable access. If you still need an inbox, secure its credentials before clearing site data. Changing the mailbox password does not change the owner-account password and does not automatically revoke every existing session or share link. Use the recovery guide for the correct access path and contact support about suspected compromise.
What the HTML viewer does not guarantee
Received HTML is displayed within a restricted viewer to contain active content. That does not make a sender trustworthy or guarantee that remote images cannot contact another server. Do not open unexpected links or attachments just because they are inside a password-protected inbox.
Retention is separate from access control
An active reusable mailbox may remain available for later messages under the current retention policy. Removing a mailbox from an account or forgetting it on a device is not the same operation as deleting its messages or obtaining permanent server deletion.
Do not use this service for irreplaceable recovery, financial, medical, legal or confidential records. Privacy separation is useful for low-risk receiving; it is not anonymity, end-to-end encryption or a guarantee against operational access.
See share permissions, access recovery and safe-use guidance for the controls relevant to your situation.