TEMPMAIL CLOUD

Inbox Reader Extension Privacy

What the TempMail Cloud browser extension reads, stores and sends, and how to remove its access.

The TempMail Cloud Inbox Reader has one purpose: display incoming message headers from the single inbox authorized by your receiving API key. It does not create mailboxes, send email, read browsing history or access arbitrary websites.

Data used by the extension

  • Authentication information: the API key you enter is kept in Chrome's extension session storage and sent in the Authorization header only to https://tempmail.cloud. It is not placed in a URL or synchronized through Chrome sync.
  • Personal communications: the extension receives and displays message subjects, sender addresses, receipt times and message identifiers from your chosen inbox. These headers can themselves contain personal or sensitive information. It does not request full message bodies.
  • Local display state: visible headers are held by the popup while it is open. The extension does not write message lists to persistent extension storage.

Closing the popup does not remove its session key. Restarting the browser normally clears session storage. Use Forget key to remove it immediately from the extension, then revoke the key on the website if you want all uses of that key to stop.

Permissions and network access

The storage permission provides session storage for the key. Host permission for https://tempmail.cloud/ lets the extension call that site's receiving API. The package contains no content scripts, background listener, remote executable code, advertising or analytics. Website request handling may process ordinary operational metadata such as IP address and request timing under the website privacy policy.

Use and sharing

Extension data is used to authenticate the requested inbox and display its headers. We do not sell extension user data, use it for advertising, or use it to determine creditworthiness or lending eligibility. We do not transfer it for unrelated purposes. Our use of extension data is limited to providing this user-facing feature, security and applicable legal requirements, consistent with the Chrome Web Store User Data policy.

The inbox and messages already exist on TempMail Cloud. Installing or forgetting the extension does not independently delete those server records. Mailbox retention, administrative recovery and backup handling follow the website policy. A receiving key expires after 30 days, may be revoked earlier and stops working if its inbox becomes unavailable. A timed inbox's shorter deadline takes precedence.

Your controls

  1. Prefer a message headers only key from the website's Receiving API dialog.
  2. Use Forget key to clear extension access on this browser.
  3. Revoke the key in that same website dialog to disable all copies.
  4. For mailbox/data questions, contact TempMail Cloud using the contact form. Do not submit an API key, password or private message in the form.

Developer distribution

Download version 1.0.1. The downloadable package is for manual developer installation. A Chrome Web Store listing has not yet been published. Manual installations do not update automatically. Our integration guide describes setup and current limitations.

Updated September 14, 2026. This page describes the extension; Google's browser and store services operate under Google's own policies.