Skip to main content

Privacy Policy

Last revised: October 2026

Who I am

Cactus Co is a web design and development agency based in the United Kingdom. I am the data controller for personal data you share with me through my website or during our business relationship.

Privacy contact:
Website: madebycactus.com

What data I collect and why

1. Contact form enquiries

When you use my contact form, I collect your name and email address, and the content of your message. I use this solely to respond to your enquiry.

Lawful basis: Legitimate interest: you have voluntarily contacted me about my services, and I have a clear interest in responding.

2. Instant estimate enquiries

When you use my public instant estimate tool, I record the project details you enter (page counts and selected features) and the computed estimate result shown to you, so the figure is preserved even if my pricing changes later. This tells me what people are pricing up so I can improve the tool and my packages.

The record starts out anonymous. It contains no name, email address, IP address, or device information, and it is not stored on your device or held in a cookie. It does carry a randomly generated reference for that estimate, which is what lets me connect it to a booking you go on to make. Section 6 explains that in full. If you then ask me to email you the estimate, your name and email address (and any note you add) are attached to that same record, and I use them to send you the estimate and follow up on your enquiry.

Lawful basis: Legitimate interest. Where you have asked me to email you an estimate, you have voluntarily requested a price and I have a clear interest in following up. Where you have not, my interest is in understanding what people price up so I can improve the tool and my packages, which I weigh against a record that holds no contact details and describes a project rather than a person.

3. Discovery call and meeting bookings

When you book a call or meeting using the booking form on my website, I collect your first name, last name, and email address, and I record the type of call, the call method you chose, and the scheduled time. If you choose a WhatsApp video call or a phone call, I also ask for your phone number so I can reach you. If you choose a Google Meet video call, a Google Meet link is created for you and sent to you by email. I store all of this in my own database, and I use it only to confirm, manage, remind you about, and follow up on your booking. A reference ID is attached to the booking as well, so I can tell how many enquiries turn into calls; section 6 explains what that is and what it is not.

For a Google Meet booking you can also add guests. For each guest I ask for a name and email address, and I store them with your booking and email them a confirmation with the call details. Please only add people who are happy for you to share their details with me. Guests are not asked to do anything and their details are used only for that booking.

To offer you times when I am free, the booking system checks my availability in my Google Calendar and my iCloud calendar. It reads only when I am busy, not the names, attendees, or details of my other events, and none of that information is about you. When you confirm a booking, an event for it is created in my Google Calendar. That event holds your name, email address, and phone number (if you gave one), which is how Google comes to process them on my behalf.

At the start of a consultation call I may ask whether I can transcribe it, so I can listen to you properly instead of typing notes. If you'd rather I didn't, just say, and I'll take notes by hand instead. I use Granola for this. It captures the call's audio from my computer, turns it into a written transcript, and deletes the audio as soon as that's done, so no recording of the call is kept. Granola uses its own providers to transcribe the audio and process the transcript, and publishes a list of them.

After the call, I send the transcript to Anthropic's Claude, which drafts my notes from it: what you'd like your website to do, the pages and features you mentioned, your design ideas, any dates you gave me, and anything you said you don't need. I check every note before I keep it. I don't keep the transcript itself: it is never saved on my systems, and I delete it from Granola once my notes are written up, and in any case within 30 days of the call. I have switched off Granola's option to use my data to improve its own models, and neither Granola's AI providers nor Anthropic are allowed to train their models on it.

The notes I keep, whether I typed them during the call or took them from a transcript, are stored with your name and contact details as the record of our consultation. Your quote and project brief are built from it. I keep that record for 12 months after it was last updated.

Lawful basis: Legitimate interest: pre-contractual communication with prospective clients. For guests, my interest is in sending the confirmation the person who booked has asked me to send. For transcribing a consultation call and keeping its record, my interest is in an accurate record of what you've asked for, so your quote and brief reflect it. You can say no to the transcription at the start of the call, or ask me afterwards to delete the notes.

4. The chat assistant

My public site has a chat widget answering questions about my services. It is powered by Anthropic's Claude, so the messages you type are sent to Anthropic to generate a reply. I do not save the conversation: it lives in your browser tab until you close it, and I never see it. Anthropic holds it under their own retention policy. Under the commercial API terms I use, conversations are not used to train their models.

Please do not type anything sensitive into the chat. If the assistant offers you a contact form and you fill it in, that becomes a contact form enquiry as described in section 1.

Your browser stores a random chat session ID for the length of the tab. I use it to cap how many messages one session can send, so the assistant cannot be run up as a cost against me. Your IP address is used for the same purpose, in memory only, and is not written to any record.

Lawful basis: Legitimate interest: answering questions from people considering my services, and protecting the service from abuse.

5. The free website check

The free website check on my public site tests a website you give me the address of. I send that address to Google PageSpeed Insights, which loads the page from its own servers and returns speed, accessibility and search scores and screenshots, so nothing about you is sent to Google. I also fetch the page's text and send it, with the screenshots, to Anthropic's Claude, which writes the first impressions in the report. Under the commercial API terms I use, this is not used to train their models.

I store the address, the scores, the screenshots, the page text and the written review for 90 days, then delete them. The result sits at its own link, and anyone who has the link can open it, so please share it with care. Please only check a website you are entitled to share this information about. Nothing about you is stored with the result: no IP address, browser details or contact details. Your IP address is used to limit how often one visitor can run a check, in memory only, as described in section 18.

Lawful basis: Legitimate interest: providing a free tool you have asked me to run, and protecting the service from abuse. Any personal data on the page checked, such as a name or phone number the site publishes, is processed only to produce your report.

6. Following an enquiry through to a project

I want to know how many people who price up a project go on to book a call, and how many of those become clients. To do that, each estimate is given a random reference ID. If you go straight from your estimate to booking a call, that same ID is saved with the booking, and copied onto your client account if you later become a client. A booking made without an estimate gets a fresh ID of its own.

The ID is a random value with no meaning outside my own records. It is not a cookie, it is not stored on your device, and it is not shared with any advertising or ad-tech provider. It does not follow you around this site or any other, and it records nothing about what you read or where you came from. It connects one enquiry to one booking to one account, and nothing else.

I use it only to produce counts: how many estimates led to bookings, how many bookings led to quotes, how many quotes were accepted. It is deleted whenever the estimate, booking, or client account it belongs to is deleted.

Lawful basis: Legitimate interest: understanding which parts of my sales process work so I can improve them. You can object to this at any time using the contact address above, and I will clear the reference from your records.

7. Client accounts

When you become a client I store your name, email address, phone number, and company name to manage your project and our business relationship. I also store an internal role (admin or client) and external reference IDs that link your account to my authentication provider (Supabase Auth) and payment processor (Stripe). Authentication credentials are held by Supabase, not by me directly. No card or payment data is stored by me.

Profile pictures are chosen from a small set of illustrated avatars I provide. There is no photo upload, so all I store is which avatar you picked.

You sign in with your email address and a password. You can also turn on two-factor authentication using an authenticator app, and add passkeys so you can sign in with your device's fingerprint, face, or a security key. Both are optional. If you use them, Supabase stores the secret that links your authenticator app to your account and, for each passkey, its public key and the name you gave it. Your fingerprint or face never leaves your device, and I never see it.

If I need to sign in to one of your accounts to build your site (a domain registrar or hosting login, for example), you can store those logins on your project page. They are encrypted in your browser before they are sent, so my server only ever holds the encrypted copy, and I decrypt them on my own device when I need them. I keep them until the project ends or you delete them, and they are deleted with your account.

So the dashboard can show you what has changed since you were last here, I store the time of your most recent page view in the portal and the end of your previous visit. To show a celebration once when your project reaches a new milestone, I also store the time of the latest milestone you have been shown. These are kept against your account, are not shared with anyone, and are not used for anything else.

If you save accessibility preferences in the portal (such as contrast, font size, or reading mode), I store those to your account so your choices persist across devices. These preferences may include disability-related information (such as a dyslexia reading mode); they are stored solely to improve your portal experience and are not shared with any third party.

Lawful basis: Contract performance: processing is necessary to deliver the agreed services.

8. Quotes

When I prepare a quote for you, I store the itemised services, amounts, applicable discounts, and any free-text notes associated with your quote. Quotes are linked to your client account.

Lawful basis: Contract performance: necessary for pre-contractual negotiations and to formalise the scope of work.

9. Project briefs

When I prepare a project brief for you, I record your name, email address, and company name alongside the agreed project scope: an overview, goals, pages and structure, features, design direction, client responsibilities, timeline, and out-of-scope items. Briefs are used to define and document the scope of work before or alongside a quote.

At this point I also collect your company's legal details: its registered legal name, any trading name, its company registration number, and its registered business address. These are held against your company record and are needed so that any contract that follows names the right legal entity. Where you trade as a sole trader, these details may also identify you personally.

Lawful basis: Contract performance: necessary for pre-contractual negotiations and to formalise the scope of work.

10. Contracts

When you sign a contract with me, I store the signed contract document (as a PDF) and record your email address and the date and time of signing. Contracts are signed through my own signing service at sign.madebycactus.dev, which shows you the contract and records your signature, your answers to the details it asks for (your name, position and email address), and the date, time, IP address and browser you signed from. It also records that you ticked the box agreeing to sign electronically, and the wording you agreed to. Those details are printed on a signing certificate at the end of the signed PDF, which I then store in Supabase Storage. Once signed, the PDF is digitally sealed so any later change to it can be detected, and a timestamp is added by an independent timestamping authority (DigiCert, or Sectigo if DigiCert is unavailable). The authority receives only a fingerprint (a hash) of the sealed signature, never the document, your name or your email address. The signing service runs on the same Vercel and Supabase (London) infrastructure as this site and keeps its own copy of these records for 90 days.

Lawful basis: Contract performance and legal obligation: the signed contract is a legally binding record of the agreed services.

11. Invoicing and payments

I collect your name, email address, and company name for invoicing purposes. Invoice records include itemised descriptions and amounts, payment dates, and reference IDs linking to Stripe. Payments are processed entirely by Stripe, whether you pay by card or set up a Direct Debit: those details go straight from your browser to Stripe, and I never see or store them. All I can see afterwards is the payment type and the last four digits, which Stripe shows me so you can tell your payment methods apart. Invoicing covers both one-off build projects and recurring maintenance plan subscriptions.

Lawful basis: Contract performance and legal obligation: HMRC requires retention of accounting records for six years.

12. Maintenance plan subscriptions

If you subscribe to a Cactus Co maintenance plan, I store your plan name, subscription status, current billing period, and cancellation information, alongside reference IDs from Stripe. No card data is stored by me.

Lawful basis: Contract performance: necessary to manage and deliver your ongoing maintenance plan.

13. Project messages and feedback

Within the client portal, I store messages exchanged between you and me on individual projects, as well as general company-level communications. I also send periodic feedback requests at project milestones; any feedback you submit is stored against your project record. These records are used to manage your project and maintain a clear communication history.

Lawful basis: Contract performance: necessary to deliver and document the agreed services.

14. Files and assets

Files move in both directions through the client portal, and all of them are held in Supabase Storage in private buckets that are not reachable from a public web address. Every download is served through my app, which checks that you are signed in and that the file belongs to your company before releasing a single byte.

The files involved are: assets you send me (logos, brand guidelines, photography, copy documents, spreadsheets, and short video walkthroughs, up to 50MB each); documents I share with you (briefs, brand asset packs, handover packs); images and PDFs you attach to a change request; signed contract PDFs; and invoice PDFs. Alongside each file I store its name, type, size, who uploaded it, when, and any note you added.

Please only send me files you are entitled to share. If a file you upload contains personal data about other people, such as your staff or your own customers, I hold it on your behalf as a processor rather than as a controller, and I use it only to do the work you have asked for. I do not open, index, or analyse your files for any other purpose, and none of them are used to train any AI system.

Lawful basis: Contract performance: necessary to build and maintain what you have engaged me to build.

15. Analytics and uptime monitoring for your website

For websites I build or maintain, I set up analytics and uptime monitoring and show both to you in the portal. Analytics run on my own Umami server and behave exactly as described in section 16: cookieless, no personal data, no cross-site tracking. Uptime monitoring uses BetterStack, which requests your site's home page on a schedule and records whether it answered and how quickly. It sees no visitor data.

Where this covers your own website's visitors, you are the controller of that data and I act as your processor.

Lawful basis: Contract performance: monitoring is part of the maintenance service.

16. Website analytics

I use Umami to understand how visitors use my site. Umami is a privacy-first analytics tool that does not use cookies, does not collect personal data, and does not track individuals across sites or devices. No IP addresses are stored. Because it stores nothing on your device, I do not need your consent to use it. I rely on legitimate interest for the aggregate counting it does, which I weigh against how little it records and the fact that none of it identifies anyone.

It is not a third-party service watching my visitors: I run my own Umami installation, hosted on Vercel, with its data held in my Supabase database in London. The statistics are not sold, shared, or combined with anything else.

17. Error monitoring

I use Sentry to find out when something breaks. When an error occurs, Sentry receives a report containing the page address, your browser and device type, a technical stack trace, and, if you are signed in, internal reference IDs for your account.

An error also sends Sentry a replay of what the page was doing at the time. Every piece of text on the page is masked before it leaves your browser, and images and video are blocked entirely, so the replay shows the shape of the page and the actions taken rather than anything you read or typed. This applies across the whole site, portal pages included. Nothing is recorded on a normal visit where nothing went wrong: a replay is only kept when an error actually occurs.

My Sentry account is in their EU region, and reports are only sent from the live site, never from development.

Lawful basis: Legitimate interest: I cannot fix faults I cannot see, and a working site is in the interest of everyone using it.

18. Security and abuse prevention

My public forms and the chat assistant are open to anyone, so I limit how often a single visitor can use them. That check reads your IP address and keeps a short-lived count against it in memory. Nothing is written to a database or a log I keep, and the count disappears within the hour.

Separately, my hosting provider Vercel keeps its own request logs, which include IP addresses, as part of running the service.

Lawful basis: Legitimate interest: keeping the site available and protecting it from abuse.

19. My access to your portal account

So I can help when something looks wrong on your side, my admin tools let me view the portal as your company sees it. This is strictly read-only: I cannot send messages, upload files, accept quotes, or change anything at all while in that mode, and it expires by itself after 30 minutes.

Every time it starts and stops I record it: my own email address, your company, and the time. This exists so there is a permanent record of when your account was viewed. You can ask me for the entries relating to your company at any time.

Lawful basis: Contract performance for the support itself, and legitimate interest in keeping an audit trail of that access.

20. Trees planted for your build

Every build package includes five trees, planted through Tree-Nation, a reforestation platform run by Neovee Solutions S.L. in Barcelona, Spain. When you finish onboarding, I order the trees in your company's name. To do that I send Tree-Nation your company name and a short message, and nothing else: no email address, phone number, or project details, and Tree-Nation is not asked to contact you. Tree-Nation acts as my data processor under a signed data processing agreement, and its privacy policy says that when a gift is sent with a name but no email address, it does not collect or store personal data about the recipient. If you trade as a sole trader, your company name may be your own name.

You can choose to keep your name off the certificates. Tell me before you finish onboarding and I will tick a box against your quote. Your trees are then planted into my own Tree-Nation account, using my business email address and the name "Cactus". They arrive already collected, so the certificate carries my account's name, there is no claim button, and your company name is not sent to Tree-Nation at all. If your name is on the certificate, you can ask me to change or remove it after the trees have been ordered. I send the order reference and the new name to my contact at Tree-Nation, who usually makes the change the same business day. Tree-Nation has confirmed that it keeps no record of the old name, so the only trace is my request, which does not include it. It is a request rather than something I control, so I cannot guarantee it.

Tree-Nation issues one certificate covering all five trees in that name, and I link to them from your portal. Until a certificate is collected, Tree-Nation shows a name as its first word followed by the initial of the second, so "John Smith" appears as "John S.". If you are a registered company, I send your name with the spaces removed, so "Acme Ltd" is sent as "AcmeLtd" and shows in full. If you are a sole trader with a trading name, I send that instead, also with the spaces removed, so your own name is not used. If there is no trading name, or the name includes your own name, I send it as it is and it is shortened this way. Certificate links are hosted by Tree-Nation and are permanent and unguessable, but they cannot be made private: anyone who has a link can view it, so treat a certificate as something other people could see. If someone with the link collects the tree, the certificate then shows their name instead of yours. In my own database I record which project and species the trees went to, the certificate links, the order reference and date, and whether you asked me to keep your name off. Tree-Nation is in Spain, and the UK recognises the European Economic Area as providing adequate protection for personal data. Any onward transfer to its sub-processors outside the UK and the EEA must be covered by UK adequacy rules or other safeguards that the agreement requires.

Lawful basis: Legitimate interest: delivering the trees I promise with every build and showing you where they went. You can object to this at any time using the contact address above.

21. Calendars you connect to my booking system

If I build you a website with online booking, you can connect your Google Calendar to it. Your booking page then only offers times when you are free, and each new booking appears in your calendar. You choose to connect it, through Google's own sign-in screen, which lists exactly what you are allowing.

Once connected, I access three things in your Google account, and nothing else:

  • The list of your calendars and their names, so you can choose which ones count as busy.
  • When you are busy on the calendars you choose. This is only busy and free times, not the titles, attendees, locations, or any other details of your events.
  • The events for bookings made through your booking page, which I create, move, and delete when a booking is made, rescheduled, or cancelled. I don't read or change any other event in your calendar.

I store the access Google grants, encrypted, along with the names of your calendars, which of them count as busy, and the ID of each booking event I create, so I can update or remove it later. Your busy times are checked when someone looks for a slot and are not stored.

How I protect your Google data: Security procedures are in place to protect the confidentiality of your data. The access Google grants is encrypted before it is stored, and everything sent between your browser, my systems and Google is encrypted in transit using HTTPS. Only I have access to it, and only to run your booking page. If you disconnect the calendar, I delete the access Google granted.

I use this information only to run your booking page. I don't sell it, share it with anyone, use it for advertising, or use it to train AI models, and I don't read it myself unless you ask me to help with a problem, it is needed for security, or the law requires it. Cactus's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (opens in new tab), including the Limited Use requirements.

You can disconnect your calendar at any time from your portal, or by asking me, or remove my access yourself in your Google Account's security settings, under third-party connections. When a calendar is disconnected, I delete the access Google granted. Booking events already in your calendar stay there unless you remove them.

You can connect an iCloud calendar instead of, or as well as, a Google one, so its busy times are checked too. iCloud has no sign-in screen like Google's, so it uses your Apple ID and an app-specific password that you create for this alone, never your Apple ID password. I store both encrypted. Apple's calendar service sends whole events for the days being checked, so their titles pass through briefly, but only their start and end times are used, and nothing about them is kept. If you choose an iCloud calendar to receive bookings, I add an event to it for each booking, and move or delete it when the booking is moved or cancelled. I don't change any other event in it. Removing the app-specific password from your Apple ID stops my access straight away; disconnecting the calendar in your portal also deletes the details I store.

You can also connect an Outlook calendar, from Microsoft 365 or Outlook.com. You approve my access on Microsoft's own sign-in screen, and I store the access Microsoft grants, encrypted. I read only when events in the calendars you choose start and end and whether they show as busy, never their titles, attendees or other details. If you choose an Outlook calendar to receive bookings, I add an event to it for each booking, with a Teams meeting link for video bookings when your account has Teams, and move or delete it when the booking is moved or cancelled. I don't change any other event in it. You can remove my access in your Microsoft account's settings, or for a work account by asking your IT admin; disconnecting the calendar in your portal also deletes the access I store.

If you take bookings for a team, everything above applies to each person's calendar that is connected, and I hold each person's name, which visitors see when choosing who to book with. When someone is removed, their calendars are disconnected straight away, and their name is deleted once their last booking has been.

Lawful basis: Contract: running the booking page you asked me to build, in the way you set it up.

22. Booking on a website I built for someone else

Some of the websites I build for my clients take bookings through my booking system. If you book on one of them, the business you booked with decides what happens to your booking, and I store and handle it for them as their processor. Their own privacy notice applies, and questions or requests about your booking are best sent to them. I will help them answer.

For each booking I hold your name, email address, your phone number if you give it, any notes you add, your device's time zone, and what you booked, who with, when and where. The business's website receives these to send you your confirmation and reminder emails, and the business sees them in their account with me. If the business has connected a Google, Outlook or iCloud calendar, the booking also appears in it.

If the business asks you to pay when you book, you pay on Stripe's own payment page, into the business's own Stripe account. I give Stripe your email address and what you are booking, and when. Your card details go to Stripe, not to me or to the business's website. With the booking I keep the amount, whether it was paid or refunded, and Stripe's reference for the payment. Stripe's own privacy policy covers what Stripe holds.

If you book a service to repeat, Stripe saves the card you paid the first session with, and I charge each later session to it shortly before that session, on the business's behalf. I keep only Stripe's reference to the saved card, never the card details. If you buy a session pack, you pay once on Stripe's payment page and are given a code; I keep your email address, the code and how many sessions are left. A discount code you type in is checked against the business's list of codes.

If a day you want is fully booked, you can join a waitlist with your name and email address. Nothing is sent when you join. When a time opens, everyone waiting for that day is emailed through the business's website, and the first to book gets the time. I delete your entry once the day has passed.

I delete each booking, with its payment details, 12 months after the time booked, or sooner if the business asks. Anything already in the business's own calendar is theirs to keep or delete.

23. Signing a document on a website I built for someone else

Some of the websites I build for my clients ask people to sign documents through my signing service at sign.madebycactus.dev. If you sign one, the business that sent it decides what happens to the document, and I store and handle it for them as their processor. Their own privacy notice applies, and questions or requests about your document are best sent to them. I will help them answer.

For each document I hold the document itself, your name and email address, the details you enter when signing, your signature, and the date, time, IP address and browser you signed from. I also record that you ticked the box agreeing to sign electronically, and the wording you agreed to. Those signing details are printed on a signing certificate at the end of the signed document. If the business wants to check it is you, its website emails you a one-time code, and my signing service keeps only a scrambled form of it. Signed documents are digitally sealed and timestamped as described in section 10. Documents are held in my Supabase database in London. The business's website is told when you sign, so it can email you a copy of the signed document, and the business can see and download it. The signing page sets no cookies.

I keep each signed document for as long as the business chooses, which is six years from signing unless they choose otherwise, or delete it sooner if they ask. A document that is never fully signed is deleted 30 days after its signing link expires, or after it is withdrawn or declined.

24. Live chat with AI on a website I built for someone else

Some of the websites I build for my clients have a chat box, run by my chat service at chat.madebycactus.dev. If you use one, the business whose website it is decides what happens to your conversation, and I store and handle it for them as their processor. Their own privacy notice applies, and questions or requests about your conversation are best sent to them. I will help them answer.

Opening the chat box and closing it again stores nothing on your device and sends nothing about you to me. When you send your first message, the box keeps a random token in your browser's storage so the conversation can carry on if you reload the page. It sets no cookie. I then receive your message, any name and email address you choose to give, and the page you started from (its path only, never anything after a question mark). The business's team reads and answers in their portal, and is sent a notification, and an email if nobody has looked at the message after a few minutes.

Once you have sent your first message, your browser also opens a connection to my Supabase project in London, so that replies and typing signals reach you as they happen. Supabase sees your IP address and browser details, as any service does when you connect to it. What passes over that connection is a signal that a message has arrived and a signal that someone is typing, on a channel with a random name that only you and the business's team are given. It never contains the text of a message, and I do not store it. If the connection fails, the chat box simply asks for new messages every few seconds instead.

A business can switch on an AI assistant that answers from information it has written. When it is on, the chat box tells you that you are talking to an AI, and the messages in that conversation are sent to Anthropic's Claude to write each answer. Anthropic holds them under its own retention policy, and under the commercial API terms I use they are not used to train its models. The assistant passes the conversation to the business's team if you ask for a person or it cannot help. Please do not type anything sensitive into a chat.

A business can also switch on AI help for its own team, which is off unless it chooses it, even for a business that answers by hand. When it is on, the messages in a conversation that is waiting for a person, and anything a team member has typed and asks the AI to reword, are sent to Anthropic's Claude so that it can suggest replies and reword drafts. The visitor never sees these: a person reads them, changes them and sends them. The same Anthropic terms apply as above, and the suggestions are kept with the conversation and deleted with it.

A business that takes bookings through my booking service can also let you book a time in the chat. Its AI assistant or a member of its team offers a booking form in the conversation, and you choose a day and time and give your name, your email address and anything else the business asks for when you book, such as a phone number. Those details go to the business's booking, as if you had booked on its own booking page, and are saved on the conversation so the business can see who it is talking to. They are not typed into the conversation, so they are not sent to Anthropic. Only the service and the time are written into the conversation (for example, "Booked: Intro call, Tuesday 3 November at 10:30"), and that line is part of what the AI assistant reads. Nothing is ever paid for in a chat.

I delete each conversation 90 days after its last message, unless the business chooses a different period, or sooner if the business asks.

Cookies and storage on your device

My website uses essential cookies only. These are required for the site to function correctly and do not require your consent. I do not use any advertising, tracking, or analytics cookies. This is why there is no cookie banner: there is nothing here to ask you to agree to.

The cookies are: your sign-in session, set by Supabase when you log in to the portal, a short-lived one that remembers an email address change you have started until you confirm it, and, only if you choose a light or dark theme, or change an accessibility setting, one for each that remembers the choice so the website editor shows the same theme and settings as the portal. When you pay a deposit or save a payment method, Stripe's payment form also sets two cookies (__stripe_mid and __stripe_sid) to prevent fraud. They are set by Stripe, only on those pages, and Stripe needs them to take the payment.

One more lasts a few minutes while you connect a Google or Outlook calendar to a booking page I run for you (section 21), so the connection reaches the right booking page when Google or Microsoft sends you back. Four more only ever exist in my own browser: one for the read-only account view described in section 19, one that excludes my own visits from my analytics, and two that last a few minutes while I connect my Google Calendar or FreeAgent accounts.

The demo websites under /showcase are samples and not part of the service, but two of them remember things on your device. The dentist demo sets a cookie, for a year, with the practice location you chose. The clothing demo keeps the contents of its shopping bag in your browser's storage. Neither is sent to me, and neither is used for anything outside the demo.

A few things are also kept in your browser's own storage rather than in a cookie, and none of them are ever sent to me unless you are signed in and have asked for them to be: your light or dark theme choice and your accessibility preferences (contrast, text size, reduced motion, reading mode, dyslexia-friendly type), both also kept in a cookie once you have chosen one as described above, and the chat assistant’s session reference, which is discarded when you close the tab. Clearing your browser data removes all of them.

Who I share your data with

ProviderPurposeData shared
VercelWebsite and application hosting, including my self-hosted Umami analytics serverEverything you send to or receive from this site passes through Vercel in transit. Their request logs hold your IP address, browser user agent, and the page or endpoint requested. Their Speed Insights tool also reports anonymous page performance measurements
SupabaseUser authentication, session management, database and file storageName, email, password hash, session tokens, login timestamps and IP addresses (authentication); all client account, project, booking, brief, quote, contract, invoice, and subscription data, plus every file uploaded or shared through the portal (database and storage); the records my signing service keeps while a contract is being signed (section 10); the conversations in Live chat with AI on a client's site (section 24), and the short signals that tell the chat box and the business's portal that a message has arrived or that someone is typing, which carry no message text; and the cookieless, aggregate usage statistics described in section 16
StripePayment processing and subscription billingName, email, company name, invoice and subscription amounts, reference IDs, and the card or bank details you enter into their payment form directly
GoogleCalendar and Google Meet. Checks my availability, and holds the calendar event for each bookingWhich times I am busy (read from my own calendar). For each booking, an event containing your name, email address, the type and time of the call, and your phone number if you chose a phone or WhatsApp call. For a Google Meet call, the Meet link is created as part of that event. Guests you add are not added to the Google event. If you connect your own Google Calendar to a booking page I run for you, the booking events I create in it (see section 21)
ResendTransactional email deliveryName, email address, and the full contents of each email sent, which for a contact form enquiry includes your message and for a booking includes the confirmation and reminder emails sent to you and to any guests you add
AnthropicPowers the AI chat assistant on the public site, answers visitors in Live chat with AI on a client's site if that business switches its AI assistant on, and suggests replies to its team and rewords their drafts if it switches on AI help (section 24), writes the first impressions in the free website check, and drafts my notes from consultation call transcripts for me to checkThe messages you type into the chat and the rest of that conversation, with nothing else about you attached. For a website check, the address checked and that page's screenshots and text. For a transcribed consultation call, the transcript of that call
Google PageSpeed InsightsRuns the speed, accessibility and search checks in the free website checkThe address of the website being checked. Google loads that page from its own servers, so nothing about you is sent
GranolaTranscribes consultation calls, when you agree to itThe audio of the call while it is being transcribed, which is then deleted and never stored, and the transcript, which contains whatever was said on the call. Granola's own providers, which it lists at trust.granola.ai/subprocessors, transcribe the audio and process the transcript for it
FreeAgentAccounting and invoice managementName, email, company name, invoice amounts and reference IDs
SentryError and performance monitoringError reports containing the page URL, browser and device type, a stack trace, and internal reference IDs, plus a replay of the page where the error happened, recorded with all text masked and all images and video blocked
GitHubHosts the code repository for the website I build for youThe project name and the website's code and content, including text and images you have supplied. No client contact details beyond what appears in the site itself
CloudflareTakes screenshots of the preview of your website while it is being builtThe web address of your preview and an image of the pages on it. No account or contact details
BetterStackUptime monitoring for websites I build and maintainThe web address being monitored. No visitor or client personal data
Tree-NationPlants the trees included with each build (Barcelona, Spain). Acts as my processor under its data processing agreementYour company name (unless you ask me to keep it off) and a short message, sent when I order the trees. No client email address, phone number, or project details. If you ask me to keep your name off, the trees are planted into my own Tree-Nation account instead and nothing about you is sent

All providers are contractually required to protect your data and comply with applicable data protection law. I do not sell your data, and none of it is shared with advertising networks, data brokers, or social media platforms.

The demo sites under /showcase embed a map from OpenStreetMap. As with any embedded content, your browser connects to OpenStreetMap directly and it can see your IP address. Nothing else about you is passed to it.

Vercel, Stripe, Resend, Anthropic, Google, and Granola are based in the United States, and Granola stores transcripts there. Vercel, Stripe, Resend, and Google are certified under the UK Extension to the EU-U.S. Data Privacy Framework, which the UK government recognises as providing adequate protection. Anthropic and Granola rely on the UK International Data Transfer Addendum to the EU Standard Contractual Clauses.

Note on where your data sits: My Supabase project runs in AWS London (eu-west-2), so your account data, your portal records, and every file you upload stay in the United Kingdom. That includes authentication data (password hashes, session tokens, login timestamps, IP addresses, and audit log entries), which Supabase processes under their own privacy policy, available at supabase.com/privacy. My Sentry account is in Sentry's EU region.

How long I keep your data

Data typeRetention period
Contact form enquiries12 months from last contact. The enquiry email in my inbox is deleted automatically after that
Instant estimate enquiries12 months from date of submission. The estimate record and the notification email in my inbox are deleted automatically after that
Instant estimate configurations (no contact details)6 months from the date the estimate was configured
Website check results (the address checked, its scores, screenshots and page text, and the written review)90 days from the check. Nothing about the person who ran it is stored with it
Chat conversationsNot stored on my systems. Held on your device until you close the tab, and by Anthropic under their own retention policy
Conversations in Live chat with AI on a website I built for someone else (see section 24)90 days after the last message in the conversation, unless the business chooses a different period, or asks me to delete it sooner
Booking records, including phone numbers and any guests' names and email addresses, and the matching Google Calendar event12 months from the date of the booking. The calendar event is deleted at the same time as the booking record
The names of the people a client takes bookings with (see section 21)Until they are removed from the booking page and their last booking has been deleted
Bookings made on a website I built for one of my clients (see section 22)12 months from the date of the booking, unless that business asks me to delete it sooner. Events in the business's own calendar are theirs
A name and email address given to join a waitlist on a website I built for one of my clients (see section 22)Deleted once the day waited for has passed
Documents signed on a website I built for one of my clients, and their signing records (see section 23)For the period that business chooses, six years from signing unless they choose otherwise, or sooner if they ask. A document never fully signed: 30 days after its signing link expires, or after it is withdrawn or declined
A Google, Outlook or iCloud calendar you connect to a booking page I run for you (the encrypted access granted by Google or Microsoft, or your Apple ID and app-specific password, encrypted; the names of your calendars and which ones count as busy; and the IDs of the booking events I created)Until you disconnect the calendar or your account is deleted. Revoking my access in your Google or Microsoft account, or removing the app-specific password from your Apple ID, stops it working straight away. Busy times are read when a slot is checked and are not stored
Consultation call audioNot kept. Granola deletes it as soon as the call has been transcribed
Consultation call transcriptsNot stored on my systems. Held by Granola until I delete it, which I do once my notes are written up and within 30 days of the call at most. Anthropic holds what it is sent under its own retention policy
Consultation records (your details and my notes from the call)12 months from when the record was last updated. Your quote and brief keep their own copies under their own rules
Enquiry reference IDs used for funnel reportingDeleted with the estimate, booking, or client account they belong to
Client account dataDuration of contract plus 6 years. An account with no activity or outstanding balance for 6 years is deleted automatically, along with its files
Project briefsDuration of contract plus 6 years (or 12 months after the brief was last updated, if no project resulted)
QuotesDuration of contract plus 6 years (or 12 months if no contract resulted)
ContractsDuration of contract plus 6 years
Invoice and payment records, including the copies held in FreeAgent and Stripe6 years from invoice date (HMRC requirement). Stripe may keep some payment records longer to meet its own legal obligations. When your account is deleted I also delete your Stripe customer record
Subscription recordsDuration of subscription plus 6 years
Project messages and feedbackDuration of contract plus 6 years
Files you upload, and files I share with youDuration of contract plus 6 years, or until you ask me to delete them
Records of admin access to your accountDuration of contract plus 6 years
Milestones, tasks, credentials you store on your project page, analytics reports, and strategy call notesDuration of contract plus 6 years, and deleted with the client account
Signing records held by my signing service (the contract as sent, your signature, what you typed when signing, and the signing history with IP addresses and browser details)Deleted 90 days after the contract is signed by both of us, and with your account if it is deleted sooner. The signed contract, including its signing certificate, is kept with my own records for the contract period above. A contract that is never signed is deleted 30 days after its signing link expires, or after it is withdrawn or declined
Sign-in sessions, including the IP address they were created fromFor as long as your account exists, and deleted with it. Held by Supabase
Website request logs (IP address, browser user agent, page requested)Held by Vercel for up to 1 day
Two-factor authentication and passkey detailsHeld by Supabase until you turn two-factor off or remove the passkey, and deleted with your account
Trees planted for your build (project, species, certificate links, order reference)Deleted with the client account. Tree-Nation keeps its own record of the order and the certificates under its own retention policy (it keeps transaction records for ten years), because a tree that has been planted cannot be un-planted. Deleting your account does not remove your name from the certificates. To have it changed or removed, ask me (see section 20)
Error reports and session replaysHeld by Sentry under their retention policy (90 days by default)
Delivery records of emails I send you (your email address, the subject line, and whether the email arrived)90 days from the date sent, including after your account is deleted. The body of the email is kept for at most 14 days, and only until it is delivered
Copies of emails sent through Resend, including contact form messages and booking emailsHeld by Resend for 30 days, in the United States
Umami analyticsNo personal data collected; no retention limit applies

Your rights under UK GDPR

You have the right to:

  • Access your data
  • Correct inaccurate data
  • Request erasure
  • Restrict processing
  • Data portability
  • Object to processing based on legitimate interest
  • Withdraw consent at any time where processing is consent-based

To exercise any right, email . I will respond within 30 days.

Complaints

You may lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk or on 0303 123 1113.

Changes to this policy

I may update this policy periodically. The date at the top of this page shows when it was last revised. Material changes will be communicated to active clients by email at least 14 days before they take effect.

Let's talk about your project.

A free 30-minute call. I'll go through your project with you, answer your questions, and give you a price on the call.

Book a free consultation

Next free call: Thu 19 Nov, 10:30