Privacy summary
Web temporary email requires zero signup. Password-locked inbox keys (tbx_pw_…) are encrypted strictly inside your browser. The Outlook/IMAP Inbox Viewer is 100% stateless and never stores credentials. Google Sign-In is optional and used solely to issue free 100/day MCP API keys.
1. Temporary Email & Local Browser Storage
When you use Tempboxy’s temporary inbox on tempboxy.com, we do not ask for your name, real email address, phone number, or password. Your active inbox list, theme choice (Studio Dark or Paper Light), and sound/shield preferences are stored locally in your browser’s localStorage so your session survives page refreshes. You can clear them anytime by burning your inbox or clearing browser storage.
Incoming emails are routed through external mail infrastructure so messages can be delivered to live .com and .edu.pl domains. Do not use disposable email for confidential legal, medical, financial, or government communications.
2. Recovery Tokens & Client-Side Password Locks
- Signed Recovery Tokens (
tbx_v1_…): Tempboxy seals your mailbox session identifier and chosen TTL inside an HMAC-SHA256 signed token. We do not maintain a public directory of active addresses. - Password-Protected Inboxes (
tbx_pw_…): On /temp-mail-with-password, your password is used exclusively inside your browser via Web Crypto PBKDF2-SHA256 (120,000 iterations) and AES-256-GCM. Your password is never transmitted to or stored on Tempboxy servers.
3. Stateless Outlook OAuth2 & IMAP Inbox Viewer
When you use /inbox-viewer to read an Outlook/Hotmail mailbox (via Microsoft OAuth2) or another email domain (via IMAP TLS), your tokens or App Passwords are sent over HTTPS strictly in memory to fulfill that single fetch request and discarded immediately afterward. Responses carry Cache-Control: no-store. Tempboxy never logs, writes to disk, or persists your Outlook refresh tokens, access tokens, IMAP passwords, or fetched personal emails.
4. Google Sign-In for Hosted MCP & API Keys
Signing up at /signup is optional and only required if you want a free 100/day key for the hosted MCP server (/mcp). When you sign in with Google via Firebase Authentication (project tempboxy), we verify your Google ID token and store only:
- Your Firebase Google UID, verified Google email address, and display name.
- Your Tempboxy API key (
tbx_k_…), encrypted at rest with AES-256-GCM alongside its SHA-256 lookup hash. - Daily UTC call counts used to enforce the 100 free daily usage limit.
We never request access to your Gmail messages, contacts, or Google Drive. You can rotate your API key anytime on /signup or request full account record deletion via /contact.
5. Analytics, Logs & Email Diagnostic Tools
- Firebase Analytics: Tempboxy uses Firebase Analytics (Google Analytics measurement ID
G-1BBSQE74YS) to measure aggregate traffic and anonymous feature usage (such as page views, inbox creations, and OTP copies). We never send email contents, addresses, OTP codes, or passwords to Analytics. - Rate-Limiting & Security Logs: Our server applies temporary in-memory IP rate limits to prevent abuse on
/api/v1,/mcp,/api/viewer/fetch, and/api/contact. - Free Tools (/tools): SMTP Header Analyzer, RFC Format Validator, Spam Score Audit, and HTML Previewer execute 100% locally in your browser. Only live MX/SPF/DMARC queries contact
/api/tools/dns-mxwith the requested domain name.
6. Tracker Pixel Protection
Inside the inbox reader, HTML emails render in a sandboxed iframe with scripts disabled and remote image requests blocked by default via Content Security Policy to help stop 1×1 open-tracking pixels from revealing your IP address to email senders.
7. Your Rights & Contact
If you reside in the EEA, UK, California, or another jurisdiction with data-protection rights, you may request access to or deletion of any stored Google MCP account record or contact submission by writing to support@tempboxy.com or using /contact.