Android App Privacy Policy
Last updated: 15 October 2026
This policy covers TempMailPortal: Temp Mail, the Android app developed by Avinash Verma under the Ynoxa name, with package identifier com.ynoxa.tempmailportal. It explains the temporary-email service, data kept on your device, usage analytics, crash reporting and advertising in the app.
This policy describes the Android app, including the version 1.4.4 update. The browser website has its own website privacy policy.
The choices available to you
- No account, primary email address, password or phone number is needed to create a random temporary inbox.
- Usage analytics and crash reports are on by default starting in version 1.4.4. You may turn either off separately in Settings, without an extra app prompt. Earlier versions had analytics off by default and no crash-reporting SDK.
- From Android version 1.4.2, app screens may display one AdMob banner above bottom navigation after the applicable advertising consent flow. Earlier versions limit banners to guides. An occasional interstitial may appear when you choose Next guide after reading; it does not block inbox actions.
- New random inboxes use private bearer credentials: knowing the address alone does not grant access. Custom-name and older inboxes remain public; anyone requesting the same address can obtain access. This is still a short-lived, low-stakes service. Do not send it financial, medical, identity or other sensitive information.
Email processing and retention
The app communicates over HTTPS with the TempMailPortal API. The service processes the temporary address and mailbox access token, and receives sender details, subject, message text, formatted body and attachment metadata so mail can reach the correct inbox. Cloudflare provides the receiving, application and storage infrastructure. Plain text is the default. An optional formatted view removes links, images, scripts, styles, forms and external resources. It cannot verify a sender or make a malicious message trustworthy. Attachment access is offered in Android only when a file is retained in storage. Image and plain-text previews are processed in app memory, with no external viewer or active links; files you save remain in the location you choose until you delete them.
New private inboxes let you choose a message lifetime of 10 minutes, 1 hour or 24 hours. Older and custom-name inboxes use 24 hours. Private inbox credentials expire after 30 days. A scheduled cleanup removes expired stored messages, so the message lifetime is not a promise that every provider log or backup disappears at that exact moment. Clear messages requests removal of the current inbox's stored messages sooner. Wait for confirmation: a failed network request is not a confirmed deletion.
Clearing messages does not revoke the mailbox token or prevent later messages arriving at the same address. Forget address removes the active address and token from this device and selects another saved address if available; it does not itself delete the server's messages. Clear the inbox before forgetting it if you also want to request server-side message removal. A new address does not recover the old inbox.
We do not sell received messages or deliberately send their contents to advertising or any other service. The service is receive-only. There is no outbound email composer, permanent account archive, or guaranteed recovery of expired mail.
Accounts, app verification and daily allowances
The Android security update uses Firebase Authentication and Google Play Integrity through Firebase App Check. Guest access creates a temporary Firebase identity automatically, without asking for an email address or Google sign-in. This identifier supports inbox ownership and guest usage limits. Optional Google sign-in links this identity to your Google account and unlocks higher allowances shared across devices. Only if you choose Google sign-in do Google and Firebase process your Google profile and email address; TempMailPortal never receives your Google password. Google processes app and device integrity signals. Email message contents are not sent as part of those checks.
Our API verifies the app and account tokens and stores an account identifier, the inboxes it owns, and daily usage counters. Counters include requests, new inboxes, attachment transfer bytes, incoming messages and incoming message bytes. Detailed daily counters are retained for up to seven days plus the cleanup interval. Private inbox ownership lasts until closure or the inbox expiry. The allowance follows your account across devices.
Guest identities cannot be recovered after app data is cleared or the app is uninstalled unless previously linked to Google. You can close an inbox permanently in the updated app's Settings. You can delete a TempMailPortal account and its server inboxes in Settings or the account dashboard; recent sign-in may be required. Deletion removes server messages, attachment objects, mailbox access records and usage counters, followed by the Firebase account. This does not delete your Google account. A minimal closure record containing the account identifier and closure time is retained to prevent reuse of old sessions. If any step fails, retry and contact support if necessary. Email support for deletion help if you cannot sign in. Local files previously saved or shared are not removed from their destinations.
What stays on your device
Up to five saved addresses and access tokens are stored in an encrypted local file using a key protected by Android Keystore. Keeping a previous address is optional. Foreground refresh checks the selected inbox; optional background alerts check all saved inboxes. This file is excluded from Android backup. Privacy and display preferences, and the time of the most recent guide interstitial attempt for frequency limiting, are also stored locally. Labels, pins, read marks and stars are saved with the encrypted inbox data. Search text stays in memory. Their values are not sent to analytics or advertising services. Starring a message does not extend its retention. QR codes are generated on the device and contain only the address, never its access token. The app does not deliberately save message bodies as an offline archive. App lock uses Android device authentication and protects access through this app; it does not change whether an older or custom-name inbox is public.
Content you choose to copy goes to the Android clipboard, including an address or suggested code. When you choose Share, Android lets you select another app to receive the address. Those are actions you initiate; the chosen destination's own privacy practices then apply. Code suggestions are extracted on your device, can be mistaken, and are not transmitted as analytics events.
The app does not request contacts, SMS, microphone, camera or precise-location access. Networking is required for the inbox. Advertising SDKs can process advertising identifiers and approximate location derived from an IP address, as described below.
Device pairing and optional alerts
A private inbox owner can create a one-use pairing code, valid for five minutes, to grant another device signed into the same account access to the same inbox in the security update. Treat that code as a secret. The server stores hashes of access tokens and pairing codes, inbox expiry and session ownership. The original owner device can revoke paired sessions and pending codes. Forgetting the owner credentials may make this management access unrecoverable.
Background alerts are off by default and request notification permission when needed. If enabled, Android schedules checks approximately every 15 minutes or later. Alerts contain no address, sender, subject, message text or verification code. Hashed message identifiers and the alert start time are retained locally to avoid duplicate alerts. Turn the setting off to stop checks and clear that local history. Short-lived messages can expire before a background check.
Instant alerts for private inboxes are a separate, off-by-default option using Firebase Cloud Messaging. Enabling them uses the existing Firebase installation and sends technical delivery information to Google. Our Cloudflare service stores the device delivery token alongside the private inbox session until unsubscription, revocation, expiry or an invalid-token response. Notification payloads contain a hashed inbox identifier and random message identifier, never an address, sender, subject, body or verification code. They are used for app functionality, not advertising or analytics.
Turning instant alerts off immediately suppresses them in this app and schedules removal of subscriptions and the messaging token when connectivity permits. The installation identifier remains in use for app verification; disabling notifications does not disable account security. Notification delivery depends on Google Play services, network access and Android restrictions. See Firebase privacy and retention information. Locally hashed alert history is used to suppress duplicates across notification methods.
Usage analytics and crash reports
Usage analytics is on by default in version 1.4.4 and later. While enabled, Firebase Analytics receives an app-instance identifier, masked IP address used to derive coarse location, app, device, installation and session metadata, and app-lifecycle events. The app also sends fixed events for creating an inbox, refreshing, opening a message, clearing an inbox, copying or sharing an address, copying a possible code, opening a guide, banner-ad results and generic operation failures. Explicit screen events use only the fixed names Inbox, Message, Addresses, Guides and Settings, plus the identifiers of the three built-in guides. The Message screen name is generic; no message identifier is included. You can turn it off in Settings without losing inbox features.
Analytics events never contain an email address, mailbox or message identifier, sender, recipient, subject, message body, attachment, verification code, search text, label, bearer token, Google account identifier or TempMailPortal account identifier. The app sets no Analytics user ID or custom user property. Analytics advertising-ID collection, ad storage, ad user data and ad-personalization consent remain disabled. If you turn analytics off, collection stops and the app resets its local Analytics data and app-instance identifier. Google may retain data already received under its applicable terms and retention settings.
Crash reports are on by default in version 1.4.4 and later. Firebase Crashlytics receives crash, non-fatal error and application-not-responding diagnostics, which can include stack traces, app and device state, installation identifiers and breadcrumbs from enabled Analytics. We do not add email content, mailbox addresses, access tokens or account identifiers as Crashlytics custom keys or logs. Turning Crash reports off in Settings stops automatic upload on the next app launch; the app also requests deletion of unsent reports held locally. Reports already received by Google may remain under its retention rules. Crash reporting and analytics are separate switches. Optional notification identifiers and advertising SDK data are described separately on this page. See Firebase privacy and retention information.
The app may offer Google Play's in-app rating after you successfully copy an address on three separate days. It makes this automatic offer at most once per installation, while you are in Inbox. Whether the dialog appears is controlled by Google Play. The app also has a direct Play listing link in Settings. Local review timing stores only the number of qualifying days, the last qualifying day and whether the offer was made; no mailbox content is sent for this choice.
Advertising and consent
From Android version 1.4.2, bottom banners may appear on the inbox, message reader, saved addresses, guides and Settings screens. They occupy a separate area above navigation. We do not require watching a full-screen ad to read mail, copy a code or download an available attachment, or insert a full-screen ad when you open the app. Ad availability depends on the app's advertising review, consent and available inventory.
Google's User Messaging Platform supplies applicable advertising privacy choices. You can use Manage advertising privacy on the app's Settings screen when that option is available. The Usage analytics switch does not grant advertising consent.
When advertising is requested, the Google Mobile Ads SDK may collect and share IP addresses, approximate location, app interactions, diagnostic information and device or account identifiers for advertising, measurement and fraud prevention. A non-personalized ad does not mean no technical data is processed. See Google Mobile Ads data disclosures and how Google uses information from partner apps.
Service operations, support and other providers
Our infrastructure providers process technical connection data such as IP addresses, request times and error information to operate the API, limit abuse and maintain reliability. These operational records have separate retention from temporary messages. If you email support, we process the contact details and information you choose to send for that request. Please do not include a mailbox token, verification code or sensitive message.
Google and Cloudflare may process information in countries other than yours under their applicable terms and safeguards. For SDK-specific categories, see Google Mobile Ads Android data disclosures. We do not claim that all app data is erased within 24 hours: that short lifetime describes temporary messages, not advertising data held by Google, operational logs or support correspondence.
Children, rights and contact
The service is not directed to children and is not intended for people under 16 or a higher applicable minimum age. It is unsuitable for sensitive or lasting accounts regardless of age.
Depending on your location, you may have rights to access, correct, delete or restrict personal information, withdraw consent or object to certain uses. Contact privacy@tempmailportal.com or support@tempmailportal.com with the app version and a description of your request. We will explain what can be identified and acted on without asking you to publish private messages.
Material changes to these practices will update this page's date and, when needed, the in-app explanation or consent request. Changes to a policy do not substitute for consent where a separate choice is required. You can also read our Terms, Acceptable Use Policy and Editorial Policy.