When a company says "we are fine with the GDPR", it usually means there is a notice on the website and a document signed by the consultant. A privacy assessment is for checking whether what is written is also what happens: where the personal data really is, who processes it, how long they keep it and what they would do if some of it leaked tomorrow.
The scope
The assessment applies whenever a project touches the processing of personal data, data subject rights, transfers outside the Union or the obligations arising from Regulation (EU) 2016/679 or equivalent frameworks (for example Brazil's LGPD or California's CCPA). It does not replace legal advice: it gathers the facts on which a lawyer or the DPO can give an opinion.
The five things to look at
- The record of processing activities (RoPA). Does it exist, is it up to date, does it cover the main processing? A record that has stood still for over a year describes a company that changed tools without changing documents.
- Legal bases and consent. For each processing activity, what basis it rests on. Where there is consent: how it is collected, how it is withdrawn, where the proof of it is kept.
- The impact assessment (DPIA). Has it been done for high-risk processing?
- Data subject rights. How requests for access, erasure and portability arrive and are tracked, and how quickly they are answered.
- Breaches (data breach). Is there a documented procedure to notify the supervisory authority within 72 hours of discovery, as Article 33 of the Regulation provides?
The questions change with the interlocutor
DPO, legal, compliance. Is the record kept up to date? Which legal bases are used for each processing activity? How is consent collected and withdrawn? Who decides that a DPIA is needed? Who keeps the register of data subject requests?
Technical staff (IT, security). Where is personal data stored, is there an inventory or a map of flows? How is minimisation applied to collection and retention? What encryption and pseudonymisation controls are there? Are retention periods configured and is deletion or anonymisation automatic? How are suppliers that process data (cloud, SaaS) assessed and contracted?
Business leads. Do marketing and analytics tools collect personal data? Is the cookie banner configured correctly? Are employees trained? Have there been breaches or near-breaches in the last year?
The evidence to ask for
- an extract of the record of processing for the main activities;
- the configuration of the consent management platform or the outcome of a cookie audit;
- the data processing agreements (DPAs) with the main processors;
- the DPIAs already produced;
- the register of data subject requests for the last twelve months;
- the breach register and the response procedures;
- the retention policy and proof that the automatic deletions run.
The warning signs
- Record absent or not updated for over a year.
- Data kept beyond the declared period.
- No DPA signed with suppliers that process personal data.
- Consent collected without a valid legal basis or without retained proof.
- No documented breach procedure.
- Flows to third countries without adequate safeguards (standard contractual clauses, adequacy decision).
How to read the result
Three rules of reading help avoid producing an undifferentiated list of "non-conformities".
Weigh by risk of sanction, not by technical severity. An unencrypted database in a test environment with no real data is less worrying than consent collected without proof on a marketing customer base.
Distinguish controller and processor. When several parties take part in the processing, the obligations are different. A finding attributed to the wrong party will never be closed.
Cross-check technical facts and documents. Archives, logs and configurations say what happens; the documentation says what the company believes happens. The differences between the two are the real findings.
An example
A services company states in its record that it keeps candidates' data for six months. From the conversation with IT it emerges that the selection system has no deletion job and has kept everything since it was installed. The finding is not "a policy is missing": the policy exists. It is that the declared retention and the real one diverge, and that the proof of deletion does not exist.
For whoever writes it
The report must say clearly what is a verified fact, what is declared by the interlocutor and what is an assessment to be confirmed with the DPO or a lawyer. The skill at the end brings this knowledge in a form an agent can use, with or without interviews.
This article is an OIAR skill
What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.
data-privacy-complianceKnowledge for assessing an organisation's privacy compliance (GDPR and similar frameworks): record of processing, legal bases, DPIA, data subject rights, breaches, external processors. Use it when the user asks for a GDPR assessment, a check of processing activities or the reading of privacy documents, with or without interviews.