Why we wrote this
Privacy and cookie compliance usually sits with an organisation’s own legal, data protection or operations leads. Our role as a web partner is to make sure your website does what your policies say it should: the right notices in the right places, consent tools that work as intended, and forms that collect only what you need.
Over the past year, through our website health checks and day-to-day support work, we’ve started to see the same patterns come up across very different sites:
- spam protection running quietly on forms, with no mention of it in the privacy notice
- cookie banners in place, but analytics and marketing tags loading before visitors make a choice
- embedded videos and booking widgets setting cookies of their own
- sign-up forms that bundle marketing consent into a booking or enquiry
None of these are unusual, and most are quick to fix. Many happen because websites change over time: a new plugin, a tag added for a campaign, a video embedded on a page. Meanwhile, the guidance itself has moved on, with changes from Google, the ICO and new UK legislation all landing in 2026.
So we’ve pulled together the checks we’d suggest any arts organisation runs on its own site. They’re not legal advice, and we’re not privacy lawyers. They’re a practical starting point for a conversation with your legal team or data protection lead. Once you know what you need, we can help with the technical side: configuring consent tools, updating forms and notices, and making sure your site behaves the way your policies say it does.
What CAPTCHA does, and why you rarely see it
CAPTCHA tools check whether the person filling in your form is a human or a bot. Without them, contact, newsletter, and booking enquiry forms can fill up with spam within days.
The older style asks visitors to tick a box or pick out traffic lights in a grid. Most sites now use an invisible version instead. Google’s reCAPTCHA v3, for example, watches how someone interacts with the page and scores how likely they are to be human. The visitor never sees a puzzle.
That invisibility is good for your booking journey. It also means many teams forget the tool is there at all. By default, invisible reCAPTCHA shows a small badge in the corner of the screen. Plenty of sites hide that badge because it clashes with the design or covers a button. Hiding it is allowed, but only if you tell visitors another way.
What you need to tell visitors, and the wording changed this year
If you hide the reCAPTCHA badge, Google requires you to say on the page that your site uses reCAPTCHA. This is a condition of using Google’s service rather than a law, but breaking it puts you outside the terms you agreed to.
For years, the required wording was: “This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply”, with links to both Google documents. You’ll still find that line on thousands of websites and in most plugin documentation.
On 2 April 2026, Google changed its position. It now acts as a data processor for reCAPTCHA, and your organisation is the sole data controller: the one responsible for deciding how visitor data is used. Because of that, Google now recommends that sites remove the references to its Privacy Policy and Terms. The recommended line is simply:
This site is protected by reCAPTCHA.
Google also says sites should review their own privacy notices so they cover what reCAPTCHA processes data for: security, fraud, and abuse prevention (Google reCAPTCHA FAQ).
Where to put it. Google’s current FAQ doesn’t say exactly where the line should sit. Our recommendation is directly beneath the submit button on every protected form, where visitors will actually see it, rather than tucked away in a footer or privacy policy. Keep it short, readable, and accessible: sufficient colour contrast, real text rather than an image, and a size people can actually read. Done well, it adds no extra steps, no new fields, and no friction.
What it doesn’t mean. The notice doesn’t change your form fields, ask visitors to do anything, or slow the journey down. If a mock-up ever suggests otherwise, it’s worth asking why.
The bigger picture: privacy notices and cookies
The form notice is the visible part. Underneath it sit two sets of UK rules that apply to every arts organisation collecting details online.
Your privacy notice. Under UK data protection law, you have to tell people what personal data you collect, why, and who processes it on your behalf. Since Google now acts as your processor for reCAPTCHA, your privacy notice should name it and explain that it’s used for security and spam prevention. The same goes for any alternative tool you use.
Cookies and similar technologies. reCAPTCHA sets a cookie, which Google describes as necessary for its risk analysis (Google reCAPTCHA FAQ). In the UK, the Privacy and Electronic Communications Regulations (PECR) say you need consent before storing anything on someone’s device, unless an exception applies. The ICO’s updated guidance lists security among the purposes that can count as “strictly necessary”, which doesn’t need consent (ICO). The ICO is equally clear that the test is applied from the visitor’s point of view, and narrowly.
Two practical points follow. First, list your CAPTCHA cookie in your cookie notice as strictly necessary, with a plain-English explanation. Second, even when consent isn’t needed, transparency still is: the ICO says you must explain these technologies in a way anyone visiting can understand (ICO).
The stakes have also risen. The Data (Use and Access) Act 2025 raises maximum PECR fines to UK GDPR levels: up to £17.5 million or 4% of global annual turnover, whichever is higher (Howard Kennedy). Few arts organisations are likely targets, but the direction of travel is clear.
Cookie consent: the features that help
We’re not privacy or cookie-compliance specialists, and this is a specialised area that sits with your legal or data protection lead. But our website health checks often turn up the same few gaps, and most are straightforward to fix on the website itself:
- A consent tool that actually blocks. Analytics and advertising tags, such as Google Analytics or the Meta pixel, shouldn’t load until a visitor makes a choice. We regularly see banners in place while tracking fires as soon as the page loads.
- A banner that shows up straight away. Some consent tools wait until everything on the page has finished loading before they show the banner. On our own site, a large background video held it back for close to a minute in our testing, so visitors could browse for some time before being asked. If your banner takes a while to appear, ask your developer to load it earlier.
- A real choice. “Reject” should be as easy as “Accept”, with no marketing or advertising categories switched on by default. Banners that say “by continuing to use this site, you accept cookies” don’t meet UK rules (ICO): consent has to be an active choice, made before any marketing or analytics tags load.
- A way to change your mind. A “Cookie settings” link in your footer, or a small floating icon, lets visitors reopen their choices at any time.
- A privacy policy in the first place. Some of the sites we check don’t have one at all, or don’t link to it from their forms. Any site that collects visitors’ details needs a privacy policy and a cookie notice, linked from the footer and from every form.
- Notices that match reality. Your cookie notice and privacy policy should list what’s actually running, including CAPTCHA and analytics tools, in plain English.
- No forgotten code. Retired tags, such as the old Universal Analytics code that Google stopped collecting data with in 2023, are still on many sites and should be removed.
What about analytics? Recent changes under the Data (Use and Access) Act mean some analytics used purely to understand and improve your own site may not need consent, as long as visitors are told and can easily opt out (ICO). In practice, an opt-out means a clear “turn off analytics” option in your cookie banner and cookie settings, and a site that actually stops tracking when someone uses it. Whether that covers your setup, especially Google Analytics, depends on how it’s configured, so check with a specialist. Marketing and advertising tags, like the Meta pixel, still need consent first.
Is it a big job? For most sites, setting up consent properly is a few hours’ developer work, not a rebuild. The fiddly part is usually tracking code that has built up over the years in different places, and testing that a visitor’s choice is actually respected.
Videos, booking widgets and other embeds
Embedded content can quietly undo a well-configured cookie banner. A YouTube video, a booking widget or a ticketing iframe can set its own cookies the moment the page loads, before a visitor has made any choice.
On one site we look after, a routine cookie scan flagged exactly this. The fix was simple: make sure the consent tool loads before any tracking scripts, and hold the video back until the visitor agrees. But blocking the video outright left an awkward “accept cookies” wall where the content should be.
The better answer was a click-to-load approach. Visitors see a normal thumbnail and play button. Nothing from YouTube loads until they click, and at that moment a single “Accept marketing cookies to play” button asks for consent in context. It’s compliant, it feels natural, and it took a couple of hours of developer time.
A few things worth knowing:
- YouTube’s privacy-enhanced mode helps, but isn’t entirely cookie-free. Switching embeds to youtube-nocookie.com is a quick improvement, but it’s not a complete answer on its own.
- Marketing cookies can’t be switched on by default. Consent has to be an active choice, even when it’s only to play a video.
- Ticketing and booking widgets run on your provider’s system. Ask them how their embed handles consent, and whether it can wait until a visitor agrees.
Opt-in consent: getting sign-ups right
Spam protection decides who can submit a form. Consent decides what you can do with their details afterwards. For most venues, that means email marketing.
Under PECR, you generally need someone’s consent before sending them marketing emails or texts. There are two exceptions, known as soft opt-ins, which we’ll cover below. Where you rely on consent, good practice looks like this:
- Separate it from the transaction. Booking a ticket or sending an enquiry shouldn’t automatically sign someone up. Ask the marketing question on its own.
- No pre-ticked boxes. The visitor has to actively choose to opt in.
- Say what they’re signing up for. “Season announcements and priority booking, about twice a month” is clearer and more inviting than “news and offers”.
- Ask only for what you need. A newsletter sign-up needs an email address. Extra fields such as phone numbers or job titles feel intrusive and cost you sign-ups.
- Make leaving easy. Every email needs a simple unsubscribe link, and it has to work.
- Keep a record. Your system should log when and how each person opted in, so you can show it if asked.
This is also where psychology and compliance point the same way. People commit more readily when they know exactly what they’re agreeing to and feel in control of it. A clear, honest sign-up builds a list of people who actually want to hear from you.
The charity soft opt-in: an opportunity with conditions
If your organisation is a registered charity, this year brought a genuinely useful change, and plenty of room for confusion.
The long-standing soft opt-in lets any organisation email existing customers about similar products or services without fresh consent, as long as they could opt out when they first gave their details. The Data (Use and Access) Act 2025 added a second version just for charities. The charitable purposes soft opt-in came into force on 5 February 2026, and the ICO published updated guidance on 28 April 2026 (source).
To use it, a charity has to meet all of these conditions, according to that guidance:
- You collected the details yourself. Details collected by someone else, even a closely connected organisation such as a trading subsidiary or a third-party fundraising platform, don’t qualify.
- The person showed support or interest. Donating, volunteering, or engaging with your mission counts. Incidental contact, like using a charity café’s free wifi, doesn’t.
- The marketing furthers your own charitable purposes. Appeals, volunteering, and news about your work are fine. Promoting other organisations, including other charities, isn’t.
- You offer a clear opt-out at the point of collection and in every message. An opt-out buried in a privacy policy won’t do.
- The details were collected on or after 5 February 2026. It can’t be applied to existing lists.
Why this matters for venues. Many theatres and arts organisations are charities that also sell tickets, memberships, and merchandise. The ICO says a single interaction can sometimes qualify for both soft opt-ins, but you’d need separate opt-outs for each and systems that record them separately (source). A ticket bought through an external box office platform adds another layer: whose data is it, and who collected it?
This is the part we’d encourage every charitable venue to slow down on. Map where supporter details come in: donation forms, booking journeys, membership sign-ups, and partner platforms. Then decide, for each one, whether you’re relying on consent, the products and services soft opt-in, or the charitable purposes soft opt-in. Your forms, privacy notice, and CRM all need to reflect that decision.
Alternatives to reCAPTCHA
reCAPTCHA is the most common choice, but it isn’t the only one. The right option depends on how much spam you get, what your platform supports, and how much data you’re comfortable sending to a third party.
| Option | How it works | Visitor experience | Privacy footprint |
|---|---|---|---|
| Google reCAPTCHA v3 | Scores visitor behaviour invisibly | No puzzle; badge or text notice | Sets a cookie; Google acts as your processor since April 2026 (Google) |
| Cloudflare Turnstile | Runs rotating background browser checks | Usually no puzzle; free to use | Cloudflare said at launch in 2022 that it never uses cookies to collect or store information (Cloudflare) |
| hCaptcha and similar services | Challenge or invisible checks from an independent provider | Varies by setting | Check each provider’s privacy terms |
| Honeypot fields plus timing checks | Hidden fields that only bots fill in, and rejecting forms submitted impossibly fast | Invisible; nothing to see | No third party involved |
For most arts organisations, the web community’s direction of travel is towards lighter, more private tools: Turnstile or a well-built honeypot first, with reCAPTCHA reserved for sites that face heavier attacks. Whatever you choose, the same principles apply. Name it in your privacy notice, list any cookies it sets, and be open with visitors about it.
A note for US audiences and organisations
If you’re based in the US, or have significant US audiences, the rules work differently from the UK. There’s no single federal privacy law. Instead, a growing number of states have their own, and they vary in who they apply to and what they require. A few differences worth knowing:
- Opt-out rather than opt-in. Most US state laws don’t require consent before analytics or advertising cookies load. Instead, visitors must be able to opt out of their data being “sold” or “shared” for targeted advertising, often through a clear link such as “Do Not Sell or Share My Personal Information”.
- Browser privacy signals. Several states expect websites to respect the Global Privacy Control (GPC), a browser setting that automatically tells sites a visitor wants to opt out. Many consent tools can detect and honour it.
- Nonprofits aren’t always exempt. Some state laws only apply to businesses above certain size thresholds, but several also cover nonprofits (VeraSafe). Check with your advisers rather than assuming you’re out of scope.
- Tracking pixels carry legal risk. US organisations have faced a wave of lawsuits over advertising pixels, chat tools and session recording, including claims that pixels on pages with video share viewing history without permission (Buchanan Ingersoll & Rooney). It’s worth reviewing which tags run on your site.
The reCAPTCHA wording change applies worldwide, and the practical features in this guide still apply: a consent tool that works as configured, accurate privacy notices, and tags that respect visitors’ choices. But what your site needs to do depends on which states you operate in, so confirm the specifics with your legal team.
A quick health check for your forms and cookies
If you only do one thing after reading this, run through these questions with whoever looks after your website:
- Do we have a privacy policy and cookie notice, linked from the footer and from every form?
- Do we know which spam protection tool runs on each form?
- If the reCAPTCHA badge is hidden, does each form show “This site is protected by reCAPTCHA” beneath the submit button?
- Have we removed the old references to Google’s Privacy Policy and Terms of Service?
- Does our privacy notice name our CAPTCHA provider and explain it’s used for security?
- Is the CAPTCHA cookie listed in our cookie notice as strictly necessary?
- Are marketing opt-ins separate from bookings and enquiries, with no pre-ticked boxes?
- Does every sign-up form ask only for what it needs?
- If we’re a charity, have we decided which basis we rely on for each way supporter details come in?
- Does our consent tool stop analytics and marketing tags loading until a visitor makes a choice?
- Is “Reject” as easy as “Accept”, with no marketing categories switched on by default and no “by continuing to use this site” wording?
- Is there a “Cookie settings” link so visitors can change their mind later?
- Have we removed old or unused tracking code, such as Universal Analytics?
- Do videos, booking widgets and other embeds wait for consent before loading?
How we’re approaching this at Chaptr
We’re offering a one-off check to every site we host, and building these features into new projects as standard. That means the right notice on every protected form, privacy and cookie notices that reflect the tools actually in use, consent tools and embeds that respect visitors’ choices, and opt-in journeys designed to be clear rather than clever. Nothing goes live without your review and approval.
If any of this raises questions about your own forms or cookie setup, or you’re working through the charity soft opt-in and want a second pair of eyes on your supporter journeys, we’re happy to chat.
Not sure where your site stands? Our HOME health check looks at your website from the outside, the way a visitor or a search engine sees it, and flags issues like these alongside hosting, maintenance and accessibility. Find out more at care.chaptr.studio.
This article is general guidance, not legal advice. For decisions about your own organisation, please speak to your data protection lead or legal adviser.
Sources
- Google reCAPTCHA FAQ (Google Cloud Fraud Defense), last updated 29 October 2026
- ICO: What are the exceptions? (storage and access technologies)
- ICO: How do we comply with the PECR rules?
- Lewis Silkin: The charitable purposes soft opt-in, ICO issues updated direct marketing guidance, 8 May 2026
- Howard Kennedy: Unlocking new privacy standards, higher fines for direct marketing and cookie breaches, 25 June 2025
- Cloudflare: Announcing Turnstile
- ICO: How do we manage consent in practice?
- ICO: The Data (Use and Access) Act 2025, what does it mean for organisations?
- Global Privacy Control
- VeraSafe: U.S. privacy laws for nonprofits
- Buchanan Ingersoll & Rooney: Is your website a lawsuit target? Emerging trends in chat, pixel and VPPA cases