Nigel Wilkinson
Managing Director of Daneswood. Nigel has been in sales and marketing since the 1980's and run digital marketing agencies since 2000.
There has been a significant change to the way GDPR complaints are handled, and it’s something every business should be aware of.
Back in June, the Information Commissioner’s Office (ICO) updated its guidance around complaints. The reason for the change is fairly straightforward. The ICO was receiving a huge volume of relatively minor complaints, which made it more difficult for them to focus on larger and more serious data protection issues.
As a result, the expectation now is that people should raise their concerns directly with the organisation involved before taking the complaint to the ICO.
What Does This Mean for Businesses?
If someone believes your business has breached GDPR, they should now be able to contact you directly and give you the opportunity to resolve the issue before escalating it to the ICO.
In practical terms, this means you need to have a clear process in place and explain it within your privacy policy.
For example, if you send a marketing email and somebody believes you’ve handled their data incorrectly, they need to know exactly how they can make a complaint to your business.
Changes Required to Your Privacy Policy
The good news is that the changes required on your website are relatively simple.
Your privacy policy should clearly state:
- Who a complaint should be made to
- How someone can submit a complaint
- That you will respond within 30 days
- What steps you will take to investigate and resolve the complaint
- That the individual can still contact the ICO if they are unhappy with the outcome
For most businesses, updating the privacy policy itself is not particularly difficult.
The Bigger Challenge Is Behind the Scenes:
Where things become a little more involved is within your internal processes.
It’s not enough to simply add a few paragraphs to your privacy policy and consider the job done. You also need documented procedures to ensure complaints are handled consistently and correctly.
Your GDPR documentation, operations manual, and standard operating procedures should clearly define:
- Where complaints will be received
- Which email address or contact method will be used
- Who is responsible for managing complaints
- How quickly responses will be issued
- What information should be included in communications
- The process for investigating and resolving issues
- How records of complaints will be maintained
If a complaint is received, your team should know exactly what happens next and who owns the process.
The reality is that GDPR compliance is now both a front-end and back-end requirement.
On the front end, your privacy policy needs to explain how complaints can be made.
Behind the scenes, you need a documented process that demonstrates your business is capable of handling those complaints appropriately and within the required timeframe.
Failing to update your procedures could leave your business exposed, even if your website documentation has been updated correctly.
What Our Clients Need to Do
For clients who have our GDPR package as part of their hosting service, we’re already dealing with the website-side changes and ensuring the necessary updates are made to privacy policies.
What those businesses still need to focus on is their internal documentation.
The important question to ask is: If a GDPR complaint arrived today, would your team know exactly what to do with it?
If the answer is no, now is the time to update your operational procedures, assign ownership, and document the process properly. That way, you’ll be complying not only with the wording on your website but also with the latest expectations from the ICO.
Need help reviewing your GDPR documentation or updating your privacy policy? Get in touch, and we’ll help ensure both your website and your internal procedures are aligned with the latest ICO guidance.