Preskoči na sadržaj
Sports Club Website GDPR: What We Found on 739 Club Websites

Sports Club Website GDPR: What We Found on 739 Club Websites

We checked 739 sports club websites for GDPR and cookie-consent problems. Most track visitors before they agree, collect children's data through forms with no privacy notice, or hide where data goes. Here is what to fix and how.

Most sports club websites have a GDPR problem, and the club usually doesn't know. The website was built by a volunteer or an agency years ago, a plugin added Google Analytics, someone embedded a YouTube video and a Google Form for enrolment, and nobody has looked at it since. Meanwhile the site collects names, phone numbers and children's dates of birth.

In November 2026 we checked 739 Croatian sports club websites: tennis, padel, football, swimming, martial arts, fitness and more. We opened each site the way a first-time visitor would, in a fresh browser, without touching the cookie banner and without submitting anything. We recorded what loaded before consent, whether there was a banner and what it offered, which forms asked for personal data, and what the privacy policy said. We name no clubs here. The problems are common enough that naming any one of them would be unfair.

This article covers the seven problems we saw most, why each one matters, and what a club can do about it.

What we found

Of the 739 websites that loaded:

  • 219 started Google Analytics, the Meta Pixel or other analytics and ad tracking before the visitor agreed to anything. 112 of them had no cookie banner at all.
  • 95 had a cookie-consent tool installed that didn't actually block the trackers.
  • 68 cookie banners had no way to refuse on the first screen, only "Accept" or "OK". 30 said that continuing to browse counts as consent.
  • 264 collected personal data through a form: contact forms, membership applications, school enrolment, camp sign-ups.
  • 139 of those had no privacy policy anywhere on the site.
  • 50 enrolment forms asked for a child's date of birth, personal identification number (OIB) or health information.
  • 46 sent enrolment to Google Forms, Jotform, Typeform or similar.
  • 22 served a personal-data form over plain HTTP, without encryption.
  • 150 privacy policies were missing basic items: who the controller is, the legal basis, how long data is kept, or the right to complain to the data protection authority.
  • 144 sites sent visitor data to US services (Google Analytics, Google Fonts, YouTube, Google Maps) with a privacy policy that never mentions data leaving the EU.

These figures come from one visit to each site on a desktop browser, so a banner shown only on mobile, or a form behind a login, wouldn't have been seen. They are a snapshot, but a consistent one.

The seven problems, and why they matter

Under the EU's ePrivacy rules, transposed in Croatia by the Electronic Communications Act, a website may store or read cookies on a visitor's device without consent only when that is strictly necessary to provide the service. Analytics and advertising are not strictly necessary. The Court of Justice made this explicit in Planet49 (2019), and it doesn't matter whether the cookie holds personal data.

So a site that loads Google Analytics or the Meta Pixel the moment someone arrives is in breach, banner or not. The most common cause we saw was a theme or plugin that adds the tracking code directly, with the consent tool added later and never connected to it.

2. A banner that only lets you say yes

Consent under the GDPR has to be freely given and as easy to withdraw as to give (Articles 4(11) and 7). The European Data Protection Board's cookie banner taskforce found that a first screen with "Accept" and no "Reject" doesn't meet that standard, and neither does "by continuing to browse you agree". A banner that asks the question but offers only one answer is decoration.

3. Forms with no privacy notice

When you collect personal data, Article 13 of the GDPR requires you to tell the person, at that moment: who you are, why you want the data, on what legal basis, how long you keep it, who else gets it, what their rights are, and that they can complain to the supervisory authority (AZOP in Croatia). A contact form or membership application with no link to a privacy policy can't do that.

4. Children's data

Football schools, swimming clubs and tennis academies ask for a lot about children: date of birth, OIB, school, allergies, sometimes medical conditions. The GDPR (recital 38) says children's data deserves specific protection, and health data is a special category under Article 9. We saw enrolment forms collecting all of this with no privacy notice, no consent checkbox, and in a few cases over plain HTTP. If you are unsure at what age a child can consent for themselves, see the age of digital consent by country.

5. Enrolment through Google Forms

Google Forms is free and quick, which is why clubs use it. It also means a child's details sit in a personal Google account, copied into a spreadsheet, shared with whoever has the link, with no record of what the parent agreed to and no way to delete it reliably when the child leaves. It is not illegal in itself, but your privacy policy has to name Google as a processor, you need a data processing agreement, and you have to manage access. Few clubs do.

6. Forms over plain HTTP

A form served without HTTPS sends names, phone numbers and dates of birth across the internet in readable text. Article 32 of the GDPR requires appropriate security, and in 2026 a free TLS certificate is the bare minimum. Browsers also mark these pages "Not secure", which tells parents something about the club, fairly or not.

7. Data going to the US, unmentioned

Since the EU-US Data Privacy Framework (2023), sending data to certified US companies such as Google and Meta is lawful. What the GDPR still requires is that you say so. A site that loads Google Fonts, Google Maps or YouTube passes every visitor's IP address to Google, and the privacy policy has to mention it. Most of the policies we read were copied from a template written before the site added those services, or before the GDPR existed. Two still cited the Croatian data protection act repealed in 2018.

How clubs usually handle it

Most clubs fix this in pieces. Someone installs a free cookie plugin, which shows a banner but often doesn't block anything. Someone else downloads a privacy policy template and fills in the club's name. The enrolment form stays on Google Forms because it works. Each step looks like compliance, and none of them connects to the others.

The underlying problem is that a club website is usually a patchwork of tools: a WordPress theme, a form plugin, Google Analytics, embedded maps and videos, a separate booking system. Every tool adds its own tracking and its own data flow, and nobody owns the whole picture.

What to do

Start with what visitors see before they click anything.

  1. Open your site in a private window and don't click the banner. In your browser's developer tools, look at the Network tab and the cookies. If anything from google-analytics.com, googletagmanager.com, facebook.net or doubleclick.net appears, you are tracking before consent.
  2. Decide whether you need analytics at all. Many clubs never look at their Google Analytics. Removing it is the simplest fix there is.
  3. If you keep tracking, make the banner work. The tool must block scripts until consent, offer "Reject" as clearly as "Accept", and remember the choice.
  4. Load maps and videos on click. Replace embedded Google Maps and YouTube with a placeholder that loads them when the visitor asks, plus a plain "Open in Google Maps" link.
  5. Link a real privacy policy from every form. It should name the club as controller (with its OIB and address), list what you collect and why, how long you keep it, who receives it (including Google if you use its services), and the right to complain to AZOP.
  6. Take enrolment off Google Forms. Use a form that records each consent separately and keeps the data where you can manage and delete it. A sports school registration form covers what it should ask.
  7. Turn on HTTPS everywhere and redirect plain HTTP to it.
  8. Ask only for what you need. If you don't use a child's OIB until the first invoice, don't ask for it on the enquiry form.

Example

A hypothetical football club with 180 children in its school has a WordPress site built in 2017. Google Analytics, a Facebook page plugin and a Google Map in the footer load on every page. Enrolment is a Google Form linked from the menu, asking for the child's name, date of birth, OIB, the parents' phone numbers and "health notes". The privacy policy is a 2018 template that mentions neither Google nor AZOP.

The fix doesn't need a lawyer for every line. The club removes Analytics (nobody had logged in for two years), swaps the Facebook plugin for a plain link, and makes the map load on click. It moves enrolment to a form that shows the privacy policy and records consents separately, so the spreadsheet of children's OIBs in a coach's personal Google account can be deleted. The privacy policy now names the club, the platform that processes its data, where that data is hosted, and AZOP. An afternoon's work removes most of the risk.

How SportyPlus can help

SportyPlus gives every club a website that is part of the same platform as its bookings, memberships and school enrolment, so there's no patchwork. A SportyPlus club site loads no analytics or advertising trackers. Maps load only when a visitor asks for them. Every club gets its own privacy policy and terms of use, generated with the club's details and editable in the CMS. Both are linked from the footer of every page and from every place someone can create an account: registration, sign-in with Google, Apple or Microsoft, checkout, the chat, newsletter sign-ups and school enrolment.

School enrolment records each consent separately, with the wording the parent saw, and the child's data goes straight into a member profile the club controls rather than a shared spreadsheet. Mailing lists use double opt-in. Medical documents are encrypted and every access is logged. Club data is hosted in Frankfurt, and the full list of sub-processors and where they process data is public. The club website builder is part of every plan.

Practical recommendations

  • Check your own site today with a private window and the browser's developer tools. It takes five minutes.
  • Remove any tracking tool you don't actually use.
  • Never pre-tick a consent box, and never bundle photo consent with data processing.
  • Put a privacy policy link next to the submit button of every form, not only in the footer.
  • Write down which outside services your site uses (fonts, maps, video, forms, payments) and make sure the privacy policy names each one.
  • Review the privacy policy once a year, and whenever you add a tool to the site.

No. A site that sets only strictly necessary cookies (keeping someone signed in, remembering their language) doesn't need consent for them. You still need to explain them in your privacy or cookie policy.

Is Google Fonts a GDPR problem?

Loading fonts from Google's servers sends each visitor's IP address to Google. Under the Data Privacy Framework that transfer is lawful, but it must be disclosed. Hosting the font files on your own server avoids the question entirely.

Can we keep using Google Forms for enrolment?

You can, but you'll need a data processing agreement with Google, a privacy notice on the form, control over who can open the responses, and a way to delete a child's data when they leave. A dedicated enrolment form usually ends up being less work.

Who is responsible: the club or the agency that built the site?

The club. As data controller it is responsible for what its website collects and how, even if someone else built it.

What can AZOP do?

AZOP can order a club to fix its processing and can impose fines under the GDPR. Complaints from parents are the usual trigger. In practice most clubs fix these problems long before it comes to that, once they know.

Want a club website that doesn't track your visitors and links your privacy policy wherever someone signs up? See the SportyPlus club website.