Privacy Policy
Effective 4 October 2026
In short: we collect what we need to run your account and keep it secure. We pass your emails through to you but don't store their content. We don't sell data, don't use advertising or analytics trackers, and only set a login cookie.
1. Who we are
GhostParse is operated by WILDYE LIMITED, a company registered in England and Wales ("WILDYE LIMITED", "we", "us"), a company based in the United Kingdom. Our servers, and the database that holds your account, are in the United Kingdom. For personal data about our users (described in section 2) we are the controller. Contact us about privacy at hello@wildye.com.
For personal data inside the emails our customers send and receive through the Service, the customer is the controller and we act as their processor (see section 4). If you are the sender or recipient of such an email, please contact the organisation that sent or received it.
2. What we collect about our users
| Data | Why |
|---|---|
| Company or project name, email address, role in a team | To create and run your account and team |
| Password (stored only as a salted scrypt hash) | To let you log in |
| Two-factor authentication secret (encrypted) and recovery codes (hashed) | To protect your login if you turn on 2FA |
| Login sessions: a hashed session identifier, IP address, browser user agent | To keep you logged in and detect suspicious access |
| Domains, DNS verification status, webhook URL, encrypted webhook secret and DKIM keys, hashed API keys | To provide sending and receiving |
| Audit log entries: who did what and when, with IP address and user agent, e.g. logins, setting changes, invitations (including the invited email address) | Security, abuse prevention and to show you your account's activity |
| Delivery log entries for inbound email: when it arrived, the outcome (delivered, refused and why, retried), the recipient addresses at your own domain, the sender's domain (not their address), the Message-ID, size, spam score and your webhook's response | To show you what happened to your email and to alert you when deliveries fail |
| Email we send you: verification, password reset and team invitations, and in your first week, up to three emails helping you finish setting up (each has a link to stop them) | To operate your account and help you start using it |
| Support tickets you send from your dashboard: the subject, your messages and ours (stored encrypted), who on your team wrote them and when. Deleted two years after the ticket is closed | To answer your questions and fix problems |
| Billing: your plan, usage counts (how many emails and AI extractions, never their content), and your Stripe customer reference. Card details, billing name and address and VAT number are collected and held by Stripe, not us. | To charge for paid plans, keep tax records and enforce plan limits |
| If your account was set up by a reseller (for example your hosting company): which reseller, and your reference with them | So the reseller can manage your account, as agreed between you and them |
| If you register interest in running the Service on your own servers (our Partners page): your name, company, work email, and the website, size and message you choose to give | To tell you when licences are available (legitimate interests); nothing else |
| If you install our Desk: its version, its web address, and how many users and mailboxes it has (never who they are, or any email), from its requests and a daily check-in | To support it, know which versions are in use before releasing updates, and tell you when its email can't arrive |
| If you use meetings in our Desk: how many meetings and people there are, how many minutes they lasted, the largest, how many guests joined, how many recordings were made, and how many people were turned away because a meeting was full (only numbers, never names, titles, links or anything said) | To run and support meetings, see how they're used, and plan larger meetings (our legitimate interest) |
| If you take calls from your website in our Desk and connect a BigCommerce store: when a caller gives their email address, your Desk asks us for their newest order in each connected store, and we look it up in the store and pass a short summary back (number, status, total, items, tracking). We don't keep the address or the order | To show whoever answers what the call is probably about (to provide the service) |
| If your Desk meetings have more than 6 people: our media server forwards each person's sound and video to the others while the meeting goes on. Everything is encrypted end to end in the browsers with a key only the people in the meeting have, so we can't see or hear it, and nothing of it is kept. The media server sees network addresses, an opaque number for the meeting and each person (never names or links), and how much was sent, while the meeting lasts. Afterwards we keep, per account and per day, the total person-minutes and data sent (no people, meetings or addresses), to bill large meetings | To carry meetings of more than 6 people and bill them (to provide the service) |
| If you use meetings in our Desk and a direct connection between two people isn't possible: our relay (TURN) passes on their call, which stays encrypted end to end, so we can't see or hear it and nothing of it is kept. The relay sees the two network addresses and how much was sent, for as long as the call lasts | To connect calls that couldn't connect otherwise (to provide the service) |
| If you install our Desk, a summary of attacks its firewall refused: the attacking IP address, the kind of attack, how many times and when (never the content of requests, or anything about your users or email). It can be turned off in Desk's firewall settings | To see what's attacking webmail installs and protect them (security: our legitimate interest) |
| Server logs: IP addresses, requested URLs, timings and errors | To keep the Service running and secure |
If CAPTCHA is enabled on our signup page, the CAPTCHA provider processes information about your browser and IP address to tell humans from bots (see section 5 and our Cookie Policy).
3. Our legal bases (UK GDPR)
- Contract: to provide the Service you signed up for (account, login, domains, API keys, webhooks, emails we send you).
- Legitimate interests: to secure the Service, prevent abuse and enforce our Terms (for example the transactional-only rule), keep audit logs, and fix problems. We balance these against your rights and keep the data to what's needed.
- Legal obligation: where we must keep or disclose data by law.
4. Emails passing through the Service
When we receive an email for a customer's domain, we parse it in memory, check its SPF, DKIM and DMARC authentication, and deliver it as JSON to the customer's webhook. When a customer sends an email, we build it, sign it and hand it to our outbound email relay. If it bounces permanently, or the recipient reports it as spam, we keep the recipient's address on that customer's suppression list so they aren't emailed again. When a customer imports old email into their webmail, each message is sent to us to be read into the same JSON and returned straight away. We do not store the content of these emails (body, subject or attachments) once they have been delivered or rejected. Limited metadata (the Message-ID, the sender's domain, the recipient addresses at the customer's own domain, size, spam score and the delivery outcome) is kept in the customer's delivery log for 90 days.
AI extraction (optional). If an account owner or admin turns on AI extraction and gives an address an AI parser, the subject, sender, recipients and text of each email to that address are sent to Anthropic (the provider of the Claude AI model) to read the fields the customer asked for. Under Anthropic's commercial terms, this data isn't used to train its models. Nothing is sent for accounts or addresses that don't use AI parsers.
Autopilot for WooCommerce (optional). If a customer turns on the Autopilot in our WordPress plugin, their site sends us each customer email it reads (the sender, subject and text) with the details of the order it's about, read in their WordPress. We pass them to Anthropic to sort the email and write a reply, return the reply to the site, and keep nothing. Drafts are kept in the customer's own WordPress.
Webhook inspector (optional). If a customer creates an inspector URL in the dashboard, the requests sent to it (which can include emails, if they point a webhook at it) are kept in memory, never on disk, so they can look at them: at most the last 50, for two hours at most, and gone sooner if they delete it or our server restarts.
If spam or virus scanning is enabled, messages are scanned in memory by software running on our own servers; they are not sent to a third party for scanning. If a customer chooses to receive the original message or attachments, they are sent only to that customer's webhook, or, if the customer sets up attachment storage, uploaded to the customer's own storage bucket (which the customer controls, at the storage provider they choose) and not kept by us.
Integrations (optional). A customer can send emails on to services they choose, such as Slack, Microsoft Teams, Google Sheets, Make, n8n or another webhook, and can set routing rules that decide which emails go where. We send each email only to the services the customer set up, and we don't keep a copy. Once it arrives, that service holds the email under the customer's own agreement with it.
BigCommerce (optional). A customer can connect their BigCommerce store, with an API token they make in it, so its order emails are sent through us. When an order changes, we read it from BigCommerce (the buyer's name, email and addresses, the products, amounts and shipments) to write and send the email, and don't keep it. We keep the order number, the event and whether the email was sent for 30 days. The token is stored encrypted. If the customer sets up a store inbox, emails their buyers send to it are forwarded to the customer and added to the order's staff notes in their BigCommerce store. If they turn on the Autopilot, each email to the store's inbox and the details of the order it's about are sent to Anthropic to sort it and write a reply; the email's text and the reply are kept for 30 days for the customer's staff to review, then deleted. We don't keep a copy of anything else.
We process this data only on the customer's instructions, as described in section 7 of our Terms.
5. Who we share data with
We do not sell personal data or share it for advertising. We share it only with:
- Stripe, which processes payments for paid plans. Stripe acts as an independent controller for payment data; see Stripe's privacy policy.
- Service providers who host and run the Service for us, such as our hosting and database provider, our outbound email relay (for the account emails we send you), (if enabled) our CAPTCHA provider, and Anthropic for AI extraction and the Autopilot (for accounts that turn them on, see section 4). They act on our instructions under contract.
- Your team: other members of your account can see your email address, role, 2FA status, last login, and your actions in the audit log (owners and admins).
- Professional advisers, regulators, law enforcement or courts where required by law or to protect our rights, users or the public.
- A buyer or successor if our business is reorganised or sold, under equivalent protections.
The sub-processors that handle email passing through the Service are listed in our Data Processing Agreement.
6. International transfers
Email passing through the Service is processed on servers in the United Kingdom, except for AI extraction, which an account has to turn on (section 4). Some of our providers may process data outside the UK. Where they do, we use safeguards recognised under UK data protection law, such as adequacy regulations or the UK International Data Transfer Agreement or Addendum.
7. How long we keep data
| Data | Kept for |
|---|---|
| Account, team, domain and API key data | Until your account or the item is deleted |
| Login sessions | Up to 14 days, or until you log out |
| Email verification and password reset links | 48 hours and 1 hour respectively |
| Team invitations | 7 days unless accepted |
| Audit log entries | 90 days |
| Delivery log entries (inbound email metadata) | Your plan's delivery log period (up to 90 days) |
| Invoices and payment records | Six years, as UK tax law requires |
| Email content passing through the Service | Not stored (email being sent waits in the mail queue until it's delivered, up to 5 days) |
| DMARC reports about customers' domains (sending IP addresses and counts) | 90 days |
| Suppressed addresses (permanent bounces and spam complaints) | Until the customer removes them or closes their account |
| Interest in a licence (Partners page) | Until you ask us to remove it, and no more than 12 months after licences go on sale |
| Desk installs (version, address, user and mailbox counts) | Until the API key it uses is deleted, or your account is |
| Meeting usage counts from webmail installs | 400 days |
| Large-meeting totals per account and day (person-minutes, data sent) | 7 years, with billing records |
| Attacks reported by webmail installs | 30 days |
| Server logs | A limited period for security and troubleshooting |
| Database backups | 14 days, then overwritten |
We may keep data longer where the law requires it or to deal with a dispute or abuse investigation.
8. Security
Connections are encrypted in transit. Passwords, API keys, session identifiers and recovery codes are stored only as hashes; webhook secrets, DKIM private keys and 2FA secrets are encrypted at rest. Access is restricted by role, 2FA is available (and can be required for your team), and account activity is audit-logged. No system is perfectly secure, but we work to protect your data and will tell you without undue delay about any breach that affects you.
9. Your rights
Deleting your account. The account's owner can delete it at any time under Account → Delete account in the dashboard. It happens straight away: the account, its users, domains, addresses, API keys, settings, logs and support tickets are deleted, and any subscription ends. What stays: invoices and payment records (which the law requires us to keep), database backups until they're overwritten (14 days), and a record that an account was deleted and when, without who it was.
Under UK data protection law you can also ask to access, correct, delete or receive a copy of your personal data, and to restrict or object to how we use it. To make a request, email hello@wildye.com. We will respond within one month. If you are unhappy with how we handle your data, you can complain to the Information Commissioner's Office (ico.org.uk), though we'd appreciate the chance to help first.
10. Children
The Service is for businesses and developers and is not intended for anyone under 18.
11. Changes
We may update this policy. We will post the new version here with its effective date and, for significant changes, let you know by email or in the dashboard.
12. Contact
WILDYE LIMITED, a company registered in England and Wales. Email: hello@wildye.com.