# Privacy Policy — TempFox Multi Mail + OTP (Web Edition)

Last updated: July 31, 2026

## Data collection

The TempFox web app does not collect, sell, share, or transmit personal user data for analytics, advertising, profiling, or tracking. It has no backend server and no analytics code.

## Local data

The following app state is stored locally in your browser using `localStorage`:

- generated temporary email addresses and provider identifiers;
- temporary provider session tokens and provider-created mailbox credentials;
- recent-inbox history and read/unread state;
- locally generated signup usernames and random passwords;
- app settings and the last detected verification-code state.

This local data can be deleted with **Settings → Reset local data**, by clearing the site's storage, or by closing the private-browsing window.

## Provider requests

To perform its user-requested temporary-mail function, TempFox communicates directly with the selected temporary-mail provider. Requests may contain a generated temporary address, provider-issued mailbox/session token, message identifier, or provider-specific account credential. These values are operational data created for the temporary inbox, not personal data collected for TempFox.

Each provider controls its own server logs, retention, terms, and privacy practices. TempFox has no server and receives no copy of provider traffic.

## Website filling

Because web pages cannot access other tabs, the web edition does not fill forms on other websites and does not auto-paste codes. Detected verification codes are shown as copy cards so you can paste them yourself. (Auto-paste and signup-form filling are available only in the Firefox extension, where they never submit forms.)

## Email content

Email content is requested directly from the selected temporary-mail provider and displayed as inert text. TempFox does not load remote email images, scripts, iframes, or tracking pixels.

## Notifications

If you enable new-mail notifications, your browser prompts for notification permission. Notifications are delivered by the browser only while the page is open. No notification data is sent to TempFox.

## CORS relay

Most provider APIs allow direct browser requests. For providers that block them, the app retries through a relay when the "CORS relay fallback" setting is enabled (it is on by default). The relay chain is: a same-origin relay if one is deployed with the site, then any custom relay URL you configure, then public relays. Only requests that failed a direct attempt are relayed, and the setting can be disabled for strict privacy.

A relay sees the same provider API traffic the browser would have sent directly — generated temporary addresses, provider-issued tokens, and message identifiers — and no other personal data. Public relays are third-party services with their own logs and terms; for full control, deploy the included `relay/` folder to your own host and set its URL in Settings.

## Sensitive use

Temporary email is unsuitable for banking, payments, health data, identity documents, account recovery, purchases, or confidential communication.