Hello,
This comment was left by a Forum Volunteer. It is NOT the official response of OVO.
Firstly, please try to format your posts properly into paragraphs. Giant walls of text are annoying and painful for others to read, so please try to make it easier for other folks in future.
I think you really, really need to lower and manage your own expectations here tbh. You’re asking too much of the wrong team to do the wrong thing.
If you actually read the Privacy Policy properly, you would have not only found an email address - dataprotection@ovoenergy.com - AND a postal address - OVO Energy, 1 Rivergate, Temple Quay, Bristol, BS1 6ED - AND two web links to a couple of forms. This one to request access to your data and this one to request erasure of your data. Everything else is either self-service or can be done via Support. FWIW, yes call recordings can be requested this way too.
Also, not everything in your account is personal data. OVO is allowed to withhold certain stuff from a GDPR request.
This isn’t the place to be going into details about Data Controllers and Data Processors acting on behalf of a Data Controller. I will refer you back to the ICO for that.
One merely needs to provide a way of getting in touch with the DPO, there’s nothing in the rules about how. And I’m sorry, but if your preferred way is by phone… Good luck with that. Most large companies don’t allow you to phone the DPO directly. And besides, 99% of the time they need to have a written record of the request - verbal often isn’t enough. This is exactly why there’s no phone number (other than the ICO one) in the “how to contact us” section of OVO’s Privacy Policy.
Sorry, but this feels like an issue with your expectations vs reality if I’m being honest.
In my personal view, I’d probably also advise against trying to tell others here on the Forum about how GDPR stuff works unless you fully understand it yourself. This is just a request from me, but it helps to prevent difficult situations from arising as a result of bad advice. Only the Forum Volunteers and Forum Moderators know the full story about how the SSE to OVO Migration worked and I can tell you now that OVO took a total backup of all the old systems before pulling the plug on them. In addition, wiping the old data off of SSE systems merely one month after migrating a customer would have caused its own problems, such as not being able to resolve read disputes or historical billing issues. That data needs to be held for up to six years post-migration. Only then can it be deleted - and most likely will.
Migrations never lose data when done correctly. Rather than move the original data, you make a copy of it, move that copy over, verify it and only after the migration has been totally verified as complete do you actually proceed to delete the old copy. If something went wrong, you can just go back and grab the missing stuff from the original copy.
One does not become a GDPR expert simply by reading the ICO website for a few days and calling the ICO once or twice. It took me several months of research to gain the knowledge I have. Given my IT and Cybersecurity backgrounds, I’m also trained on GDPR matters - I have to know it as part of my job.