Know what happens to your data before you receive email.

01 / Scope

One policy for two ways to receive email

This policy covers the free temporary email, email verification-code login, forwarding aliases, and email archive features on fwdsky.com. It explains why these features process data, their stated retention periods, and what you can do through the website and support channels.

Temporary email doesn’t require an account, while forwarding requires verifying a login email address that can receive messages. Their credentials and deletion actions are separate. Before using either, read Temporary email vs. aliases If you need account recovery, refunds, or ongoing contact, don’t use a temporary address that may expire soon.

This policy doesn’t replace the privacy policies of third-party sender websites, email providers, or other external sites you visit. We’ll update this page when the policy changes. To check whether a specific practice applies to your account, contact the support email at the bottom of this page.

02 / Data and purposes

What we process and why

Fwdsky processes emails and related routing information to receive, display, and forward messages. The sections below explain the data used for each service. “Temporary” and “alias” don’t mean no records, no linkability, or complete anonymity.

Login email and verification data

Used to send you login codes, confirm access to your account, and receive forwarded messages. If you enable two-step verification, we also process authenticator settings and the information needed to verify codes. Don’t share verification codes, authenticator keys, or login credentials.

Alias settings

Include the alias address, its account, and whether it’s enabled or disabled. We use them to determine whether and where to forward incoming messages and to provide management controls. Disabling an alias stops future forwarding but doesn’t delete existing archives or copies in the destination inbox.

Email content and metadata

Includes the sender, recipient address, subject, time, message body, attachments, and delivery status. We use this information to display, forward, and troubleshoot email. Senders may include third-party content in messages. Don’t use a temporary inbox for banking, identity documents, or other highly sensitive information.

Necessary request and service logs

When you access or use the service, we may process IP addresses, request times, interface results, and technical information provided by your browser. We use this information to rate-limit requests, prevent abuse, maintain security, and troubleshoot issues. We don’t promise zero logging or invent a single retention period for these records. Contact support with questions about a specific request.

Credentials stored in your browser

Used to restore access to a temporary inbox, keep you logged in, and remember the selected email so you don’t have to start over each time you visit. Each serves a different purpose. Clearing browser data doesn’t submit a deletion request to our servers. See Browser credential guide.

We use this information to provide inbox access, verify logins, forward email, and maintain security. This doesn’t mean that every sender will accept a disposable email address. Check the sender website’s own rules before choosing an address.

03 / Retention periods

Time-limited inboxes aren’t for recovery

Temporary inboxes and long-term forwarding archives have different retention periods. Check the countdown on the homepage for the time remaining on a temporary address. When planning, allow time for verification codes, downloads, and saving anything you need.

Expiry and manual deletion aren’t reversible archive actions. Save anything you need before taking action. We also don’t promise that all service logs, records we’re required to retain, or system copies will be physically erased at the exact moment you click delete.

If you need to receive password resets or order updates over time, use your real email address or a long-term alias instead of repeatedly extending a temporary address. For help planning around expiry, see Temporary email expiry guide.

04 / Browser credentials

More than just an address stays on your device

Temporary inbox credentials and account login tokens are stored locally in your browser to restore the relevant features when you return. The selected-email record restores your reading position; it isn’t an email backup and can’t replace valid access credentials.

• Temporary inbox credentials: Let your browser access the current inbox. If you clear them, you may not be able to reopen an older inbox that hasn’t expired yet. Knowing the address alone isn’t enough to restore access.
• Account login token: Lets the server confirm your account identity. Logging out clears local account login information but doesn’t destroy a separate temporary inbox.
• Selected email record: Helps restore the email you last opened. If that email is deleted or the inbox expires, the reading-position record can’t recover its contents.

On a shared device, first log out of your account in the dashboard, then manage your temporary inbox as needed and clear this site’s browser data. Closing a tab doesn’t log you out. Private browsing, switching devices, or clearing browser data can also make existing local credentials unavailable.

05 / Reading and forwarding

Isolated display doesn’t mean trusted content

HTML emails are displayed in a restricted, isolated viewer and sanitized to reduce risks from active content. This protects how messages are displayed; it doesn’t verify the sender, guarantee that message content is genuine or attachments are safe, or promise end-to-end encryption.

Emails come from third-party senders and may contain external links, image URLs, or tracking information. If you visit an external site, allow remote resources to load, or download an attachment, those services may receive information about your request. Check the source, and don’t share verification codes, passwords, or payment information based only on a brand name in an email.

After forwarding, the copy is managed by your email provider

Long-term forwarding requires us to receive and process messages before delivering them to your login email address. Once a message reaches that inbox, its storage, spam filtering, deletion, and access are managed by that email provider. Deleting the Fwdsky archive won’t delete the copy there.

Fwdsky doesn’t describe forwarding addresses as anonymous tools that hide all communication relationships. If you’re unsure what “alias,” “forwarding,” or “metadata” means, read our Email glossary before deciding whether to use this feature.

06 / Controls and requests

Choose the action that matches what you want to end

Deleting an email, destroying an inbox, deleting an alias, and logging out affect different things. No single action replaces the others. Check the address and email before acting, and save anything you need. Don’t rely on recovery after a successful action.

Delete one temporary email

Go to the temporary inbox, select the email, then choose “Delete” in the reading pane. Deleting a demo email only changes what’s displayed; it doesn’t delete real data in a third-party account.

End an old temporary inbox

On the homepage, “Get a new address” requests destruction of the old inbox after a new one is created successfully. Check that the address change worked. Closing the page or clearing local credentials doesn’t destroy the inbox. Don’t keep using the old address for messages you’re expecting.

Disable or delete an alias

In the forwarding dashboard, manage the relevant alias. Once disabled, future messages sent to it will be discarded instead of forwarded. Deleting an alias won’t recall forwarded messages or close your account on the sender’s website.

Delete a forwarding archive or log out

In the dashboard, open the archive details and delete the relevant record. To end account access on your device, choose “Log out.” Logging out only clears the local account session; it doesn’t automatically disable aliases or delete emails in the destination inbox.

For permitted uses of the service and limits on responsibility, see our Terms of Service. If this page doesn’t answer your question, contact support first to confirm before submitting or continuing to store the relevant information.