Skip to content

Your cart

Your cart is empty.

Add a service in the shop and it waits here until you check out.

Browse the shop

After you pay

  1. The team reads your details and emails you, usually within one working day.
  2. You follow the work and talk to the team in your client portal.
Subtotal

One-time service fees in USD.

Checkout View cart
Privacy

What your website quietly collects, and how to cut it down

Forms, analytics, embeds, cookies and server logs all gather visitor data. How to see exactly what your site collects, then keep only what you need.

Published: 5 min read5 sources

Most small business websites collect more about visitors than their owners know. Not because anyone planned it, but because every plugin, script and embed added over the years brings its own data collection with it. This guide shows where that data comes from, how to see it for yourself in about half an hour, and how to cut it back.

Why it matters

Under the GDPR, an IP address or a cookie identifier can be personal data. Recital 30 names both as online identifiers that, combined with other information, can be used to profile and identify people. The data minimisation principle in Article 5 says personal data must be “limited to what is necessary” for its purpose.

So “we only run a small brochure site” is not a defence. If the site collects it, you are responsible for it.

The five places data comes from

1. Server logs

Every request to your site is usually logged: the visitor’s IP address, the time, the page, the browser and the referring page. Many hosting setups keep these for months unless someone changes it. Few owners ever look at them.

2. Forms

Contact, quote and newsletter forms are the most obvious collection point, and the easiest to overdo. Common problems:

  • Fields you never use (date of birth, company size, full address for a simple enquiry).
  • Submissions stored twice: emailed to you and saved in a plugin database nobody checks.
  • Old entries kept forever because nothing deletes them.

3. Analytics

Analytics scripts usually set cookies, record pages viewed, device details and approximate location, and often send all of it to a third party. Some tools also record mouse movement, clicks and scrolling for “session replay”, which can capture what people type into forms unless the tool is set to mask it.

4. Embeds and third-party resources

A video player, a map, a social feed, a booking widget, a chat bubble or a web font loaded from someone else’s server: each one makes the visitor’s browser connect to that company. That connection alone sends the visitor’s IP address and browser details, and many embeds set their own cookies before the visitor clicks anything.

The EDPB describes a tracking pixel as a link to a resource, usually an image, embedded in a page or email, whose job is often just to make the browser contact the pixel’s host. Tracking links do the same with an identifier added to the URL. In its 2024 guidelines the EDPB treats both as covered by the ePrivacy cookie rule (Article 5(3)), the same as cookies. Advertising and email marketing tools add these routinely.

How to see what your site collects

You need a desktop browser and 30 minutes. No special software.

  1. Open a private window so you start with no cookies.
  2. Open the developer tools (right-click the page, choose Inspect) and go to the Network tab. Tick “Disable cache”.
  3. Load your home page without touching the cookie banner. Sort the list by domain. Every domain that is not yours is a third party receiving the visitor’s IP address.
  4. Check the Application (or Storage) tab. Look under Cookies and Local Storage. Any analytics, advertising or social cookie set before consent is a finding.
  5. Repeat on your contact page, a product page and a page with a video or map.
  6. Submit a test enquiry. Then find every place it ended up: your inbox, the website’s admin area, any CRM or mailing tool connected to the form.
  7. Ask your host what server logs are kept, what they contain, and for how long.

Write the results in a simple table: what is collected, by whom, why, and for how long. The EDPB’s cookie banner taskforce noted that website owners are responsible for keeping a list of the cookies they use and being able to show why each one is essential. Your table is the start of that list.

How to cut it down

Work through your table and ask one question per row: do we actually use this?

Remove what you don’t use

  • Delete plugins, scripts and tags left over from old campaigns, past agencies or tools you cancelled.
  • If two analytics tools are running, keep one.
  • Remove social sharing widgets nobody clicks.

Load embeds only on request

Replace live video, map and social embeds with a static preview image. Load the real embed only when the visitor clicks. Nothing is sent to the third party until the visitor chooses to.

Host fonts and files yourself

Serve web fonts, scripts and images from your own domain instead of a third-party server. The site looks the same and the visitor’s IP address stays with you.

Trim your forms

  • Ask only for what you need to reply. Usually that is a name, a way to contact the person and their message.
  • Make optional fields clearly optional, or remove them.
  • Pick one place submissions are stored. Turn off the duplicate.
  • Set a retention period, for example 12 months for enquiries that did not become customers, and delete on schedule.

Choose lighter analytics

Decide which numbers you actually look at. For most small sites that is page views, where visitors came from and which pages lead to an enquiry. Tools that count those without profiling individuals collect far less.

Be aware that the rules on analytics cookies differ by country. France’s regulator, the CNIL, accepts consent-free analytics only under strict conditions, including truncating IP addresses, limiting cookie lifetime to 13 months and not combining the data with anything else. It also states that most large analytics offerings do not qualify, however they are configured.

Shorten log retention

Ask your host to keep raw server logs only as long as you need them for security and troubleshooting. Weeks, not years.

Keep it from creeping back

Data collection grows every time someone adds a plugin or a marketing tag. Two habits stop that:

  • One owner. One person approves anything new added to the site, and updates the table.
  • A quarterly check. Repeat the 30-minute browser check every three months and after any redesign.

General guidance, not legal advice.

Where EWC can help

Our general cybersecurity assessment checks your website’s cookie settings, security headers and public data exposure, and gives you a prioritised list of what to fix first.

Sources

What this article is based on.

5 sources
  1. European Data Protection BoardGuidelines 2/2023 on Technical Scope of Art. 5(3) of ePrivacy Directive (version 2.0)edpb.europa.eu
  2. European Data Protection BoardReport of the work undertaken by the Cookie Banner Taskforceedpb.europa.eu
  3. Intersoft Consulting (GDPR text)GDPR Recital 30: Online identifiers for profiling and identificationgdpr-info.eu
  4. Intersoft Consulting (GDPR text)GDPR Article 5: Principles relating to processing of personal datagdpr-info.eu
  5. CNILSheet n°16: Use analytics on your websites and applicationscnil.fr

Where we can help · Level 1

General cybersecurity assessment

Review your website’s visible security risks and get practical recommendations.

What you get

  • Exposure & configurationHTTPS, headers, cookies & exposed data.
  • Sign-in & account protectionReview of your visible sign-in safeguards.
  • Your security findings reportEvidence, priorities & remediation guidance.