Your information, plainly
Last updated
What we collect. When you join AIMOCS we collect your email address and your name. If you choose to, you can add your role, seniority, country, organization type, and institution to your profile. If you apply to the cohort or the ambassador program, we keep what you write in the application. If you post in the community, register for an event, or take a course, we keep your posts, replies, reactions, registrations, course progress, and any certificates you earn. If you pay for a place in a cohort, we keep the name, email address, and phone number you give at checkout, and a record of what you paid.
Why we collect it. To run your membership: the community, the directory, events, courses, and certificates. To review applications. To email you when new material is published. We do not sell or rent your information. Apart from the measurement described under cookies below, we do not share it with advertisers.
What other people can see. Signed-in members can see your name, role, seniority, institution, and country on your member profile, and everything you post in the community. If you are featured as an ambassador, your name, institution, country, and track appear on the public ambassadors page. Each certificate you earn has a public verification page showing your name, the course, and the date it was issued; it can only be found with its verification code. Everything else is seen only by the team running AIMOCS.
Patients. Please do not post patient-identifiable information in the community. Describe a case without names, dates of birth, record numbers, images, or any other detail that could identify a patient.
Where it lives. Data is stored with our database provider (Supabase), and email is delivered through our email provider (Resend). Payments are handled by Stripe. Video is played from YouTube, and a bot check from Cloudflare may run on forms. Site analytics by Google and, on the cohort enrolment pages and the introductory session page only, advertising measurement by Meta run unless you opt out. Each is described on this page.
Emails, downloads and sign-ups. Some pages offer a download, a live session, a quotation or the AIMOCS briefing. We ask for your email address, and sometimes your name and role. Each of these forms says, under the button, that by signing up you agree to receive emails from AIMOCS, and submitting it adds you to our email list. We keep a record of what you agreed to: the exact wording shown, the date and time, the page, and a scrambled (hashed) form of your network address and browser details, never the raw address. Every email we send has an unsubscribe link; pressing it stops those emails at once and is recorded too.
Bot check. Where a form is being abused, we may add Cloudflare Turnstile, a check from Cloudflare that tells people from automated scripts. When it is switched on, your browser loads a script from Cloudflare and sends it some browser signals to decide whether you are a person. It is used for that check only.
Videos. Videos on AIMOCS are from YouTube. A video loads only when you click it, and it loads from YouTube’s privacy-enhanced address (youtube-nocookie.com). Until you click, nothing is fetched from YouTube and YouTube learns nothing about your visit. Once you play a video, YouTube’s own privacy policy covers it.
How long we keep it. Account and membership information stays while your account is open, and we delete it when you ask. Payment records are kept for as long as UK tax law requires. People on the email list stay on it until they unsubscribe; when you unsubscribe we keep a minimal record of that, so we do not email you again, and we delete your address on request. First-party analytics records carry no name or email address. Google Analytics data is kept for 14 months.
Your rights. You can ask to see your information, correct it, delete it, restrict or object to how we use it, or take a copy of it. You can withdraw consent at any time, as easily as you gave it. AIMOCS Limited is the company responsible for your information. If you are unhappy with our answer, you can complain to the Information Commissioner’s Office (ico.org.uk) in the UK, or to your local data protection authority. Write to hello@aimocs.com.
Payments. When you pay for a place in a cohort, you pay on a page run by Stripe. Your card details go to Stripe and never reach AIMOCS. We receive confirmation of the payment, the amount, and the name, email address, and phone number you gave at checkout, and we use them to enrol you. Stripe’s own privacy policy covers what it does with the rest.
Your choices. Marketing email, such as notes about new material, includes an unsubscribe link. Account email, such as your sign-in code, does not. You can ask us at any time to show you the information we hold about you, correct it, or delete it entirely. Write to hello@aimocs.com and we will handle it within 30 days. Your choice about cookies is described below, and you can change it at any time.
Cookies. Signing in sets cookies that keep you signed in. We also use cookies from Google Analytics on every page and, on the enrolment and session pages, from Meta, to measure visits and which ads bring people here. They are on by default, wherever you are, and you can opt out at any time: with Opt out in the small notice shown on your first visit, with Cookie settings in the footer of every page, or by sending Global Privacy Control from your browser. We remember your choice for 180 days in a small cookie of our own, aimocs_ads_consent. An older cookie of ours, aimocs_cr, which recorded only whether your connection appeared to come from the United States, is no longer used; the site removes it the next time you open a page. The cookies described below are the only others.
Our own analytics. We run first-party analytics: a few actions, such as starting and finishing the join form, are recorded with the page, the referring page, any campaign tags in the link, and a random identifier kept in your browser’s local storage. These records are not linked to your account, name, or email address. If your browser sends Do Not Track or Global Privacy Control, nothing is recorded. This does not use cookies.
Google Analytics. Unless you opt out, we use Google Analytics 4, from Google, to see how people use the site. It records which pages are read, how visitors arrive (the referring site and any campaign tags), roughly where they are (country and city), what kind of device and browser they use, and a few actions such as joining or signing in. It sets two cookies, _ga and _ga_ followed by an identifier, which let it recognise a returning browser. Google receives your IP address when its script loads, as any site you visit does. According to Google, Analytics 4 does not log or store IP addresses; it uses them to work out an approximate location. We keep Google Analytics data as set in our Google Analytics settings (14 months). We do not use Google Ads, and the site always tells Google not to use your visit for advertising. If you opt out, Google Analytics stops at once: its cookies are removed from your browser and it is not loaded again. If your browser sends Global Privacy Control, it is not loaded at all, and Google receives nothing about your visit.
Advertising on the enrolment and session pages. Unless you opt out, the pages where you enrol in a cohort or register for the introductory session, and only those pages, also use the Meta pixel in your browser and, from our servers, Meta’s Conversions API. They tell Meta when someone views one of those pages, asks for the syllabus, registers for the session as a doctor, starts checkout, or enrols, so we can measure which ads bring people here. The pixel sets a cookie, _fbp, and, if you arrived from an ad, _fbc, which let Meta recognise your browser. Meta can receive the page address, your IP address, your browser type, and an identifier from the ad you clicked. When you ask for the syllabus, register as a doctor or start checkout, it can also receive the email address you typed, and once you enrol, the email address, name, phone number, and country you gave at checkout; these are scrambled (hashed) before they are sent. We send no health information. If you opt out, nothing more goes to Meta: the pixel’s cookies are removed, the pixel is not loaded again, and our servers send Meta no events about you. If your browser sends Global Privacy Control, the pixel is not loaded at all and our servers send Meta nothing. Meta’s privacy policy covers what it does next.
Your choice. One choice covers Google Analytics and Meta. Both are on by default, wherever you are. On your first visit a small notice says so: OK keeps them on and Opt out turns them off. If your browser sends Global Privacy Control, we treat that as opting out of both, unless you choose Allow in Cookie settings yourself. You can change your mind at any time with Cookie settings in the footer of every page. Opting out removes the Google Analytics and Meta cookies from your browser and stops anything further being sent.
Questions. hello@aimocs.com