A plain summary of how Ironfang runs. The Privacy Policy and each product's documentation are the detailed sources, and where this page and the Privacy Policy differ, the Privacy Policy applies.
Who operates Ironfang
- Ironfang Ltd, registered in England & Wales, company number 12764014, registered office C/O Burton Varley Ltd, The Counting House, 24 Richmond Road, Bowdon, Altrincham, WA14 2TT, England.
- Ironfang was founded by Richard Adnams, who builds and operates its services and supports the developers who use them.
- Ironfang Ltd is registered with the Information Commissioner's Office as a data controller (reference ZB444797). Registration is a legal requirement; it is not an approval of our products or our security.
Where services run
Ironfang's services run on servers Ironfang owns and operates in the UK.
That does not mean every copy of your data stays in the UK. Encrypted backup copies are also kept with a storage provider in Germany, and the providers below handle traffic, messages and payments on our behalf, some of them outside the UK.
Providers that handle data
These providers handle data for Ironfang, each for the purpose shown:
- Cloudflare: network security and content delivery, including traffic to our MCP server.
- Stripe: payments. Card details go to Stripe and never reach our servers.
- SMTP2GO: account emails, product notifications and contact-form delivery, sent through its EU service.
- Google: Google Ads measurement, only if you agree to it, and the mailbox where contact enquiries arrive.
- Meta (WhatsApp): the messages Ironfang Agent sends and receives for a business that uses it.
- GitHub: hosts the service status page.
- Backup storage in Germany: encrypted backup copies, encrypted before they leave our servers.
Where data leaves the UK, transfers rely on adequacy decisions or standard contractual clauses. Meta may process WhatsApp messages outside the UK; the Ironfang Agent privacy notice covers Agent in full.
How long each product keeps data
Retention differs by product. Deleted data leaves the live systems first; backups can still hold a copy until they are replaced, and we do not yet publish a backup retention period.
- Ironfang Render: request history is kept for 7 days. An async job's request body is cleared 24 hours after it finishes, and its hosted result is kept for 24 hours. Webhook payloads are cleared after 7 days.
- Ironfang Finance: the free validator does not store documents or results. Signed-in results and generated invoice XML are kept for 30 days and can be deleted sooner; async inputs are stored encrypted and removed when the job finishes or after its 24-hour deadline.
- Ironfang Rig: captured payloads are kept for 7 days and run records for 90 days.
- Ironfang Analytics: a site keeps session recordings for up to 28 days and session history for up to 90 days.
- Ironfang Agent: enquiries are kept for one year unless the business using Agent chooses otherwise, and WhatsApp delivery records for 30 days.
- Accounts, enquiries and logs: account data for the life of the account, and billing records for as long as tax law requires (typically 6 years); contact enquiries for up to 12 months after they are resolved; server logs for up to 90 days.
For Ironfang Audit and Ironfang Security, or to close an account and have its data erased, contact us. Erasure is carried out by us rather than in the portal.
Access and encryption
These controls are in place today, with the scope shown:
- Account passwords are stored only as Argon2id hashes.
- API keys are stored only as SHA-256 hashes, never as the key itself.
- Credentials you give us for delivery, such as webhook signing secrets and S3-compatible access keys, are encrypted with AES-256-GCM and decrypted only to make a delivery you asked for.
- The keys that sign sign-in tokens are encrypted at rest, so a copy of the database alone cannot sign a token.
- Backups are encrypted before they leave our servers.
- Staff actions in our internal management tools are written to an audit log that the tools can add to but cannot change or delete.
- Our source code is scanned for leaked secrets, and its Go dependencies are checked for known vulnerabilities, on every change.
Ironfang holds no security certification and has not published a penetration test. The services have no guaranteed service level (see the Terms of Service), and support has no guaranteed response time.
Support and vulnerability reports
For help, use the contact form or email hello@ironfang.com. You reach the people who build and run Ironfang.
To report a vulnerability, email security@ironfang.com. The Vulnerability Disclosure Policy sets out what is in scope and what we promise, including an acknowledgement within 5 working days.
Status and changes
The service status page shows the live state of each service. The changelog records what has changed in the products, and when.

