Privacy policy
A website may only see your alias, but Swiftfwd needs to know where to forward your mail. This policy explains temporary inboxes, ongoing forwarding, and sign-in verification separately—and what you can stop or delete.
Aliases can help keep websites from getting your real email address directly. Our service still needs to link each alias to its forwarding destination, and message content may include personal information you choose to share.
Temporary inboxes are available for a limited time. Forwarded email records are kept for 30 days. Account and alias settings support ongoing forwarding; the email retention period does not mean your account is automatically deleted.
Disabling an alias stops future forwarding; it doesn’t recall messages already sent. Deleting records from our service won’t delete copies held by your real inbox or the sender.
By feature
You don’t need to sign in with your real email account to use a temporary inbox. To use ongoing forwarding, you must provide a real email address that can receive verification codes and forwarded messages. The access credentials for these two features are separate: signing in to a forwarding account does not give you access to a temporary inbox.
The table below lists data by purpose. “Spam protection” doesn’t mean we never process message content, keep technical records, or associate data with an account. Delivering email, detecting spam, and troubleshooting may all require us to process relevant data.
| Feature | Data involved | Why we need it | What to keep in mind |
|---|---|---|---|
| Temporary inbox | Temporary address, access credentials, creation and expiry times, and email received at that address. | Create an inbox, verify access, display email, and calculate its validity period and renewal limits. | Access credentials grant access to your inbox. Don’t share request URLs containing credentials, browser storage, or screenshots showing debugging information. |
| Sign-in with your real email | Real email address, verification-code checks, and sign-in credentials. If you enable two-step verification, we also process authenticator setup and verification data. | Send you a sign-in code, verify account access, and link ongoing forwarding settings to your account. | Passwordless doesn’t mean protection-free. A compromised real email account or exposed sign-in credentials can put your account at risk. |
| Alias settings | Alias address, associated account, enabled status, and forwarding destination. | Determine where incoming messages should go, and carry out enable, disable, or delete actions. | Websites you sign up with generally see the alias you enter. We still need to know the real destination address to forward your email. |
| Email content | Sender and recipient details, subject, message body, and any attachments included with the email. | Receive and display email, detect spam, and forward messages while an alias is enabled. | Messages may contain names, order details, verification codes, or other sensitive information. Don’t use a temporary inbox as the only place to store important information. |
| Delivery and security records | Email processing times, delivery status, reasons for failure, and request information needed to run and protect the service. | Show forwarding history, troubleshoot delivery issues, prevent abuse, and keep the service running. | “Forwarded” is a processing status. It doesn’t guarantee the destination inbox will accept the message; the destination provider may still filter it. |
| Support communications | The contact address you write to support from, your description of the issue, and any relevant records you choose to share. | Understand your request, troubleshoot issues, and respond to data requests. | Share only what’s necessary. Don’t send verification codes, sign-in credentials, authenticator keys, or unrelated full email messages. |
If you only need to receive a one-time verification code, you can use a temporary inbox. If you need to keep receiving bills or shipping notifications, use an ongoing alias. Keep in mind that forwarding requires a link between your real email address and the alias.
Retention and deletion
Temporary email addresses are valid for 3 hours by default. You can renew them in 3-hour increments while they’re valid, up to 24 hours per inbox. Ongoing forwarding follows a separate schedule: forwarded email records are kept for 30 days, while alias settings remain in place for continued delivery and don’t expire when an individual email record does.
These time limits describe how long content is available through the product; they aren’t guarantees about when every copy is removed from all underlying infrastructure. Save any email you need to keep before it expires, and don’t use an expiring temporary address for account recovery.
3hours
Starts when the inbox is created. Check the remaining time shown in the inbox, rather than measuring from when an email arrived.
24hours
Renewing an inbox won’t keep it indefinitely. Once it expires, the address and its emails can’t be recovered. Creating a new address won’t transfer old messages.
30days
View recent records in Alias Management. This period doesn’t control copies saved by your real inbox after an email has been forwarded there.
| Event or action | Effect on our service | What it won’t do automatically |
|---|---|---|
| Temporary inbox expires | Ends access to the temporary inbox. Its address and emails can’t be recovered. | It won’t update the email address on websites where you registered, or guarantee those sites can still reach you at the old address. |
| Manually delete an email | Removes the record from the relevant inbox or forwarding archive without waiting for it to expire. | It won’t undo a completed delivery or delete copies held by the sender or destination inbox. |
| Disable or delete an alias | When disabled, messages sent to the alias are no longer forwarded to your real email. Deleting it removes the alias settings. | It won’t delete historical archive records. Delete existing records separately if needed; messages received while the alias is disabled won’t be forwarded later. |
| Clear browser storage | Removes access state saved in the current browser and may prevent you from accessing your temporary inbox. | It isn’t a data deletion request to our servers and won’t clear sign-in state on your other devices. |
We don’t promise a specific backup deletion schedule unless it has been confirmed. The 3-hour, 24-hour, and 30-day periods above don’t apply uniformly to all security logs, support communications, or infrastructure copies. If your request concerns these records, contact support with the data category so they can confirm what can be handled and any limitations.
From receipt to forwarding
To receive and deliver email, our service needs to process necessary content, including email headers, destination addresses, and message bodies. Spam detection, delivery troubleshooting, and archive display may also involve this information. Alias forwarding doesn’t mean our service can’t process message content, nor does it mean your email has end-to-end encryption that only you can decrypt.
We use the recipient address to identify a temporary inbox or forwarding alias, then check its validity, access permissions, or enabled status. Sender, recipient, and time information in the email headers is used to display and process incoming messages.
We check messages that need forwarding for spam and record the processing outcome. If an alias is disabled, we won’t forward messages to your real email. Otherwise, forwarding requires us to send the email to the destination provider, which follows its own data handling rules.
Temporary emails are available to view while the inbox is valid. Forwarded email records can be viewed for 30 days. Statuses such as delivered, blocked, failed, or pending explain the current processing outcome; they don’t mean records held by the sender or another inbox have been deleted.
Messages are provided by their senders, and their content, attachments, and links may include third-party material. Loading remote images or tracking resources may disclose your network address, access time, or other request information to the relevant third party. Following a link takes you to that website’s own data handling practices.
Don’t trust an email based only on its sender display name, and never share your service access credentials to “verify your identity.” If a notification looks suspicious, visit the relevant service directly to check it rather than using a link in the email.
Browser and access security
Your browser saves the access state needed to keep using the service after you refresh the page. Ongoing forwarding sign-in credentials, temporary inbox access credentials, and your email reading selection serve different purposes. Signing out, closing a tab, and clearing storage aren’t interchangeable actions.
After using a public computer, sign out on the Alias Management page and clear this browser’s site storage if needed. Save anything you still need before clearing it. Temporary inboxes don’t use your real email account for sign-in, so check separately whether their access credentials remain in the browser.
Don’t include verification codes, sign-in credentials, temporary inbox credentials, or authenticator keys in support tickets, chats, or public screenshots. You can enable two-step verification in Alias Management: scan the QR code with a mobile app such as Google Authenticator, Microsoft Authenticator, or 1Password, then enter the 6-digit code generated by the app to confirm. This adds sign-in protection but can’t eliminate every risk.
When you access the site and its interfaces, network infrastructure may process your IP address, request times, browser details, and error information to provide and secure the service. We don’t promise “zero logs.” To ask about specific technical records, analytics processing, or retention, contact support using the address below.
What you can do
You can perform common actions directly in your inbox or Alias Management without contacting support. Before taking action, check that you’ve selected the right address and records. In particular, “stop forwarding” doesn’t mean earlier messages have disappeared from everywhere.
To access data related to you, correct information, request deletion of account-related data, or ask about data not covered by the page controls, email support@swiftfwd.com. Include the type of request, the relevant account email or alias, an approximate timeframe, and what outcome you’re looking for. There’s no need to attach the full email content.
To prevent someone else from claiming or deleting your data, we may need to verify that you’re authorized to make the request using your account email or other necessary information. Support will handle the request based on the data we can verify and the requirements that apply. Some data may not be recoverable or removable, for example if a temporary inbox has expired, access credentials are missing, an email has been sent to another service, or the request covers necessary security records.
This policy applies to temporary inboxes, ongoing forwarding, and related account features provided at swiftfwd.com. It doesn’t replace the policies of the sender’s website, the destination email provider, or any third party linked from an email. For service limitations, prohibited conduct, and usage rules, also read the separate Terms of Service.
We’ll update this policy and the date at the top of the page when our features or data practices change. If you have questions about a change, contact support before continuing to use the relevant feature to understand how it may affect your addresses, emails, or account data.
