Privacy policy
Last updated 17 November 2026
Who handles your data
Wildmail is the controller for personal data it uses to administer accounts, manage subscriptions, provide support, and protect the service. See Contact and complaints below for how to reach us.
When customers use Wildmail to receive, store, parse, or deliver email on their instructions, Wildmail generally acts as a processor. The customer acts as the controller or on behalf of its own controller. Customers are responsible for the lawful basis and notices for their processing. Where the GDPR requires an agreement for this processing, Article 28 applies.
What we collect and why
To provide your account, we process your name, email address, sign-in and verification records, session data, and any profile information you provide. We also process settings, domains, webhook destinations, API credential records, and usage. We use this information to provide the service under our contract with you or to take steps you request before entering into one. For users acting on behalf of an organisation, we rely on our legitimate interest in administering that organisation’s account. A working email address is required for account access. Optional profile information and third-party sign-in are your choice.
Sign-in and security records can include password hashes, authentication factors, IP addresses, browser information, and login activity. We use operational logs, usage records, delivery diagnostics, and security signals to keep the service reliable, investigate issues, and prevent fraud and abuse. We process support correspondence to answer requests. We rely on our legitimate interests in these activities where processing is outside performance of our contract.
For paid plans, we process your account email, billing customer and subscription identifiers, plan, and payment status to provide and administer the subscription. Stripe receives billing information when you use paid features. Stripe collects payment details on its own checkout pages. We retain or disclose information when required by applicable tax, accounting, or other legal obligations.
Customer email arrives from senders at addresses configured by customers. It can contain sender and recipient addresses, headers, subjects, message bodies, attachments, and personal data within them. To provide email intake on customer instructions, we parse messages, record sender-authentication and delivery results, and deliver events to the destinations customers configure. Retention settings determine whether delivery can be retried or replayed.
Cookies and browser storage
Wildmail uses cookies for sessions, sign-in, and security checks. Blocking them can prevent sign-in or account access. If you choose a theme, your browser stores that preference locally under the key ‘theme’. You can clear it through your browser settings.
Hosting, recipients, and international transfers
We run our application, databases, and mail processing on infrastructure we manage in the European Union. We store message content on those systems and use Backblaze B2’s S3-compatible EU Central region in Amsterdam, the Netherlands, to store attachment files.
Customer-configured webhook destinations receive the events and message data needed for the customer’s integration. Where available, Google or GitHub participates only if you choose that provider to sign in. We receive the profile and account information you authorise that provider to share. Sign-in and recovery emails pass through the mail systems needed to deliver them. We may disclose information as required by law.
Stripe acts as merchant of record for paid subscriptions through Stripe Managed Payments. Its handling of payment data and international transfers is described in the Stripe Privacy Policy linked below. Providers and customer-configured destinations may process data outside the European Economic Area. Where Wildmail makes a transfer governed by the GDPR, it relies on an applicable adequacy decision or appropriate safeguards such as standard contractual clauses. Contact us for information about safeguards that apply to a transfer.
Retention and account deletion
We keep account information while your account is open. Session and verification records are kept according to their expiry and security needs. Support and security records are kept as needed to resolve requests, investigate incidents, or address abuse. Billing records may be kept as required by law. Relevant records may also be retained where needed for legal claims.
You choose how long email and attachments remain available within your plan’s retention limit. With zero-day retention, content is kept for at most one webhook attempt, with a 24-hour safety deadline for messages that never reach an attempt. Delivery history without message content can remain available after content expires. Physical cleanup runs separately from expiry. Attachment files referenced by other retained messages can remain until those references are removed. Backup copies, where present, follow their own expiry schedules.
You can delete your account in Settings. Deletion disables sign-in and inbound mail, requests immediate cancellation of an active subscription recorded on your account, schedules mailbox removal, and removes your account, API keys, sign-in records, and account delivery history. Removing mailbox data and attachment files runs in the background. Deletion issues no automatic refund and does not erase Stripe’s transaction records or copies already delivered to your webhook destinations.
Your privacy rights
Under the GDPR, you can request access to, correction of, or erasure of your personal data, and restriction of processing. Where applicable, you can request portability, object to processing based on legitimate interests, or withdraw consent without affecting the lawfulness of earlier processing.
Use the contact below to exercise your rights, including if you cannot sign in. We may ask for information needed to verify your identity. We respond within one month, unless the GDPR permits extra time. If we need extra time, we will tell you within the first month and explain why. If the request concerns email a Wildmail customer controls, contact that customer. Wildmail assists the customer with requests about the data it processes on their behalf.
Contact and complaints
For privacy questions, rights requests, or information about international transfer safeguards, contact Wildmail at hello@wildmail.app.
You may complain to a competent data protection supervisory authority, including in the EEA country where you live or work or where an alleged infringement occurred. In Estonia this is Andmekaitse Inspektsioon (the Estonian Data Protection Inspectorate). See its official contact and complaint guidance for current submission requirements.
For payment data that Stripe handles as merchant of record, see the Stripe Privacy Policy.
We will update the date on this page when we revise this policy and notify affected users of material changes through the service or by email.