Privacy notice

Last updated: 16 November 2026

Who I am

I'm Glenn Johnston, director of HAZELKITE LIMITED, providing AI and business process consultancy to small and medium-sized businesses. In this notice, "I" and "my" mean HAZELKITE LIMITED.

HAZELKITE LIMITED is the data controller for the personal data described here.

What this covers

This notice explains what I do with personal data when you visit my website, enquire about my services, book a call, complete an intake form, take part in an engagement, or work for a business that has engaged me.

What I collect

If you visit my website: hazelkite.com sets no cookies, runs no analytics and has no forms. Netlify, which hosts it, records technical details of each request, such as your IP address, your browser and the page you asked for. That's needed to deliver the pages and protect the site from abuse.

If you contact me or book a call: name, email address, phone number, business name, job title, and whatever you choose to tell me about your business.

If you complete an intake form: the above plus your answers about how your business operates, which may include headcount, systems used, process descriptions, volumes, times and costs.

If you take part in a call I record: an audio recording and a written transcript, containing your voice and anything you say.

During an engagement: notes, documents you send me, and anonymised or dummy records used to illustrate how a process works.

What I don't ask for. I don't ask for or accept your login credentials. I don't have access to your live systems unless we've agreed it in writing as part of a build, on stated terms. Where I need to see how something works, I use screen-shares, anonymised samples or dummy records wherever I can.

Real client records, only when agreed in writing. Some work can't be tested on dummy records, such as turning a dictated report into a draft. I handle real records about a business's own customers only with that business's written agreement. See "Data I handle for a client" below.

Why, and on what legal basis

What I doWhyLawful basis (UK GDPR Art. 6)
Run the websiteTo deliver its pages and keep it secureLegitimate interests: running a website people can rely on
Respond to enquiries, arrange and hold callsTo discuss whether I can helpLegitimate interests: responding to someone who contacted me
Deliver an engagementTo do the work agreedContract, or legitimate interests where the contract is with your employer
Record and transcribe callsAccuracy, so figures are captured correctly rather than typed while you talkConsent, asked for before each recording and withdrawable at any time
Produce the findings reportThe deliverableContract or legitimate interests
Keep records of work doneLegal, tax, insurance and professional obligationsLegal obligation, and legitimate interests
Prepare case studies or use testimonialsMarketingConsent, separately given, with the wording approved in advance

Where I rely on legitimate interests, I've considered whether it's fair to you. If you disagree, you can object (see your rights below).

Where I rely on consent, you can withdraw it at any time without giving a reason. That won't affect anything done before you withdrew it.

Who I share it with

I don't sell personal data and I don't share it for marketing.

RecipientWhatWhy
Netlify (US)Technical details of website visits, including IP addressesHosting hazelkite.com
Microsoft (Microsoft 365, OneDrive, Teams)Email, files, call recordingsBusiness systems
GitHub (a Microsoft company)My own written analysis and working notes, and their version history. Not recordings, not files you send me, not anything holding your customers' detailsBackup and version history of my own work
Fireflies.ai (US)Call recordings, transcripts and meeting summariesTranscribing calls you've agreed to have recorded
Anthropic (Claude, US)Notes, transcripts, documents and draft reports I work on, which can include names and other personal detailsAI assistant I use to analyse information and draft my work. Used under Anthropic's commercial terms and data processing addendum, which don't allow it to train its models on this data
Calendly (US)Your name, email, company details and booking answersBooking calls
Notion (US)Notes and engagement recordsWorking notes and project tracking
LinkedIn and WhatsAppYour name, contact details and our messagesContacting people and replying to messages
MonzoPayment detailsBusiness banking
My accountantInvoicing and financial recordsAccounts and tax
Professional advisers and insurersOnly if needed for a claim or legal issueLegal obligation or legitimate interests
Subcontracted developersOnly where you engage me for implementation, and only what they needContract, under written data-processing terms
Server hosting provider, named in the written terms with that clientOnly where a client chooses a build that runs on a rented server: that client's filesRunning the system the client chose, usually under the client's own account

On GitHub specifically. I keep my own written analysis in a private version-controlled repository, so I don't lose it and can see how my thinking changed. What goes there is limited by a technical rule, not by memory: written analysis only. Recordings, documents you send me, data exported from your systems, and signed agreements are excluded automatically.

Nothing containing your customers', tenants' or employees' personal details goes there. My notes name the people I interview and describe how your business works, because that's what the analysis is. They don't carry your customer records.

Some of the services above are based in the US or store data there. I only transfer personal data outside the UK through the standard protections those providers offer. Where implementation work involves a developer outside the UK, I'll tell you before any of your data reaches them. For clients in regulated sectors I assume UK-based delivery unless we agree otherwise in writing.

Data I handle for a client

If a business hires me and gives me records about its own customers, that business is the data controller and I'm its processor. Written terms with the business set out what I may do with them, who else handles them and when they're deleted. I use them only for the agreed work.

If you're that business's customer, its privacy notice applies and it's your first point of contact. You can also write to me, and I'll pass your request on.

How long I keep it

Most periods below run from the end date: the date of my last invoice to your business, or, for work I didn't charge for, the date I delivered the findings report. If we work together again, the end date moves to the end of that work.

DataRetention
Website request logsA short period set by Netlify, which hosts the site
Records I handle for a clientAs set out in my written terms with that client
Enquiries that don't proceed12 months from our last contact
Call recordings3 months from the end date, then deleted
Call transcripts12 months from the end date
Record of your consent to a recording6 years from the end date
Intake form responses and engagement notes6 years from the end date
Findings reports6 years from the end date
My written analysis and its version history6 years from the end date, then removed from the repository and its history
Invoices and financial records6 years from the end of the financial year they belong to (HMRC requirement)

I delete recordings sooner on request.

How I protect it

Files are held in Microsoft 365 with multi-factor authentication. Devices are encrypted and password protected. Access is limited to me, except where this notice says otherwise. I follow an internal data-handling checklist for every engagement.

Your rights

Under UK data protection law you can ask me to:

Email glenn@hazelkite.com and I'll respond within one month. There's no charge.

If you're unhappy with how I've handled your data, please tell me first so I can put it right. You also have the right to complain to the Information Commissioner's Office: ico.org.uk, or 0303 123 1113.

Changes

I'll update this notice when my practices change and will change the date at the top. If the change is significant and affects an engagement in progress, I'll tell you directly.