Websites and Tech

GDPR Compliance Features

Also called GDPR features, data protection features

The working capabilities a site or tool needs to honour consent, export a person's data and delete it on request.

Quick facts: GDPR Compliance Features

Category
Websites and Tech
Also called
GDPR features, data protection features
Level
Intermediate
Affects
Analytics completeness, email list quality, procurement, legal risk
Where to see it
Consent management platforms, WordPress export and erase tools, CRM data request tools, GA4 data retention settings
In this article4
  1. How GDPR compliance features work
  2. Why GDPR compliance features matter
  3. Where GDPR compliance features go wrong
  4. What to do about it

How GDPR compliance features work

The phrase covers the practical capabilities a website, CRM or email tool needs so that the rights the regulation gives people can actually be exercised. Three of them do most of the work. Consent capture asks permission before non-essential tracking or marketing runs, and records what was agreed, when, and against which wording. Data export produces everything held about one named person on request, from every system, not just the obvious one. Data deletion removes it, and keeps it removed in backups and connected tools.

Around those sit the supporting pieces: a retention setting so records expire instead of accumulating for ever, a privacy notice that matches what the site actually does, a list of the processors your data passes through, and a route for someone to make a request and get an answer inside the deadline the law sets. The regulation applies to people located in the EU and UK, so a business in Kathmandu selling to London or Berlin is in scope regardless of where its servers sit.

Why GDPR compliance features matter

They decide what your marketing data is worth. An email list built without a recorded lawful basis is a list you cannot safely use, and a CRM full of contacts nobody can trace the origin of is a liability rather than an asset. Consent capture also changes what your analytics sees, because declined tracking produces genuine gaps in reporting that no tool can quietly fill.

There is a commercial reason as well as a legal one. Larger clients, particularly in the UK, Australia and the EU, ask about this during procurement, and a supplier who cannot answer where the data lives or how it is deleted loses the work before price is discussed.

Where GDPR compliance features go wrong

The biggest error is treating a plugin as the whole job. A badge in a footer, or a banner installed and forgotten, is not compliance; the regulation asks about behaviour and records, and no piece of software can supply those on your behalf. A consent panel that displays but does not actually hold the tags back is the clearest version of this — the choice is collected and then ignored.

The other frequent failure is scope. Export and deletion are tested on the website and nowhere else, so the same person’s details stay in the email platform, the spreadsheet a salesperson keeps, and the ad platform’s uploaded customer list. Retention is left switched off, so records that had a clear purpose years ago are still sitting there with none.

What to do about it

Start by writing down what you collect, where it goes, and why. Most sites collect more than the owner expects, and the fastest improvement is usually deleting fields nobody has ever used. Then check that consent is recorded rather than assumed, and that consent management actually gates the tags it claims to gate.

Run one export and one deletion as a rehearsal, across every system, before a real request arrives — that is where the gaps show. Set a data retention period and let old records expire on their own. If tracking is involved, make sure the measurement setup and the consent setup were designed together rather than bolted to each other, which is the point of treating analytics and tracking as one piece of work.

Do and do not

Do

  • Record what was consented to, when and where
  • Rehearse an export and a deletion across every system
  • Set a retention period and let old records expire

Do not

  • Treat a plugin or a footer badge as compliance
  • Fire tracking tags before a choice is recorded
  • Collect fields you have no stated use for

Questions people ask about this

Does GDPR apply to a business based in Nepal?

It can. The regulation follows the person, not the company, so it applies when you offer goods or services to people in the EU or UK, or monitor their behaviour. A Kathmandu business selling only to Nepali customers is generally outside it, while one running ads into the UK or handling European enquiries is not. The location of your servers does not decide the question.

Is a consent banner enough on its own?

No. A banner is the visible part of consent, but compliance depends on what happens behind it: tags held back until a choice is made, the choice stored so you can show what was agreed, and a way for someone to change their mind later. A banner that appears while the tracking scripts load anyway collects an answer and then ignores it.

How do I handle a request to delete someone's data?

Find every place their details sit, not just the website database. That usually means the CRM, the email platform, any uploaded customer lists in ad accounts, support tickets and exported spreadsheets. Remove the record in each, confirm to the person that it is done, and keep a note that the request was handled. Rehearsing the process once makes the real request far quicker.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.