Android App Privacy Policy

Last updated: 9 September 2026

This policy covers TempMailPortal Temporary Email, 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, optional usage and crash reporting, and advertising on reading guides.

The Android release is being prepared. This policy describes the app's intended release configuration; it does not mean the app is already available on Google Play. 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.
• This release contains no analytics or crash-reporting SDK. No usage statistics or diagnostic reports are collected or transmitted, and the corresponding settings are shown as unavailable.
• The inbox, message reader and settings do not display ads. Educational guides may display an AdMob banner after the applicable advertising consent flow.
• A temporary inbox is not confidential. Anyone who requests the same address can obtain access. 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. The Android app displays plain text and does not render a sender's HTML or fetch remote images from a message.

Messages normally become unavailable after about 24 hours. 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 stateless mailbox token or prevent later messages arriving at the same address. Forget address removes the active address and token from this device; 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.

What stays on your device

The active address and access token are stored in an encrypted local file using a key protected by Android Keystore. This file is excluded from Android backup. Privacy preferences are also stored locally. The app does not deliberately save message bodies as an offline archive. Device encryption does not make the underlying public inbox private.

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.

Usage analytics and crash reports

This release of the app contains no analytics or crash-reporting library at all. No usage events, screen names, crash traces, diagnostic state or installation and session identifiers are gathered or sent anywhere. The Usage analytics and Crash reports settings appear in the app but cannot be switched on, because there is nothing behind them to enable.

If a diagnostics library is added in a future version, it will be off unless you turn it on, this policy will be updated before that version is published, and the Google Play Data safety declaration will be updated to match.

Advertising and consent

AdMob advertising is limited to substantial educational guides. We do not place ads beside private received messages, require watching an ad to read mail or copy a code, 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 Privacy screen when that option is available. Your optional Analytics or Crash reports switches do 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 [email protected] or [email protected] 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.