Temporary means time-limited
Temporary email addresses last 3 hours by default, up to 24 hours. Expiration is not a promise of long-term storage.
Privacy Notice · Effective August 21, 2026
This notice applies to the temporary inboxes, email forwarding, account authentication, and support services provided by quickmx.com. It explains why we process data and where we draw the line.
Temporary email addresses last 3 hours by default, up to 24 hours. Expiration is not a promise of long-term storage.
Aliases can be paused or deleted. Archives support short-term troubleshooting and do not replace your destination mailbox.
Our business is not built on selling email content or creating cross-site advertising profiles.
Send privacy requests to support@quickmx.com. We first verify the requester’s relationship to the account.
| Data category | Purpose | Typical limits |
|---|---|---|
| Temporary addresses and email | Create inboxes, display incoming messages, and prevent abuse | Addresses last 3 hours by default, up to 24 hours; messages are cleared when inbox access ends |
| Login email and verification records | Authenticate forwarding accounts and prevent credential stuffing and abuse | Verification codes are short-lived; security records are retained only as needed to prevent abuse |
| Aliases and destination mailboxes | Deliver forwarded email and manage accounts | Kept while the account exists; deletion starts a controlled cleanup process |
| Forwarding archives and attachments | Review delivery, retry forwarding, and handle misclassification | Usually kept for up to 30 days, except where held for legal or security reasons |
| Technical logs | Support availability, security investigations, and capacity planning | Records are minimized, then deleted or aggregated on a rotation schedule |
This notice covers the QuickMX website and email services initiated through it. It does not cover sender websites, destination mailbox providers, or third-party links users follow. Each third party handles data under its own privacy rules, which users should read before submitting information.
For data required to operate the service, QuickMX determines the purposes and methods of processing. When users receive third-party email through a forwarding alias, they must also ensure they have the lawful right to receive those communications.
Temporary email may process random addresses, inbox credentials, email envelope information, message content, and receivable attachments. Forwarding also processes login emails, destination addresses, user-created aliases, delivery status, quotas, and security settings.
When you use the service, the system may record the time, request path, approximate network and device information, response status, and security events. These records support troubleshooting and abuse prevention; they are not used to build sensitive profiles unrelated to the service.
We use data to create mailboxes, receive or forward email, display archives, verify accounts, carry out user instructions, and respond to support requests. The system also uses limited signals to identify automated abuse, attacks, malicious attachments, and excessive use.
Capacity and reliability analysis relies on aggregated data whenever possible. If we need to inspect a single delivery, we limit access to the information necessary to resolve the issue.
Processing is generally based on fulfilling user requests, keeping the service secure, and complying with applicable law. Where consent is required, we provide a choice before enabling the relevant feature rather than disguising unnecessary consent as a condition of service.
Users must not ask QuickMX to process communications they have no right to receive. After receiving a valid objection or restriction request, we assess our legal obligations, system integrity, and the rights of others.
Temporary addresses are designed for short-term use, with client credentials used to access the corresponding inbox. We do not promise to restore an address, message, or access after expiration, so users should not rely on temporary inboxes for critical accounts or sole copies of important files.
To keep the product within its intended boundaries, an individual inbox can live for no more than 24 hours. Any security backups are also subject to rotation, isolation, and access controls; they are not user-facing recovery copies.
Forwarding requires the mapping between an alias and a destination mailbox so incoming messages can reach the mailbox chosen by the user. Archives retained for 30 days support delivery review, downloading available attachments, retrying forwarding, and correcting spam classification.
Deleting an alias stops future delivery but does not guarantee that existing copies can be recalled from the sender or destination mailbox systems. Pausing an alias preserves its configuration until the user resumes or deletes it.
Login verification codes are sent to the email address provided by the user, expire quickly, and are rate-limited. When two-step verification is enabled, the system stores the encrypted configuration needed for verification—not the continuously changing codes in the user’s authenticator.
Security logs help identify repeated failures, token abuse, and unusual activity. We recommend protecting both your email account and authenticator, since together they form the credential chain for accessing the forwarding console.
We may use infrastructure, email delivery, security, and customer support providers to deliver the service. Providers may process necessary data only for agreed purposes and are bound by confidentiality, security, and deletion obligations.
We do not sell email content or login email addresses. If we receive a valid legal demand, we review its scope and, where legally permitted, seek to limit disclosure and notify affected users.
Internet email may naturally cross multiple jurisdictions, and infrastructure may be located outside the user’s region. We manage these risks through contracts, access controls, and applicable transfer mechanisms.
Security measures include encryption in transit, least-privilege access, log reviews, and authentication for sensitive actions. However, no internet service can promise absolute security. If you suspect an incident, send the time, address, and details to our support email; do not include secrets or complete identity documents in ordinary email.
Depending on applicable law, users may have the right to access, correct, delete, restrict, object to, or obtain a copy of their data. Requests should identify the relevant account and specific scope. We may require email verification to avoid giving data to the wrong person.
Some data cannot be deleted immediately because of security investigations, fraud prevention, dispute handling, or legal obligations. Where an exception applies, we explain why and retain only what is needed for that purpose.
The service is not designed as an identity or educational platform specifically for children. Users below the local age of independent consent should have a guardian assess the service and provide authorization where required by law.
Do not use temporary email to transmit medical, financial, government identity, or other highly sensitive materials. Even if the service can technically receive them, that does not mean the use fits the product’s security boundaries.
We will update this notice when there are material changes to the product, law, or data flows, and will show the effective date at the top of the page. Significant changes will be highlighted in a reasonable way; we will not quietly expand an old policy to cover entirely different uses.
For privacy questions, rights requests, or security reports, contact support@quickmx.com. To help us respond, include the feature used, relevant time, and action you want us to take.