Your data
Privacy policy
What Temp Mail processes, where it is stored, and the limits of the protection provided.
Version 5.0.1 · Updated 9 October 2026
1. Who operates the service
Temp Mail for iOS (bundle identifier com.mail.inbox, App Store ID 1611523684) is provided by Hoang Dai (“we”, “us”). This policy covers the redesigned v5 app, its mail service and this support website. Contact temp-mail@1timetech.com about privacy or data requests. Older releases may use different features and SDKs.
2. Mail service and technical data
To create, activate and read a temporary inbox, our mail backend processes the requested address, its access identifier and incoming messages, including sender, recipients, subject, body and message headers. You do not need an app login or a personal email address to start using the app.
The mail API at mail-server.1timetech.com and delivery infrastructure also process connection information such as IP addresses, request timestamps, user agents and operational logs to deliver mail, diagnose failures and prevent abuse. We do not promise that IP addresses are never logged.
Messages pass through mail delivery and hosting providers. Transport to the app uses HTTPS. Local body encryption does not make email end-to-end encrypted or prevent the mail service from processing incoming content.
3. Data on your device
- Mailbox addresses, account labels, access identifiers, expiry and lock state, and message metadata such as sender, subject and read state are stored in a local SQLite database. This database is not encrypted by the app at the database level.
- Downloaded message bodies are stored as encrypted files using XChaCha20-Poly1305. The key is stored in the iOS Keychain with a device-bound accessibility setting. This does not guarantee recovery after device loss or migration.
- Preferences, including language, reading mode and automatic image loading, are stored locally. Earned restoration credit is also saved locally so a failed restoration request can be retried.
4. Local authentication, camera and sharing
Per-email locking uses iOS local authentication. The app receives the authentication result, not your biometric template or device passcode. Locks apply to this installation only; someone with an account QR/access identifier may use another installation. An address is not an exclusive, password-protected account.
The camera is used to decode QR codes on device. The scanner does not capture or save a photo. Email QR contains the address; Account QR contains the address and an access identifier inside an encoded app link. Encoding is not encryption. Treat an account QR or link as sensitive access information.
Copy, QR sharing and plain-text message export occur when you choose them. Export files are temporary in the app cache and are removed after sharing completes in the normal flow; interrupted operations may leave temporary files until later cleanup. Copies in the clipboard or destination app are outside our control.
5. Images, links and message display
The default reader is Controlled, with a filtered WebView alternative. Both filter active email content such as scripts, frames and forms; rendering is not guaranteed to reproduce every email layout.
Automatic external-image loading is enabled by default on new installations. Your saved preference is respected. Image requests may disclose your IP address, device/network information and a unique image URL to the image host, allowing a sender to infer that a message was opened. Switch automatic loading off in Settings to choose whether to load images for a message. Images already loaded may be reused from the session cache.
External message links open only after confirmation. Visiting them discloses information to the destination under its own privacy policy. Blocking active HTML does not make all message content or links trustworthy.
6. Analytics, diagnostics and advertising
We use Google Firebase Analytics to understand app use and Firebase Crashlytics to diagnose errors. These SDKs may process app/installation identifiers, device and app versions, usage events and crash information. Our feature-event instrumentation is designed not to send email addresses, message subjects, message bodies or account-access links as analytics parameters.
Google AdMob and its User Messaging Platform (UMP) provide advertisements and applicable privacy messages. The Google Mobile Ads SDK may process IP addresses, device/app identifiers, approximate location derived from IP, diagnostics and ad interactions. Where applicable, the app completes the UMP consent flow before requesting Apple's App Tracking Transparency (ATT) permission. Only when the required UMP choices and ATT permission are both granted may the app access IDFA, enable advertising-related Firebase consent signals and request personalized ads. If permission is denied, unavailable or incomplete, ad requests remain non-personalized and the app continues to work. SKAdNetwork may support attribution without IDFA.
You can change ATT permission in iOS Settings. Where UMP requires an in-app privacy options entry point, Settings shows Privacy options so you can reopen the Google form and change your choices. The app does not provide a switch to disable Firebase Analytics or Crashlytics. Contact us with a privacy request; device settings and Google controls provide additional choices but are not a substitute for app-specific consent controls.
Read How Google uses information from sites or apps that use its services, Google's Privacy Policy, and Firebase privacy information.
7. Purchases and subscription verification
Apple processes Premium payments through your Apple Account. We use Qonversion to check purchase receipts and subscription status, restore eligible purchases, provide Premium access and understand subscription performance. This processing can include purchase and transaction history, product identifiers, renewal and expiration information, app/user and device identifiers, and technical information such as IP address, operating system, device model, app version and locale.
The Qonversion SDK initializes when the app starts, so technical identifiers may be processed even if you do not buy Premium. We do not send temporary email addresses, message contents or account-access QR links to Qonversion as user properties. The app does not collect your Apple Account password or full payment-card details. See Qonversion's Privacy Policy and Apple's App Store privacy information.
Premium removes ad display; it does not disable Firebase Analytics, Crashlytics or subscription verification. Purchase and subscription records follow the relevant provider retention policies and may be retained for verification, refunds, accounting or legal obligations. Removing local app data does not erase those records or cancel an Apple subscription. Contact us about access or deletion requests relating to data processed on our behalf.
8. Purposes, sharing and international processing
We process data to provide requested mail features, maintain reliability, address support requests, prevent abuse, operate advertising and provide optional subscriptions. Where applicable law requires consent for particular processing, consent is the relevant basis; providing requested services, legitimate operational/security interests and legal obligations may support other processing, subject to applicable law.
Data is disclosed to service providers involved in mail delivery, hosting, analytics, diagnostics, advertising and subscription verification; to recipients or services you choose through sharing and links; and where required by law or necessary to address abuse or protect rights. We do not offer mailbox contents for sale. Advertising-related processing may be treated differently under regional privacy laws; contact us regarding applicable opt-out rights.
Our infrastructure and providers may process information outside your country, including in the United States. Provider processing and applicable safeguards are described in their published privacy and data-processing terms.
9. Retention and deletion
The free plan's 48-hour activation timer and Premium address benefits are separate from server message retention. Server messages are subject to automated, age-based cleanup and operational limits; they may become unavailable independently of the address timer. Restoring an address does not recover messages already removed from the server. We do not promise deletion of all server logs, backups, shared copies or local data precisely when an address expires.
Local mailbox and message records remain until you remove them or delete the app's data. Clearing the private cache removes downloaded body files and their key, not all mailbox/message metadata. Removing an inbox removes its local records and associated cached bodies, not server data or exported copies. iOS backups and Keychain behavior can differ from ordinary app storage.
Provider analytics, diagnostic and advertising records follow the applicable provider retention settings and policies. Support correspondence and operational records are retained as needed for the request, service security and legal obligations. Ask us about a specific data category or deletion request; identity/access verification may be necessary, and we cannot promise to identify every anonymous installation or recover already-deleted data.
10. Your choices and rights
Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, obtain a portable copy, withdraw consent, or complain to a data protection authority. Contact us to exercise applicable rights. Withdrawing consent does not undo processing already lawfully performed. We may need proportionate verification, and legal exceptions may apply.
See Privacy choices & deletion for the actual controls available in this version. Do not send us device passcodes, one-time verification codes or full account QR links in an initial request.
11. Children, website and changes
The service is not directed to children under 13. If you believe a child has provided personal information, contact us so we can assess and address it. Applicable local age and guardian-consent requirements also apply.
This website is served by Firebase Hosting. We do not embed analytics, ad scripts, external fonts or marketing cookies on these pages. The hosting service still processes network requests and IP information to deliver and protect the site. External links have their own policies.
We will update this page when practices change and provide additional notice or obtain consent where required. The date above identifies this revision; using the service is not blanket consent to every form of data processing.