The UK GDPR sets out seven principles for handling personal data. The fourth is accuracy: personal data must be accurate and, where necessary, kept up to date, and inaccurate data must be erased or corrected without delay. For most organisations the data this bites on first is the plainest: names, addresses, phone numbers and email addresses.
This is a practical overview, not legal advice. The Information Commissioner's Office (ICO) publishes the authoritative guidance.
What the principle says
In summary, you should:
- take reasonable steps to make sure the personal data you hold is not incorrect or misleading
- keep it up to date where that is necessary for what you use it for
- correct or erase it promptly when you find it is wrong
- consider any challenge to its accuracy
"Where necessary" depends on what the data is for
You do not have to update everything for ever. The question is whether out-of-date data would matter for your purpose.
- A record of where an order was delivered in 2023 is accurate as a historical record. It does not need changing when the customer moves.
- The address you send statements to is used today. If it is out of date, personal and financial information goes to the wrong household.
Contact details used for ongoing communication nearly always fall in the second group.
What counts as "reasonable steps"?
It scales with the risk. The more harm an error could cause, the more you are expected to do. Reasonable steps for contact data commonly include:
- Recording where the data came from and when it was last confirmed.
- Making it easy for people to update their own details , online and without a phone call.
- Prompting people to review their details periodically, and before anything sensitive is posted.
- Acting on evidence that data is wrong: returned post, bounced email, a failed delivery or a text answered by a stranger.
- Not repeating the error: when one system is corrected, the others that hold a copy are corrected too.
Doing nothing until a customer complains is hard to defend where you are sending anything confidential.
The right to rectification
Individuals have the right to have inaccurate personal data corrected. When someone asks:
- you must respond within one month , which can be extended for complex requests
- you cannot normally charge a fee
- if you have shared the data with others, you should tell them about the correction where possible
- the request can be made verbally or in writing, to any part of your organisation
A change of address is the commonest rectification request there is, even though nobody calls it that. Your process for it should be quick and should reach every system.
When wrong contact data becomes a breach
Sending personal data to an old address or a recycled phone number can be a personal data breach: an unauthorised disclosure. Depending on the risk to the person, you may need to report it to the ICO within 72 hours and tell the individual. A bank statement, a medical appointment letter or a payslip reaching the wrong household is exactly the kind of incident that gets reported.
Keeping contact details accurate is therefore also part of keeping data secure.
Ways to reduce the risk
Our guide to keeping customer addresses up to date compares the options, from review prompts to mover files. In short:
- Validate details when they are captured.
- Give customers a simple way to change them.
- Treat bounces and returns as signals and act on them.
- Keep one source of truth, so a correction reaches every system.
- Where you can, get changes from the individual as they happen.
Where ContaShare fits
ContaShare supports the fifth point. Your customers keep their own address, phone number, email and name current in a ContaShare account, and choose which of them your organisation may read. You read the current version through an API and receive a notification when something changes.
For accuracy, that means the data comes from the individual, with a record of their permission, and corrections arrive without your asking. It covers the customers who connect their account, not your whole database, so it sits alongside the other steps and does not replace them. You remain the controller of the data you hold and responsible for your own compliance.
Top comments (0)