Privacy
What happens to what you send me.
Last updated
This is my own site and there is no team behind it. This page says what the site collects, where each piece goes, how long it stays there, and how to have yours deleted. It describes what the site does today. If that changes, this page changes with it.
The short version
Reading this site collects very little about you. Every page carries Cloudflare Web Analytics, which counts visits without cookies and without identifying anyone. It is described under Cloudflare Web Analytics below. The site sets no cookies of its own. The exception is the pages I advertise: the business and property pages and the assessment pages that follow them carry Meta’s advertising pixel, which does set cookies. It is described under the Meta pixel below.
What I hold is what you choose to send me: through the contact form, the assessment form, email or WhatsApp. I use it to reply to you and, for an assessment, to prepare and send it. I do not sell it, and I do not add you to a mailing list.
Reading the site
The site is served by Cloudflare. Like any host, Cloudflare handles the technical details every request carries, such as your IP address and the browser you use, to deliver the page and to protect the site from attacks. I have added no logging of my own on top of that.
The fonts and images come from this site too, so reading a page sends nothing to Google Fonts or any other outside service. The exceptions are Cloudflare Web Analytics, described next, and the pages I advertise, described under the Meta pixel below.
The blog is written in Sanity, a content service. Posts are copied into the site when it is built, so reading one does not contact Sanity, and Sanity holds nothing about visitors.
Cloudflare Web Analytics
Every page on this site carries Cloudflare Web Analytics, so that I can see how many people read which pages and how quickly the site loads for them. Cloudflare is also the company that hosts the site.
When a page loads, a small script from Cloudflare records the page you visited, the page you came from, your browser type, your country and how fast the page loaded for you. The country is worked out from your IP address, which Cloudflare says it does not store.
It sets no cookies, stores nothing on your device and creates no visitor ID or profile. I see only totals.
The contact form
The form on the contact page asks for your name, your email address, what you are building and your timeline. When you send it, it goes from your browser to Web3Forms, a form delivery service, which emails it to me.
Web3Forms keeps its copy for 30 days on the plan I use, then deletes it. The email stays in my inbox as the record of our conversation. I do not delete these on a schedule, but I will delete yours whenever you ask.
To stop the form being used for spam, your browser remembers the times of the messages it has sent in the last hour, in its own local storage. Only the times, never what you wrote, and they never leave your browser.
The assessment form
The assessment form on the business and property pages asks for your name and email address. It also asks, if you want to say, for your company, your role, a WhatsApp number, your website and any other links to your business online. Then it asks what the biggest problem is, what success would look like, and when you want the work done.
When you send it, your answers go to a small script I run on Google Apps Script. It adds them as one row in a Google Sheet in my Google account, with the time you sent it and which of the two pages you used, and emails me a notification. If you arrived from one of my adverts, the form also records which advert it was, taken from the link you clicked. From your timeline and whether you gave a company, a website or a link, it also decides which of two thank you pages you see. As I prepare your assessment, I add my own notes to the same row.
I keep the row and the email with no end date, because they are my record of your assessment. Google stores them as part of my account. I will delete both whenever you ask.
While you fill the form in, your browser keeps your answers in its session storage, so a reload does not lose them. They stay in your browser and reach nobody until you press send. They are removed when the form is sent or when you close the tab. After a successful send the browser also holds a single marker, so the thank you page knows the request really went through. The page removes it as soon as it reads it.
The Meta pixel
I advertise the business and property pages on Facebook and Instagram. So that Meta can tell which adverts bring visitors and which lead to a request, those pages carry Meta’s advertising pixel: the business page, the property page, the assessment form for each, and both thank you pages. It runs on no other page. The home page, the work pages, about, contact, the blog, the terms and this page carry no advertising tracking, and a link from one of the advertised pages to any of them loads it afresh, so the pixel does not follow you there.
When you open one of those pages, your browser loads a script from Meta. It records which of those pages you visit and the buttons and links you press on them. It also records when an assessment request is sent, with which of the two thank you pages it led to, and when a WhatsApp link is pressed. Each of these says whether it came from the business or the property side. Meta receives the technical details that come with any request, such as your IP address and browser, sets cookies of its own, such as _fbp, and may connect the visit to a Facebook or Instagram account.
I do not hand the pixel your answers, but Meta’s script reads some of them itself. Once you have typed your name, email address or phone number into the assessment form and pressed Next, the script may turn each into a hash, a scrambled code that cannot be turned back into the original, and send that to Meta with what it records afterwards. This can happen before you send the form, and even if you never send it. Meta compares the codes with those of its own account holders, to work out whether someone who made a request had seen one of my adverts.
I use it for one purpose: to see which adverts bring visitors and which lead to requests, so that the money I spend goes on the adverts that work and Meta can show them to people more likely to want this work. What Meta reports back to me is totals. It does not tell me who you are.
Meta’s Conversions API is switched on for this pixel as well. That means the same events are delivered to Meta through a server connection as well as from your browser, so an advert blocker or your browser’s cookie settings may not stop them.
Meta handles all of this under its own privacy policy, and it is Meta’s to delete, not mine. To opt out, block or clear cookies in your browser’s settings, or use a content blocker, which stops the script loading. If you have a Facebook or Instagram account, the advert preferences in its settings control how Meta uses what it receives from other websites.
Email and WhatsApp
If you email me or message me on WhatsApp, I receive what you send along with your address or number. I keep it as the record of our conversation and delete it when you ask. WhatsApp and my email provider carry those messages under their own terms.
Who sees it
Me. There is no team, so what you send is read by the person who replies to it. Apart from the services named on this page, which carry or store it for me, I do not share it, sell it or pass it on.
Seeing or deleting yours
Email me at hello@chukwumaukaha.com and tell me the address or number you used. I will send you a copy of what I hold, or delete it: the Sheet row, the emails and the WhatsApp messages. I will reply within one working day and confirm in writing when it is done.
The copy at Web3Forms deletes itself after 30 days. What Meta holds about a visit is held by Meta, and its own settings are the way to remove it.
When this changes
Cloudflare Web Analytics and the Meta pixel on the pages I advertise are the only analytics installed today. If I add another, or any other service that handles visitor data, this page will say so, and the date at the top will change.