Skip to main content

Hosted browser access

TempInbox saves inbox addresses and signed access tokens in your browser profile. Mail reads resolve the mailbox from the verified token, not from an address supplied by itself. Knowing an address does not grant read access. There is no inbox-password feature or supported cross-device recovery. Anyone controlling the browser profile or holding its tokens may be able to read the inbox. Do not share tokens or export hosted browser credentials into CI.

Self-hosted implementation

An instance you operate may return an address-scoped JWT when creating an inbox. Its mail endpoints can validate a bearer token or browser cookie, depending on the deployed version and configuration.
Confirm the signing key, token expiry settings, creation requirements, and routing for your deployment. Cookie lifetime and token validity are different; neither guarantees that stored messages remain available. Do not assume a universal seven-day token validity period or permanent mailbox access. The hosted TempInbox service has no supported public automation API. Internal endpoint details and self-hosted examples are not a hosted compatibility contract.