Privacy Policy

01Introduction

Your privacy matters, and in this work it matters more than most. This policy explains how I, Gareth Willett, collect, use, store and protect your personal information across everything I offer: my websites, one-to-one therapy and coaching, the Academy, and the Listen in Deep app. It also explains your rights under UK data protection law.

I've tried to write it as something you could actually read rather than something you'd scroll past. Where I've had to be technical, I've explained why. If anything here is unclear, email me and I'll explain it properly.

02Who I am

I'm Gareth Willett, a sole trader trading as Listen in Deep. I'm the data controller for everything described here.

Address: 32 St Aidan's Road, London SE22 0RP
Email: [email protected]
ICO registration: ZB948922

I'm an accredited member of the British Association for Behavioural and Cognitive Psychotherapies (BABCP), membership number 160104, and a self-discovery coach, trained through a programme aligned with ICF's core competencies. I'm not required to appoint a Data Protection Officer, so questions about your data come to me directly.

I work as an independent practitioner offering psychotherapy, coaching, a membership platform, and a self-guided self-discovery app.

03What this policy covers

• One-to-one therapy — psychotherapy sessions, including CBT, booked and delivered directly with me.
• Coaching — self-discovery coaching, booked and delivered directly with me.
• The Listen in Deep Academy ("the Academy") — my membership, courses and community platform.
• The Listen in Deep app (app.listenindeep.com) — a self-guided self-discovery app, holding a 90-day framework, a journal with your Reflections and your Dream Journal, and breathwork and meditation tools. One of its features is the Inner Guide, which lets you talk things through with an AI companion built on Anthropic's Claude models. The Inner Guide is part of the app, not a separate service.
• My websites — listenindeep.com, go.listenindeep.com and garethwillett.com.

Each collects somewhat different information, set out below. The app in particular works differently from everything else, which is why it gets its own section.

04What I collect

Across therapy, coaching and the Academy

• Contact details — name, email address, phone number, preferred contact method
• Health and background information relevant to therapy or coaching, such as life history, what's brought you, or personal goals
• Payment details, processed by third-party providers — I never see or store card numbers
• Membership data — login details, participation history, messages, and any materials you upload or comment on
• If you give me a testimonial — your name and your words, and, depending on how you choose to submit it, a photo, or a video containing your image and voice. I'll only publish it with your permission, and you can ask me to take it down at any time.
• If we collaborate using Trello — content on a shared board, which may include personal or session-related material either of us adds: notes, files or images you've put there, or things I add as part of the work, such as a practice, a tool, or my own notes

Specific to the Listen in Deep app

• Account details — your name and email address. Signing in by email uses a one-time code, not a password. If you sign up with Google or Apple instead, your name and email are pre-filled from that provider's profile rather than typed in.
• Journal entries — both Reflections and Dream Journal entries, written by you inside the app
• Conversations with the Inner Guide — the full text of what you and it said to each other. Photos you share with it are sent to Anthropic to generate a reply, but they aren't kept in the saved conversation.
• Insights — short pieces of text drawn out of your conversations, which you can edit before they're saved
• Embodiments — notes about something you actually did or changed, in your own words. You can type one straight in, or write it when the app asks you after a conversation.
• Today's intention — a short intention you write for the day, kept against that date
• Session summaries — if you ask the app to summarise a conversation, it writes one and keeps it: the themes it noticed, insights and reframes it drew out, intentions or actions it named, and what seemed to want more attention
• Your end-of-journey reflection — what you write in answer to the closing questions when you complete a 90-day journey
• Practice records — for breathwork and meditation sessions, the dates you practised and how often. No notes, no content, just that you did it
• Your Story So Far — a short narrative the app generates about your journey, built from what you've recorded and quoting your own insights back to you. It isn't written by you, but it's about you and it uses your words, so I treat it exactly like anything else you've written. The current version is kept, along with the two before it, and a short quote distilled from it for your Story Card. Generating your Story So Far and Story Card involves sending your name, journey day, session and insight counts, and the text of your recent insights and embodiments to Anthropic — see Sections 13 and 14. This is different from the Journey Card image, which is built entirely on your device and sends nothing anywhere (Section 6).
• Progress data — which steps of the framework you've worked through, and when
• Voice input, if you use the microphone to talk to the app
• A random device ID — a generated identifier stored on your device, used to route notifications to the right device and to apply fair-use limits across the parts of the app that have them, including the Inner Guide and cloud sync. Applying those limits means my server keeps a count, against that device ID, of how many requests it has made in the current window. When the window passes, the count isn't deleted — it's ignored and overwritten the next time, so a device ID can persist in my rate-limiting store indefinitely once it's been used. It isn't derived from your device's hardware and doesn't identify you on its own.
• Ordinary server logs — when the app contacts my server, for instance to reach the Inner Guide, my hosting provider records the usual technical details: IP address, the time, and which request was made. These are standard web-server logs. They don't contain anything you wrote, and they're kept for a short period for security and troubleshooting under the provider's own retention.
• A record that you agreed — when you create an account, I log your email address, the date and time you confirmed you're 18 and accepted my Terms and this policy, and which version of each you were shown. The law requires me to be able to show that you agreed, and this is the record that does it. It's kept on my servers, not on your device.

From the websites

• Website usage data, including IP address, browser type and general site usage, through privacy-focused analytics (Section 12)

05How I collect it

• When you complete a contact form or book a session
• Through a referral from a service such as Think CBT, where you're introduced to me directly
• Through direct communication by email, phone or chat
• When you sign up to the Academy or my newsletter
• When you create an account in the app, by email or via Google or Apple sign-in
• Through tools used during therapeutic or coaching sessions, such as secure video platforms or a shared Trello board
• Through your own use of the app — writing journal entries, practising breathwork and meditation, and talking with the Inner Guide
• Automatically, through privacy-focused website analytics

06How the app stores your data

This section is specific to the app, because it works differently from the rest of my services.

What this means if you stay local-only: the responsibility for keeping your content safe sits with you. I can't recover it if your device is lost, damaged, reset, or the app is uninstalled without a backup — I never had a copy to restore from. You can export a full backup to a file at any time from Settings and re-import it on a new device, and I'd recommend doing so before switching devices, or periodically if your content matters to you. This isn't meant to alarm you. It's the honest trade-off of a service that never holds your data unless you ask it to.

How long things stay on your device

• Your journal entries are kept until you delete them. Nothing clears them automatically — and the same goes for your insights, your embodiments, your Story So Far, your practice records and your end-of-journey reflections.
• Your conversations with the Inner Guide are cleared after 120 days. This is the one thing the app removes without being asked. It applies on both Free and Plus. If you want to keep a conversation beyond that, export a backup before it ages out.
• One small trace survives that. A note of when you had a conversation is kept indefinitely — the date, and nothing of what was said. It's there so your history and counts stay right after the conversations themselves have gone.

What leaves your device, and when

• When you message the Inner Guide, that conversation — including any images you attach — is sent securely to Anthropic to generate a reply. See Sections 13 and 14.
• When your Story So Far or Story Card is generated, your name, journey day, session and insight counts, and the text of your recent insights and embodiments are sent securely to Anthropic to generate them. See Sections 13 and 14.
• When you use one of the Plus voices to read something aloud, the text being read is sent securely to my voice provider, Cartesia, to generate the audio. That text may include your own words or the Inner Guide's reply about them. The free tier uses your device's own voice instead, which your browser handles rather than me — though as with voice input, some browsers do that by sending the text to their own provider, outside my systems entirely.
• If you enable notifications, your first name, email address and device ID are shared with OneSignal so they can deliver reminders on my behalf. The app tells you this at the point you switch notifications on. It also remembers whether you said yes, no, or closed the prompt, so it doesn't keep asking.

That's the complete list as far as your content goes. Everything else stays put — including the Journey Card, the keepsake image summarising your 90 days. It's assembled entirely on your device from content that's already there. Nothing is sent anywhere to build it, even though you can share the finished image if you want to. The one thing that isn't content but does travel is your device ID, which accompanies requests to the parts of the app that have fair-use limits — Section 4 sets out what it is and how long it lasts.

Plus: keeping an encrypted copy in the cloud

Cloud storage is switched off by default, including for Plus subscribers. Subscribing to Plus doesn't switch it on and doesn't imply you've agreed to it. You turn it on yourself, in Settings, whenever you like — and you can turn it off again the same way, in the same number of taps.

Why this needs its own separate consent

Journal entries, insights, embodiments, your Story So Far and conversations with the Inner Guide can reveal how you're feeling, what you're struggling with, and matters relating to your mental health. UK GDPR calls this special category data and sets a higher bar for handling it — rightly. So for cloud storage I rely on two things at once:

• Article 6(1)(a) — your consent — as my lawful basis for processing it at all; and
• Article 9(2)(a) — your explicit consent — as the additional condition the law requires for special category data.

This is the only place in this policy where I rely on both. Accepting this privacy policy in general does not amount to that consent, and I don't treat it as if it does.

How the encryption works

When you turn cloud storage on, the app generates a Secret Key on your own device — a long random code that only you ever hold. Everything the app holds — your journal entries, your conversations with the Inner Guide, your insights, your embodiments and your progress — is encrypted with it here, on your device, before anything is sent. What reaches my servers is a block of ciphertext.

I can't read it. Supabase can't read it. There's no master key, no administrative override and no support process that can open it, because none of those things exists to build. That isn't a promise about my intentions — it's a fact about how it's made.

The Secret Key is shown to you once, when you switch cloud storage on. It's never sent to my servers, so I have no copy of it and no way to get one. It's designed to be saved in a password manager rather than memorised.

Signing in and decrypting are two different things. Someone who got into your email could sign in to your account — but without your Secret Key, they'd find nothing readable in the cloud copy.

If you lose your Secret Key

There's no recovery path, and that's deliberate. A recovery path is a second way in, and a second way in is a way in for someone who isn't you.

What losing it actually costs you is smaller than it sounds. Your journal is on your device, untouched, exactly as it was — you haven't lost your writing, you've lost the backup. You can turn cloud storage on again with a new Secret Key and start a fresh encrypted copy whenever you like. When you do, the previous copy, which nobody can now read, is deleted.

What isn't encrypted

To run your account at all, a few things sit beside your encrypted content in readable form: your email address; whether cloud storage is switched on; when you switched it on, and which version of this policy you were shown at the time; whether your Plus access has lapsed, and when; the date your cloud copy is due to be deleted, where one is set; and when your backup was last updated. That last one means I can see that you saved something on a Tuesday evening — not a single word of what you wrote, but the timing itself. I'd rather name that than let "end-to-end encrypted" imply I can see nothing whatsoever.

Your device ID isn't one of them. Your cloud copy is filed against your email address and nothing else, so there's no record here of which device it came from.

What cloud storage does, and what it doesn't

What it does: it protects you against losing what's on your device right now. If your phone is lost or damaged beyond use, if you reinstall, or if you move to a new device — your journal comes back.

What it doesn't do: it doesn't keep anything for longer than your device does. Cloud storage mirrors what's on your device at each sync rather than keeping a separate archive, so when your Inner Guide conversations clear at 120 days, the next sync removes them from the cloud copy too. It isn't permanent history and it isn't unlimited history. It's a safety net under the history you already have.

Where it's stored

Cloud copies are held with Supabase, a database and cloud-storage provider, on a project hosted in London, United Kingdom, on Supabase's Pro plan. I use the Pro plan specifically because, unlike the free plan, it's never automatically paused for inactivity. Supabase Inc. is a US company, so although your data sits in the UK, some support access may come from outside it — Section 14 sets out the safeguards I have in place for that.

How long it's kept, and exactly when it goes

• While cloud storage is on and your Plus subscription is active, your cloud copy is kept and kept up to date.
• A 30-day countdown starts on the earlier of two dates: the day you switch cloud storage off in Settings, or the day your paid Plus access ends. Not the day you cancel — the day the period you paid for runs out.
• The 30 days exist for one reason: so that an accidental lapse, an expired card or a change of mind doesn't cost you your backup.
• If your Plus access lapses without you meaning it to, I'll email you when the countdown starts — to the address on your account, telling you the date your cloud copy is due to be deleted and how to stop it — with two further reminders as the date gets close: one with 7 days left, and one with 24 hours left. An expired card shouldn't quietly cost you your writing. If you switched cloud storage off yourself, you'll already have seen that date when you confirmed it. If you don't see one of these emails, check your junk or spam folder — and consider adding [email protected] to your contacts so it isn't missed.
• At the end of the 30 days, your cloud copy is deleted from my live systems.
• You can skip the wait entirely. "Delete everything now" in Settings removes your cloud copy from my live systems immediately — no 30 days, no waiting, no second step to come back for.
• Backups. My database provider takes automated daily backups for disaster recovery — kept for 7 days in case something goes badly wrong with the database itself, for instance a technical fault that corrupts or wipes live data. If that happened, these backups are what let me restore the whole system, not any one person's account — you can't ask me to "roll back to 3 days ago" for just your own data, because they're never opened for that. A deleted copy can survive in those backups until they cycle out, but because everything stored is encrypted with your Secret Key, what's actually sitting in a backup is ciphertext nobody, including me, can read anyway.
• None of this touches the copy on your own device. That stays until you delete it.
• If you delete your account entirely, the cloud copy and the account record go together, within 30 days.

Turning it off, and what that does

You can withdraw your consent at any time, from Settings, as easily as you gave it. There are two buttons there, and they do different things:

• Turn off stops any further syncing straight away and starts the 30-day countdown above. Your cloud copy stays put during those 30 days, in case you change your mind, then it's deleted.
• Delete everything now turns cloud storage off and deletes the cloud copy in the same action, immediately. Use this one if you want it gone rather than merely stopped.

Withdrawing consent doesn't make the earlier storage unlawful — it was lawful while you consented to it — but it stops it going forward, and it gets your data deleted on whichever timetable you chose.

The record I keep of your consent

The law requires me to be able to show that you consented, so when you turn cloud storage on I record the date and time, and which version of this wording you were shown. That's all — it's a record about the consent, not about what you wrote.

07What I can and can't see

There's a real difference between the app and my other work, and it's worth being direct about it.

In therapy or coaching, I'm a person in the room with you. I keep records, I notice things, and I carry professional duties — including, in rare and serious circumstances, a duty to break confidentiality if I believe someone is at risk of significant harm. If that ever became necessary I would tell you, wherever it was safe to do so.

The app doesn't work like that. On the free tier, and on Plus without cloud storage, nothing you write in the app reaches me at all. With cloud storage on, what reaches me is encrypted with a key only you hold, so I couldn't read it even if I wanted to. There's no review, no alerting, no monitoring, and no dashboard where your entries appear. Nobody is checking on you through the app.

Which means: I cannot act on anything you write in the app. If you write about being in danger, or about someone else being in danger, no one will see it and no one will respond. That's a deliberate design choice — your journal is genuinely private — but it has this consequence, and you should know it before you rely on it.

One exception, and it's entirely your choice. If we're working together 1:1, I might suggest during a session that something you've written in the app could be useful for our work — and if you agree, you can forward it to me by email yourself, using the share option in the app. That's the only way anything from the app reaches me, and it only happens because you've chosen to send it. Once you do, I treat it as part of our session work, kept under the same retention as your other clinical or coaching records (Section 11).

If you need someone to know, please tell a person:

Two small things do reach my side, and I'd rather name them than let the claim sound broader than it is. My server counts how many Inner Guide messages a device has sent in the current hour, so the fair-use limit can be applied — it sees that a request happened, not what was in it. And my hosting provider keeps ordinary technical logs of those requests, including IP address and time. Neither contains a word you wrote. "Nothing reaches me" is a claim about your content, and it holds.

One further exception: your messages to the Inner Guide pass through Anthropic to generate a reply. Anthropic operates its own automated safety systems on what passes through its service, under its own policies. That isn't me reading your conversation, and it isn't a safety net — but it isn't nothing either, and you should know it happens.

08Why I use your information

• Providing therapy, coaching, and app-based support
• Managing appointments, communication and payments
• Maintaining accurate and confidential clinical records in line with professional standards
• Providing access to membership and course materials
• Generating Inner Guide responses and voice playback within the app
• Sending reminders you've opted into
• Keeping the app working and protecting it from misuse, including fair-use limits
• Improving my services, content and user experience
• Sending updates and news, where you've given consent

I never sell or rent your personal information to anyone, and I never will.

09My lawful basis

Under UK GDPR, the lawful bases I rely on are:

• Contract — information needed to deliver the therapy, coaching, membership or app services you've asked for, under whichever agreement covers that service — the Terms of Service for the app and Academy, or your own client agreement for 1:1 therapy and coaching.
• Legal obligation — compliance with tax and professional record-keeping requirements.
• Legitimate interest — a lawful basis that lets me process some information without asking first, because it's a reasonable and expected part of running the service and I've checked it doesn't unfairly override your own rights. I rely on it for running and improving my business, community and app, including fair-use limits applied via the device ID described in Section 4.
• Consent — newsletters, marketing, notifications, microphone access, and cloud storage. Where I rely on consent you can withdraw it at any time.
• Explicit consent under Article 9(2)(a) — for Plus cloud storage specifically, given the special category nature of journal and session content (Section 6).

For clinical records, I also rely on Article 9(2)(h) — processing necessary for the provision of health care and treatment by a professional bound by a duty of confidentiality.

You can withdraw consent at any time by contacting me, or — for app notifications, microphone access and cloud storage — through your device, browser or app settings.

10How I protect it

I take appropriate technical and organisational measures to keep your information secure — including encryption in transit and at rest, access controls, and other appropriate safeguards on the systems that hold personal data. No system can be completely secure, and I won't pretend otherwise, but I take this seriously and I'll tell you promptly if something goes wrong.

Where a breach is likely to result in a risk to your rights and freedoms, I'll report it to the ICO within 72 hours of becoming aware of it, and tell you directly where the risk is high.

Clinical notes and contact details for 1:1 clients are held together on uk.Tacklit.com, operated by Tacklit UK Ltd, a UK-based encrypted platform built for healthcare professionals. Tacklit keeps UK/EU client data hosted and processed regionally, separate from its Australian infrastructure.

Academy and membership data is held on my membership platform, provided by Content Creator Machine, built on the GoHighLevel platform.

App content is stored on your own device, as explained in Section 6. Sign-in is handled through encrypted, time-limited tokens.

Shared Trello boards are stored on Trello's own platform, under access you've granted me and can revoke at any time.

11How long I keep it

Conversations sent to Anthropic and text sent to Cartesia are retained by them under their own terms — briefly, for safety and abuse monitoring — and are not used to train their models. See Section 13.

Where a period above ends, I delete or securely destroy the information unless I'm legally required to keep it longer.

12Cookies and device storage

The websites

My websites and the Academy run on Content Creator Machine, built on the GoHighLevel platform. It automatically logs standard technical details — IP address, browser type, and how many times a page is visited — for security and basic traffic statistics. This isn't a tracking cookie and doesn't follow you elsewhere; it's routine server-side logging, the kind almost every website keeps.

Content Creator Machine also sets one cookie — msgsndr_id — when a page loads. It links your visit to my CRM, so that something like a form submission can be matched to the right contact record. It isn't an advertising cookie and doesn't track you across other websites.

It isn't necessary for the site to work, and under UK law it should only be set once you've agreed to it. I've added a cookie consent banner that's meant to hold it back until you do — but in practice, right now, it's set on every visit regardless of what you choose. I'm working to fix that, and this section will be corrected the moment it's genuinely gated rather than just disclosed.

I don't currently use Google Analytics, Meta Pixel, or any other standalone analytics or tracking tool on my websites. If that changes, this section will be updated before any such tool goes live.

The app

The app uses no advertising or tracking cookies at all. It stores two things on your device:

• Your own content, in your browser's local storage. That's the whole design — it's how your journal stays yours (Section 6). It's necessary for the app to work, so it doesn't require separate consent.
• A randomly generated device ID, so that fair-use limits can be applied and, if you turn notifications on, so reminders reach the right device. It isn't derived from your hardware and doesn't identify you on its own. I treat this as necessary to provide the service you've asked for and to keep it working for everyone.

You can clear both at any time through your browser settings — but clearing local storage deletes your app content, so export a backup first.

13Third-party services

I use third-party platforms to run my business, sharing only the minimum each one needs. Most are bound by a written data processing agreement requiring them to handle your information only on my instructions and to keep it secure. Two aren't, currently: Content Creator Machine, which runs my website, Academy, forms, newsletter, CRM and live video, has confirmed that GoHighLevel's own data processing agreement isn't contractually passed through to Content Creator Machine customers; and Senja, my testimonials platform, doesn't offer individually signed DPAs either. For both, I limit what I send them and rely on their own published terms and privacy policy instead.

Each has its own privacy statement on its website.

On Anthropic specifically: conversations with the Inner Guide, and the data used to generate your Story So Far and Story Card, are sent through Anthropic's commercial API. Under those terms, Anthropic does not use what you send to train its models. It retains it briefly for safety and abuse monitoring, then deletes it — see Anthropic's own privacy policy for their current periods.

14International transfers

Some of these services process data outside the UK, mostly in the United States. Where they do, UK GDPR requires me to put a specific legal safeguard in place before the data leaves — it isn't enough for the provider to say they're compliant. I'm putting the UK International Data Transfer Agreement, or the UK Addendum to the EU Standard Contractual Clauses, in place with each provider below, and I'm working through a risk assessment for each transfer. Two exceptions: GoHighLevel itself has a proper transfer safeguard in place, including the UK Transfer Addendum, but Content Creator Machine has confirmed it isn't contractually passed through to me as one of their customers; and Senja doesn't offer this to customers on my plan either. For both, I rely on minimising what's sent and their own published terms instead, rather than a safeguard of my own.

Worth noting: because cloud storage is encrypted on your device with a key only you hold, what crosses any border is ciphertext nobody at these companies can read.

If you'd like a copy of the safeguards in place for any of these, email me and I'll send them.

15Sharing your information

Your information stays confidential. I'll only share it when:

• The law requires it — a court order, a safeguarding obligation, or a tax requirement.
• A service provider needs it to do their job — the providers listed in Section 13, each under a written agreement.
• You've given explicit consent — for example, if a referral to another professional is appropriate.
• For clinical supervision — I discuss my one-to-one work with an accredited clinical supervisor, as my professional body requires. Wherever possible this is anonymised; where it isn't, my supervisor is bound by the same confidentiality I am.
• If the business changes hands — if Listen in Deep is ever sold, merged, or passed on, your information may transfer with it, but only to someone who agrees to honour this policy. I'll tell you if this happens.

On safeguarding: in one-to-one work, there are rare circumstances where I may need to break confidentiality because someone is at serious risk. Section 7 explains why this cannot apply to anything you write in the app.

16Automated decisions and AI

The Inner Guide — the AI companion feature inside the app — generates its replies automatically, without a person involved. It's worth being clear about what that does and doesn't amount to.

It doesn't make any decision about you that has a legal or similarly significant effect. It doesn't decide what you're charged, whether you can use the service, what support you're offered, or anything else affecting your rights. It generates text in response to text, and you're free to ignore all of it.

So there's no automated decision-making of the kind Articles 22A–22D of UK GDPR govern, and no profiling: I don't build a profile of you from what you write, and I couldn't, because in the ordinary case it never reaches me (Section 6).

17Children's privacy

My services, including the app and the Academy, are for adults aged 18 and over. I ask you to confirm this when you create an account, and I don't knowingly collect personal information from anyone under 18. If you believe someone under 18 has given me personal information, please email [email protected] and I'll delete it.

18Your rights

Under UK data protection law you have the right to:

• See what I hold about you, and get a copy.
• Correct anything inaccurate or incomplete.
• Have it deleted, where there's no legal reason for me to keep it. There are two exceptions: clinical and coaching records, which I keep for seven years after our work ends (Section 11); and the record that you agreed to my Terms and this policy, which I keep for six years after your account closes because it's my only proof the agreement existed. Everything else goes.
• Take it with you. Where I hold your data on the basis of consent or a contract, you can ask for it in a common, machine-readable format, or ask me to send it to someone else. In the app you don't need to ask: the export in Settings does exactly this, whenever you want, without involving me.
• Restrict or object to how I use it, including anything I do on the basis of legitimate interests.
• Stop marketing — this one is absolute. If you tell me to stop sending you marketing, I stop, no reason needed. Every email has an unsubscribe link, and it works.
• Withdraw consent for anything you consented to, at any time, as easily as you gave it. For cloud storage, that's a switch in Settings (Section 6). Withdrawing doesn't make what happened before unlawful; it stops it going forward.
• Complain — see below.

How to use them

Email [email protected]. I'll respond within one month, and it's free. If a request is unusually complex I may need up to two further months, in which case I'll tell you why within the first month. I may ask you to confirm your identity first, particularly for anything involving clinical records — that's to protect you, not to slow you down.

Some things you can do yourself, faster than I can: app content is on your device and you can delete or export it from Settings; you can revoke my access to a shared Trello board directly in Trello; you can unsubscribe from any email.

If you want to complain

Please tell me first — email me and I'll look into it properly. You also have the right to complain to the Information Commissioner's Office at any time, at ico.org.uk or on 0303 123 1113. You don't need my permission and it won't affect anything else.

19Updates to this policy

This policy may be updated from time to time to reflect legal, ethical or operational changes — including as new app features go live. The current version number and effective date are always at the top of this page, and previous versions are available on request.

If a change materially affects how I handle your information, I'll email you rather than relying on you noticing.