DSAR info supplied, but I don't understand it

-taff

SO this was a chain of loans that was consolidated ?
It's the last bit on each one that says rebate A that makes me wonder if you did pay it.
Did you pay the last one off early or did it go to term? Did you refinance this loan with another one from someone else?

MarkTDon

Honestly I can't remember, this is all I have, the front page of each one is ineligible. I don't remember why I got these loans, what I did with them or anything tbh. I don't understand loans or ppi, don't think I agreed to ppi as I didn't think I needed it. I just hoped someone would see what I posted and would be able to tell if there was ppi on there or not. Thanks for everyone's time though. Will wait til Monday and ring them.

[Deleted User]

Your SAR information does not explicitly show you paying any PPI. It is inconclusive and therefore useless in any PPI complaint...

MarkTDon

Thanks, which is why I was asking for help in deciphering the images. Didn't understand the code words and couldn't see ppi anywhere. Just thought someone would be able to spot if it was there or not.

[Deleted User]

SARs are not required to explain any "codewords". As I said, your SAR information does not explicitly show you paying any PPI.

It is inconclusive and therefore useless in any PPI complaint...


The end.

Sorry.

Nasqueron

Moneyineptitude wrote: »

SARs are not required to explain any "codewords". As I said, your SAR information does not explicitly show you paying any PPI.

It is inconclusive and therefore useless in any PPI complaint...


The end.

Sorry.

They do actually have to explain codes according to the ICO, but they're a bit vague on whether the data should be changed to make it easier to understand as their advice seems to contradict itself.

Do we have to explain the contents of the information we send to the individual?

The GDPR requires that the information you provide to an individual is in a concise, transparent, intelligible and easily accessible form, using clear and plain language. This will be particularly important where the information is addressed to a child.
At its most basic, this means that the additional information you provide in response to a request (see the ‘Other information’ section above) should be capable of being understood by the average person (or child). However, you are not required to ensure that that the information is provided in a form that can be understood by the particular individual making the request.


Example
An individual makes a request for their personal data. When preparing the response, you notice that a lot of it is in coded form. For example, attendance at a particular training session is logged as “A”, while non-attendance at a similar event is logged as “M”. Also, some of the information is in the form of handwritten notes that are difficult to read. Without access to your key or index to explain this information, it would be impossible for anyone outside your organisation to understand. In this case, you are required to explain the meaning of the coded information. However, although it is good practice to do so, you are not required to decipher the poorly written notes, as the GDPR does not require you to make information legible.

linky

[Deleted User]

Nasqueron wrote: »

They do actually have to explain codes

Regardless of any codewords, that SAR doesn't show any PPI.

Nasqueron

Moneyineptitude wrote: »

Regardless of any codewords, that SAR doesn't show any PPI.

Doesn't show anything at all beyond payments, OP needs to read the agreement they sent or ring up today and just ask, probably should have done that before sending the SAR to be honest