Your data,handled honestly

When you contact us — by email, the contact form or the workflow form — we collect your name, work email, company and whatever you tell us about your workflow, plus your role, phone or company website if you choose to share them. Submissions are stored in our own database (self-hosted PostgreSQL on our infrastructure) and delivered to our team as email through our transactional email provider. Your workflow description may also be processed by an AI model (currently OpenAI) to produce an initial interpretation shown back to you — the model receives the description and optional context you select, not your contact details. We use it to respond and, if things progress, to scope and deliver work. If you book a meeting, scheduling is handled by Calendly — your name, email and chosen time are processed by Calendly to create the booking and its confirmation.

Our hosting provider processes standard technical logs (IP address, browser, pages requested) to serve and secure the site. We don’t build profiles from it.

Some outreach emails link to this site with an opaque code in the URL (a random string with nothing readable in it). If you arrive via one, we resolve it server-side to the campaign it belongs to — which may tell us which organisation or outreach effort your visit relates to — and use it to show you more relevant content and to connect any enquiry you make to the right person on our team. The code identifies the campaign, not you personally: it contains no name or email, and a forwarded link works identically for whoever opens it. The campaign context record for a visit expires after about four hours.

Arriving via a campaign link sets a single functional session cookie (rctx) that holds a random session identifier — HttpOnly, expires after about four hours, never shared with third parties. It carries no personal data and does not persist between visits. Staff signing into our internal console get a separate sign-in cookie after Google authentication — it applies only to the internal area, not the public site. Beyond that: no advertising or tracking cookies, no third-party analytics, no fingerprinting — so no cookie banner, because there’s nothing to consent to.

Vercel (hosting, US), our own PostgreSQL database (enquiry storage), OpenAI (AI interpretation of your workflow description only — not your contact details), Resend (delivering enquiry emails), and Calendly (scheduling, which writes to our Google Workspace calendars). Each gets only the data its role needs.

We don’t sell personal data, share it with marketers, or use your enquiry for anything other than the conversation you started.