Temp Mail

Welcome to Temp Mail ("the Application", "the App", or "our Service"), designed, engineered, and published by Newgates ("Publisher", "we", "us", or "our"). Temp Mail is an Android utility application providing users with instant, disposable, temporary email addresses designed to protect personal inboxes from unwanted marketing spam, promotional clutter, tracking, and identity exposure.

This Privacy Policy establishes our factual, comprehensive technical standards regarding how data is handled across your use of the Temp Mail Android mobile application (co.newgates.tempmail) and its supporting edge cloud infrastructure. We have crafted this document to comply strictly with the Google Play Developer Program Policies, the Google Play User Data Policy, and Google Play's mandated Account Deletion Requirements.

Temp Mail operates as an inbound-only disposable messaging gateway. Understanding how the system operates technically provides clarity on why minimal data is handled:

• Temporary Mailbox Allocation: Users can generate random temporary email addresses or define custom handles on available domains (e.g., alias@domain.com). These addresses act as transient aliases.
• Inbound Routing via Cloudflare: External emails sent to your temporary address are routed securely through Cloudflare Email Routing directly into our isolated serverless processing pipeline on Cloudflare Workers.
• Ephemeral Database Persistence: Inbound message headers and sanitized bodies are stored in an encrypted distributed SQLite database (Cloudflare D1) associated solely with your anonymous installation identity or optionally linked Google account.
• Strictly Inbound-Only (No Outbound Email): Temp Mail does not provide SMTP outbound transmission, compose, or forwarding functionality. You cannot send, reply to, or blast outgoing marketing or spam emails through our infrastructure. This architecture prevents abuse and guarantees that no external personal contact books or outgoing message queues are created.

To allocate disposable inboxes, deliver incoming messages, and dispatch real-time notifications, Temp Mail processes the minimal data categories specified in the table below:

To eliminate ambiguity and guarantee compliance with Google Play's User Data privacy standards, Temp Mail explicitly refrains from accessing, collecting, or processing:

• No Real Personal Identifiers: We do not ask for or collect your real first/last name, home address, physical mailing address, or national identification numbers.
• No Mandatory Passwords: We do not operate a password database. Sessions rely on cryptographic client-side tokens.
• No Telephone Numbers: No mobile SMS verification or phone number harvesting is utilized.
• No Geolocation Data: We do not request, access, or track GPS coordinates, fine location, or coarse location (ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION).
• No Hardware Identifiers: We do not collect non-resettable hardware IDs such as IMEI, IMSI, MAC addresses, or Android Serial numbers.
• No Financial or Payment Data: Temp Mail does not request bank account details, credit/debit card numbers, or billing addresses.
• No Device Storage Scanning: We do not scan, inspect, or upload files from your external shared storage, photos, or document directories.
• No Contacts, SMS, or Call Logs: We do not request access to device contacts, SMS messages, or phone call logs.
• No Camera or Microphone Access: We do not request or utilize hardware camera or audio recording permissions.

Disposable email platforms are frequently targeted with malicious emails containing malicious JavaScript, tracking web beacons, and phishing attacks. To protect users, Temp Mail implements an automated MIME Sanitization Pipeline before any message is saved or rendered:

Multi-Stage Content Neutralization

• Executable Script Removal: All inbound HTML bodies are scrubbed using rigorous DOM sanitization rules. Script tags (<script>), embedded objects (<object>, <embed>), iframes (<iframe>), and inline JavaScript event handlers (such as onload, onerror, onclick) are permanently stripped.
• Tracking Pixel Neutralization: Known marketing tracking beacons, invisible 1x1 image web beacons, and dangerous external stylesheets are disabled to prevent third parties from logging your device's network IP address upon viewing an email.
• Isolated Android Rendering: In the Android client application, messages are rendered within sandboxed composables. The user can toggle between Plain Text view and sandboxed HTML view. External URLs within email bodies prompt a security confirmation modal before opening in the system browser.
• Local OTP Code Extraction: To streamline verification workflows, the app uses localized regex algorithms to identify and display one-tap verification OTP codes without exposing email content to external analysis engines.

Temp Mail implements a decoupled tripartite database schema designed to preserve user privacy while offering optional cross-device synchronization:

1. Default 100% Anonymous Mode

When you install Temp Mail, the app creates a random client-side Installation UUID. The server registers an internal user ID bound to an anonymous authentication provider. A cryptographic bearer token is issued to your device; only its SHA-256 hash is retained on the server. You can immediately create disposable inboxes and receive emails without sharing any personal information.

2. Optional Google Account Linking (Multi-Device Backup)

To solve the common problem of losing disposable inboxes when switching phones or reinstalling the app, Temp Mail offers optional Google Account Linking:

• Voluntary Action: Account linking is 100% optional. The user must manually navigate to Settings → Account Sync & Backup and tap Sign in with Google.
• Data Stored: When linked, our backend securely verifies Google's signed ID token via Google Play Services Auth and stores only your Google Subject Identifier (sub) and primary Google email address in our auth_identities table.
• No Access to Personal Google Data: We do not request, access, or store your Google password, contacts, Gmail inbox, Google Drive files, calendar events, or Google profile photos.
• Unlink at Any Time: You can disconnect your Google account at any moment within the app by tapping Unlink Google Account, reverting your session to local device state immediately.

Temp Mail utilizes Google Firebase Cloud Messaging (FCM) HTTP v1 API to deliver instant notifications when incoming emails or verification codes arrive.

Privacy-Safe Payload Architecture

Unlike standard email clients that transmit unencrypted subject lines and email previews across third-party push notification relays, Temp Mail implements a privacy-preserving push payload design:

• The payload sent across Google's FCM network contains only metadata trigger flags (e.g., type: NEW_MESSAGE, address_id, and message_id).
• Zero email body or sender personal data is exposed over the FCM wire.
• Upon receiving the silent push ping, the Android client securely wakes up and fetches the sanitized email payload directly from our encrypted backend API over TLS 1.3.
• Notification Control: You can enable or disable push notifications at any time via in-app Settings or by revoking the POST_NOTIFICATIONS runtime permission in Android OS system settings.

In accordance with data minimization principles, Temp Mail enforces strict automated data lifecycle policies:

• Ephemeral Mailbox Lifecycle: Temporary mailboxes are designed for short-term use. Inactive mailboxes expire automatically following system retention parameters (typically 24 hours to 7 days).
• Automated Background Cron Purge: Serverless cron jobs (address-expiration-service) execute continuously to identify expired addresses. Once an address expires or is deleted by the user, all associated received emails and attachment references are permanently erased from the D1 database.
• No Permanent Archives: We do not maintain offline tape backups, historical archives, or message transcripts. Once deleted by user action or automated expiration, data is irrecoverable.
• Local Room Database Cache: The Android app caches downloaded messages locally in private sandboxed Room SQLite storage on your device. Users can clear this cache instantly via Settings → Clear Message Cache.

We implement robust administrative, technical, and cryptographic safeguards to protect information against unauthorized access, alteration, disclosure, or destruction:

• Encryption in Transit: 100% of network communications between the Temp Mail Android app, Cloudflare Workers API, and Google Firebase servers are encrypted using modern Transport Layer Security (TLS 1.3 / HTTPS). Plaintext HTTP connections are strictly prohibited.
• Encrypted Edge Storage: Database storage on Cloudflare D1 utilizes AES-256 encryption at rest across Cloudflare's global edge infrastructure.
• Hashed Token Authentication: Bearer session tokens are transmitted over TLS and matched against one-way SHA-256 cryptographic digests in database storage. Plaintext bearer tokens are never persisted in the database.
• Administrative Route Hardening: Administrative maintenance and cron endpoints are isolated behind cryptographically random bearer secret headers (ADMIN_SECRET_KEY and CRON_SECRET).

We provide full user sovereignty over all data. Under the Google Play Account Deletion Policy, users have the right to delete their temporary mailboxes, messages, and associated accounts both within the app and via a public web portal.

1. In-App Deletion Controls

2. Public Web Account & Data Deletion Portals

In compliance with Google Play requirements, if you have uninstalled the application or wish to delete your cloud account and data externally, you can execute a full erasure request using our verified public web portals:

Temp Mail requests only the minimum Android permissions strictly required to execute its core features. We adhere strictly to the principle of least privilege:

To provide high-availability edge routing, push notifications, and crash diagnostics, Temp Mail integrates select third-party SDKs and cloud services:

Temp Mail operates under a strict Zero Advertisements standard:

• No Advertising SDKs: The application does not include Google AdMob, Unity Ads, AppLovin, ironSource, or any other third-party advertising SDKs.
• No Advertising Identifier Collection: We do not collect or process the Android Advertising ID (AD_ID) for ad serving, behavioral profiling, or cross-app tracking.
• Zero Data Brokerage or Sale: We never sell, lease, rent, trade, or monetize your temporary email handles, received messages, or telemetry data to data brokers, marketing networks, or external advertisers.

Temp Mail is a general audience utility application designated for users aged 13 and older. We strictly comply with the Children's Online Privacy Protection Act (COPPA), the EU General Data Protection Regulation (GDPR) Article 8, and Google Play's Families Policy:

• The application is not directed to children under 13 years of age.
• We do not knowingly solicit, collect, or store personal identifiable information from children under 13.
• If we learn that personal data from a child under 13 has been collected inadvertently, we will immediately delete that information from our servers. Parents or guardians may contact us at support@nilio.sbs to request immediate deletion.

When completing or verifying the Data Safety Form in the Google Play Console for Temp Mail (co.newgates.tempmail), the following declarations accurately represent our audited architecture:

Security Practices Declaration Checklist

• Data Encryption in Transit: Yes (All network traffic to Cloudflare Workers and Firebase is encrypted over HTTPS / TLS 1.3).
• Account Deletion Mechanism Provided: Yes (Both in-app via Settings and via our public web deletion portal at /delete-account).
• Data Deletion Request Pathway: Yes (Users can request complete data purge via /data-deletion).
• Target Age: 13 and older (General Audience).

Depending on your geographical jurisdiction, you possess specific statutory rights regarding personal data:

European Economic Area & UK (GDPR / UK GDPR)

• Right of Access & Portability (Art. 15 & 20): You may request confirmation and copies of data processed under your verified account.
• Right to Erasure / "Right to be Forgotten" (Art. 17): You may permanently delete your temporary inboxes and associated cloud records via our in-app reset or web deletion forms.
• Right to Restriction & Objection (Art. 18 & 21): You may object to data processing or withdraw consent for optional Google Account linking at any time.
• Legal Basis for Processing: We process data under Article 6(1)(b) (performance of contract/service delivery for routing requested emails) and Article 6(1)(f) (legitimate interest for crash diagnostics and security monitoring).

California Consumers (CCPA / CPRA)

• Right to Know & Delete: California residents have the right to request deletion of personal information.
• Do Not Sell or Share My Personal Information: We do not sell, share, or monetize personal information as defined by California law.
• Non-Discrimination: We do not discriminate against users for exercising any CCPA/CPRA privacy rights.

We may periodically update this Privacy Policy to reflect technical enhancements, architectural updates, or regulatory modifications. When amendments are enacted:

• The "Effective Date" at the top of this document will be updated accordingly.
• Material changes that alter our data processing practices will be announced prominently within the Application or via update release notes.
• Your continued installation, access, or use of Temp Mail following the posting of an updated policy signifies your acceptance of the revised terms.

If you have questions, inquiries, feedback, or data privacy requests concerning this Privacy Policy or our engineering practices, please contact our data protection team: