Last updated: November 15, 2026
The short version
- This website sets no cookies and runs no advertising or tracking scripts.
- We only get personal information you choose to send us, such as through the contact form or by email.
- We use it to reply to you and to run the work you ask us to do. We never sell or rent it, and we don't use it for advertising.
- People taking part in an engagement have additional protections, described in the participant notice.
Visiting this website
The site is a set of static pages. Loading it involves a few providers, each of which sees your IP address and basic browser information as a normal part of delivering a web page:
- Cloudflare delivers the site and protects it from abuse. It processes request data such as IP address, browser type and the page requested, and may keep short-lived security logs.
- GitHub Pages hosts the files and may log requests for security and operations.
- Google Fonts serves the typefaces, so your browser requests font files from Google.
If we turn on site statistics, we'll use a cookieless service (such as Cloudflare Web Analytics) that counts visits without identifying or following individual visitors.
The light/dark theme button saves your choice in your browser's local storage. It never leaves your device, and you can clear it at any time.
When you contact us
When you use the contact form or the "report an approach" form, or email us, we receive what you send: usually your name, work email, organization, role and message. Forms are delivered through Formspree, which passes them on to us by email. Email to our addresses is forwarded by Cloudflare Email Routing.
We use this information to respond, to scope and propose work, and to keep a simple record of our business conversations. We don't add you to a marketing list unless you ask us to.
Clients and engagements
When an organization hires us, a contract and, where required, a data processing agreement (DPA) set out what we may collect, why, and when we delete it. In those engagements we generally act on the client's behalf, and the client's own privacy notice also applies.
Engagements follow the rules on our trust & safety page: nobody is approached without their written consent, we collect the minimum needed, recording is off by default, and sponsors receive aggregate results only. The participant notice explains exactly what we record about participants and who can see it.
Who processes data for us
| Provider | What for |
|---|---|
| Cloudflare | Content delivery, security, DNS, email forwarding, cookieless statistics if enabled |
| GitHub (Pages) | Website hosting |
| Google Fonts | Web fonts |
| Formspree | Delivering website form submissions |
| Our email and document providers | Business correspondence and engagement records, under contract and encrypted |
Some of these providers are based in, or store data in, the United States. Where the law requires it, we rely on appropriate safeguards for international transfers, such as standard contractual clauses.
How long we keep it
- Enquiries that don't become work: deleted within 24 months of our last contact.
- Client business records (contracts, invoices): kept as long as tax and legal obligations require.
- Engagement data: on the schedule in the contract. Our defaults are in the participant notice.
Your rights
Depending on where you live, including under the GDPR and California's CCPA/CPRA, you may have the right to access, correct, delete or move your personal information, to object to or restrict how we use it, and to withdraw consent. We don't sell or "share" personal information as California law defines those terms, and we don't knowingly collect information from children.
To make a request, email [email protected]. We'll confirm who you are before acting, and we'll reply within 30 days. If we're processing your data on behalf of a client, we'll pass the request to them and help them respond. You can also complain to your local data protection authority.
Security
We encrypt engagement data in transit and at rest, require multi-factor authentication on our systems, limit access to the people working on an engagement, and keep each client's data and persona accounts separate. To report a security issue with this site or our services, see responsible disclosure.
Changes and contact
We'll update this page when our practices change and revise the date at the top. For anything privacy-related, contact [email protected].

