Last updated: 29 July 2026
This website is operated by Wayne Visser ("Wayne", "we", "us", "our"). Wayne Visser is the data controller for the personal data described here, acting in a personal capacity rather than through a company. We are not required to appoint a Data Protection Officer, because we are not a public authority and we do not monitor people systematically or process special category data at scale.
Reach us about anything in this policy through our contact page.
This policy covers this website only. It does not cover Wayne's presence on LinkedIn, Substack, YouTube or BlueSky, each of which is governed by that platform's own policy.
When you send a booking enquiry. Your name and your message, both of which are required. Optionally your organisation, the type of event and a proposed date. The form also carries a hidden field that no real visitor sees; if it comes back filled in, we treat the submission as automated spam and discard it.
There is no legal or contractual obligation on you to provide any of this. But name and message are required to submit the form, and if you leave out any way of contacting you, we cannot reply or take any step towards an engagement. The form does not currently ask for your email address, so please include one in the message if you want a response.
When you email us. Whatever is in the message, plus your email address and anything in your signature or attachments.
When you subscribe to the newsletter. Subscriptions are handled on Substack and on LinkedIn. Your email address goes to that platform rather than to this website. See section 4.
Automatically, when you browse. Delivering a web page requires processing your IP address, browser and device type, the pages you request and the time of each request. We do not combine this with anything else and do not use it to identify you.
Cookies and browser storage. The site sets a small number of strictly necessary cookies and stores your cookie choices in your browser's local storage. It sets no analytics or advertising cookies today. Our Cookie Policy lists every one by name and explains how to change your choices.
We do not collect special category data such as health, beliefs or biometrics. Please do not send it through the enquiry form.
| What we do | Legal basis |
|---|---|
| Read and reply to booking and speaking enquiries | Legitimate interests: responding to someone who approached us about work |
| Take steps towards a speaking, training or writing engagement you asked about | Contract |
| Send the newsletter | Consent, given when you subscribe |
| Keep an unsubscribed address on a suppression list so you are not added back by mistake | Legitimate interests, and our obligation to honour your objection to marketing |
| Keep the site available and defend it against abuse | Legitimate interests: security and continuity of our own website |
| Set non-essential cookies, including analytics if and when we enable it | Consent, given through the cookie banner |
| Keep records we are required by law to keep, or answer a lawful request | Legal obligation |
Where we rely on legitimate interests, we have weighed our interest against your rights and concluded it does not override them, because the processing stays within what you sent us and what running the site requires. You can object at any time (section 9).
The newsletter is published and delivered through Substack, which acts as a separate and independent controller of your subscription, not as our processor. When you subscribe, Substack stores your email address and applies its own open and click tracking to the emails it sends, under its own privacy policy and its own consent arrangements: substack.com/privacy. The LinkedIn newsletter works the same way, under LinkedIn's own policy.
Wayne can see subscriber counts, aggregate engagement, and individual subscriber email addresses inside Substack. We do not build profiles, segment the list by behaviour, or sell, rent or share it.
Unsubscribe from the link at the foot of every issue, or by contacting us. It takes effect immediately. We then keep your address on a suppression list for one purpose only: making sure you are not added again by mistake.
We do not sell personal data and we do not share it for anyone else's marketing. These providers handle data in order to run the site:
| Provider | What it handles | Role |
|---|---|---|
| Lovable | Builds and hosts the website | Processor |
| Cloudflare | Delivers the site from an edge location near you, and filters malicious traffic. Processes your IP address in transit | Processor |
| Supabase | Stores booking enquiries submitted through the form | Processor |
| Substack | Newsletter subscriptions and delivery | Separate and independent controller |
| Analytics, only if and when we enable it, and only with your consent | Processor |
Each processor is under a contract that limits it to acting on our instructions. We may also disclose data where the law requires it, or to establish or defend a legal claim.
The site is delivered through Cloudflare's global network, so your request is usually handled at an edge location in or near your own country. Cloudflare Inc., Supabase Inc., Substack Inc. and Google LLC are United States companies and some processing takes place there.
Where personal data leaves the UK or the EEA, we rely on one of the following, in this order:
Ask us via our contact page and we will send you a copy of the safeguard relied on for any given transfer.
| Data | Retention |
|---|---|
| Booking enquiries and related correspondence | 24 months from our last exchange with you, then deleted |
| Enquiries that turn into a paid engagement | 6 years from the end of the engagement, to meet tax and accounting requirements |
| Newsletter subscription | Until you unsubscribe |
| Suppression list after unsubscribe | Email address only, kept for as long as we run a newsletter, so that we can honour your opt-out |
| Server and security logs | No longer than 12 months |
| Cookie consent record | 12 months, then we ask you again |
The site is served over HTTPS with HTTP Strict Transport Security enabled. Enquiry data sits in a database that is not publicly readable, reachable only by Wayne and the site's server-side code. Access to the newsletter list is protected by Substack account credentials with two-factor authentication.
No website can promise perfect security. If a breach occurs that is likely to result in a risk to your rights, we will notify the ICO without undue delay and, where feasible, within 72 hours of becoming aware of it, and we will tell you directly where the law requires it.
You can ask us to:
Write to us through our contact page. We respond within one month. If a request is unusually complex or you have made several, we may extend that by up to two further months, and we will tell you within the first month if we do. There is no charge unless a request is manifestly unfounded or excessive, in which case we will explain why before doing anything.
We may ask you to confirm your identity first, so that we do not hand one person's data to someone else.
If you are unhappy with how we have handled your data, please tell us first so we can try to put it right. You can also complain to a supervisory authority at any point, without going to us first.
In the UK that is the Information Commissioner's Office:
If you are in the EU, you may complain to the data protection authority where you live, where you work, or where the alleged infringement took place.
This site is aimed at professional and academic audiences. It is not directed at children under 16 and we do not knowingly collect their data. If you believe a child has sent us personal data, tell us through our contact page and we will delete it.
We make no decisions about you by automated means and we do not profile you.
Pages here link to third parties including Amazon, Routledge, Lulu, LinkedIn, YouTube, Substack and BlueSky. Once you follow a link you are on their site under their privacy practices, and we have no control over what they collect.
We update this policy when our practices change, when we add a provider, or when the law moves. The "Last updated" date shows when it last changed. Where a change materially affects your rights we will say so on the page rather than change it quietly.
For anything in this policy, including data protection requests, please use our contact page.