How I handle your data
OCD: Conditions for Allowing · Last updated: 21 October 2026
This page explains what personal information I collect when you buy the book, use the portal or the Allowing app, book a call, or work with me — and what I do with it. I've written it in plain English on purpose. If anything is unclear, email me and I'll give you a straight answer.
I'm David Laing, and I run OCD: Conditions for Allowing as a sole trader, based in Eastbourne, East Sussex, United Kingdom. For data protection law, I'm the "controller" of your information — meaning I'm the one responsible for looking after it.
When you buy something (the book, a toolkit, an Allowing app subscription, a membership, or a programme): your name, email address, what you bought, and payment confirmation. Payments are processed by Stripe — your card details go directly to Stripe and never touch my systems.
When you start a checkout and don't finish it: what you gave on the first step (your name, your email address and, if you entered it, your phone number), and which checkout it was. My checkout provider also notes the internet address and browser you used, and which ad or page brought you there. I may email you about the book, my work and my offers.
When you book a call with me: your name, email, phone number, and your answers to the booking questions. Some of those questions ask about your experience of OCD and how you're doing — that's sensitive health information, and it gets special treatment (see section 3).
When you create a portal account (portal.conditionsforallowing.com): your email and login, your course progress, which recordings you play there and when, any notes you choose to leave on a recording, and — if you're in a programme — the things you choose to log there: daily practices, reflections, check-ins. Much of that is also sensitive health information (section 3 again).
When you use the AI tools (the ones in your portal, and the conversation in the app): whatever you type into them, and the responses that come back. That's sensitive health information too — section 3 covers it, and section 5 names every company that touches it.
If you speak to a tool instead of typing: your microphone audio is sent to be turned into text. The audio is not kept — it is transcribed and discarded, and it never reaches my database. The transcript is kept, in your portal account, the same as if you had typed it. The spoken reply you hear is generated the same way and is not stored either.
When you use the Allowing app: the app works through your portal account, and what it sends is kept there. It sends: your email address, to sign you in (each request to sign in is kept for 24 hours with the internet address it came from, so I can stop anyone guessing codes); the conversation, meaning a record that you opened it, everything you type into it and, if you report a reply, which one, all handled as above; what you write and choose in the allowing experiment and its journal; and a short note with the time and the app version each time you open the app, sign in, or a sign-in fails, so I can see whether the app is being used. If the address you type has no account with me, it goes into my customer records, and I email it about how to get the app. The practice opens the conversation when you're signed in and online. When it can't (you're offline, say), it runs on your phone alone and sends nothing. The app also checks for updates, which tells my update provider your app version, whether your phone is Android or iPhone, and a random number for this copy of the app — see section 5.
When I email you: which emails you open and which links you click (this is how email platforms work; I use it to decide who hears from me again, and to stop sending things you clearly don't want).
When you visit the website: see section 6 (cookies and analytics).
When we're working together (the membership or a programme): what you share on calls, in the community, in check-ins, and — if you're in a programme — in our WhatsApp thread.
If you post in the community: for the weekly draw, I keep a record of who posted each week and when (your community name and your posts' links), the draw's order and its result. To check whether the people drawn have the Allowing app, in the order they were drawn, I look for the app on the email their Skool account uses, or on another email they send me. If someone asks, I confirm the draw took place with the winner's first name and country, unless the winner tells me not to; and if the advertising regulator (the ASA) asks, I show them the draw's record. It's used for nothing else.
I don't collect anything I haven't listed here, and I never buy data about you from anyone.
Because of what this work is, some of what you share with me is information about your mental health. The law calls this "special category data" and requires explicit consent to use it. Here's how that works honestly:
You can withdraw consent at any time by emailing me — I'll delete the information (unless a legal duty, like tax records, requires keeping the purchase itself).
I'm a small business; these companies store or move data on my behalf. Each is bound by a contract limiting them to exactly that:
| Provider | What for |
|---|---|
| HighLevel ("LeadConnector") | Customer records, email sending, booking, checkout pages, SMS |
| Stripe | Payment processing (they hold the card details, not me) |
| Supabase | The portal database (accounts, progress, logs) |
| Anthropic | The AI tools in the portal and the app. What you type is sent to their Claude models to generate the response; under their commercial terms it is not used to train those models. |
| ElevenLabs | Speech. If you speak to a tool instead of typing, your audio goes to them to be turned into text; the spoken voice you hear back is generated by them too. |
| OpenAI | Two things: backup transcription, used only if ElevenLabs doesn't answer; and turning what you type in the portal tools into a search query, so the tool can find the relevant part of my material to answer from. |
| Expo | Delivering updates to the Allowing app. Your phone asks them for the current version, sending its app version, whether it is Android or iPhone, and a random number for this copy of the app. If an update ever fails to start, a short error report goes with the next check. They see that, not what you do in the app. |
| Resend | Sending sign-in emails: the code for the app and the link for the portal. |
| Vercel | Hosting the website and portal |
| Zoom | Calls and sessions |
| Fathom | Call transcription |
| Google Workspace | Business email |
| Skool | The community (their platform, their own privacy policy applies there). Zapier passes your email to Skool to send your invite. |
| Meta / Microsoft | Advertising and analytics — see section 6 |
I never sell your data. Nobody gets it for their own marketing.
The website (conditionsforallowing.com) currently uses:
You'll be asked before any of the advertising/analytics ones load, and "no" is a one-click answer. You can also block cookies in your browser settings at any time; the site works fine without them.
The checkout pages (checkout.conditionsforallowing.com, run through my checkout provider) also use the Meta Pixel. The consent prompt above covers this website; on the checkout pages the Pixel currently loads without a prompt — I'm extending the same consent control there.
Also from my own records, whatever you choose in the prompt: when your details first go into my customer records (for most people, the first step of a checkout), and when you buy something at my checkout, my reporting system tells Meta. That lets me see which ads lead to real orders, and lets Meta show my ads to people like the ones who buy. It sends your email address, phone number, name and country in a scrambled form (a one-way code that Meta compares with its own users', to find your Facebook or Instagram account if you have one); the internet address and browser you used, as they are; the code from the ad you clicked and the one Meta's Pixel left in your browser, if they exist; a reference number from my records; and the time. For a purchase it also sends the amount you paid, the name of the ad you came from, and the address of the page you arrived at (which can include the ad's tags). No card details, and nothing you've written to me, in the portal or in the app. My work is about OCD, though, so the fact that you're in my records at all says something about you. Meta receives all this under its own policy.
Some of the providers above (HighLevel, Stripe, Meta, Microsoft, Zoom, Google, Supabase, Anthropic, ElevenLabs, OpenAI, Expo and Resend) store or process data in the United States. Those transfers are covered by the UK's approved safeguards — the UK–US Data Bridge where the provider is certified, or the UK's standard contractual terms (IDTA/Addendum) where not.
You can ask me, at any time, to: see what I hold about you; correct it; delete it; restrict what I do with it; hand it over in a portable format; or stop using it for marketing (that last one, I must and will do, no questions). Email david@conditionsforallowing.com — I'll respond within a month, usually much faster.
If you're unhappy with how I've handled your data, you can complain to the UK regulator: the Information Commissioner's Office — ico.org.uk / 0303 123 1113. (I'd appreciate the chance to fix it first, but that's your right regardless.)
My products and programmes are for adults — 18 and over. That includes the portal, the AI tools and the Allowing app: you must be 18 or over to use them. If you're a parent, guardian or carer of a young person with OCD, you're welcome here — but the account, the purchase and the data are yours, as the adult. I don't knowingly collect information from anyone under 18; if that's happened, email me and I'll delete it.
If I change this policy in any way that matters, I'll update the date at the top and — for anything significant — tell the email list. The current version always lives at this address.
I'm not a therapist or doctor, and nothing here is therapy, medical advice, diagnosis, or treatment. I teach from lived experience of OCD and complete recovery. This work can sit alongside professional care, but it isn't a replacement for it — and please don't change or stop any medication without talking to whoever prescribed it.
If you're in crisis right now, please don't wait for an email or a call with me. In the UK: call Samaritans free on 116 123 (any time, day or night), call NHS 111 and choose the mental health option, or dial 999 if you or someone else is in immediate danger. Outside the UK, contact your local emergency number or a crisis line where you are. Reaching for that kind of help is never a step backwards.