Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Personal data inventory. GDPR Article 30.

Check your record of processing against the data your systems hold.

A source-linked record of what you hold, where it sits and why you keep it, that refreshes instead of going stale.

Four paid engagements and three proofs of concept.

The challenge

Why the record and the data drift apart

Purpose stays in the application

Dipal Panchal’s example: a contact saved in the CRM should carry its marketing consent ID. “Nobody does this,” he says, and the copy in an analytics table carries none.

Built from what teams describe

When each team describes its systems for the record, a warehouse copy nobody mentions never reaches it, however much personal data it holds.

Accountability means showing it

Article 5(2) asks you to demonstrate compliance, so a record nobody has checked against the systems is a weak exhibit when the regulator asks.

In the product

Article 30(1) item by item, against the data

Records for one processing activity, online orders. Each item shows what the record says, what the systems show and what IRIS produces.

Article 30(1) item by item, against the data
Article 30(1) itemIn the recordWhat the systems showFrom IRIS
(a) Controller and DPO contact detailsExample Retail Ltd; the DPO at dpo@example.comNothing in a data store answers thisNot produced by IRIS
(b) Purposes of the processingOrder fulfillment; order emailsPurpose registry entry linked to crm.person.email and orders.shipping_addressProduces part of this: the link from purpose to columns, where your edition has the registry
(c) Categories of data subjects and personal dataCustomers: name, email, delivery addressFindings add date of birth in orders.customer_profile, which the record doesn’t listProduces part of this: the data categories in connected sources; the data subject categories stay yours
(d) Categories of recipientsPayment processor; delivery partnerNot visible in a data storeNot produced by IRIS
(e) Transfers to third countriesSupport desk in India, under standard contractual clausesNot visible in a data storeNot produced by IRIS: it doesn’t track where data is sent
(f) Time limits for erasureOrder records 6 years; marketing preferences 2 yearsThe retention period you set on each purpose, linked to its columns; IRIS doesn’t compare it with the age of the dataProduces part of this, where your edition has the purpose registry
(g) Security measuresEncryption at rest, as the record states it before any checkProtection check: customer.phone masked, email in plain form; four roles can read crm.personPart: the protection check on sampled values, once activated on your install, and role access from table and view grants
Not an Article 30 itemNothing listedFinding: analytics.marketing_extract.email, a copy with no linked purposeProduces this: a flag on data with no linked purpose, where your edition has the registry
Requirements

What Articles 5(2) and 30 ask of you

Under GDPR Article 5(2), the controller is responsible for compliance with the principles and must be able to demonstrate it. Article 30(1) lists what the record of processing holds, and Article 30(4) has you make it available to the supervisory authority on request.

Article 30(5) exempts organizations under 250 employees, unless the processing is likely to put people’s rights at risk, isn’t occasional, or includes special category or criminal offence data. UK GDPR Article 30 keeps the same article numbers, and its regulator is now the Information Commission.

Our view: check items (b), (c) and (g) against the systems before each review of the record. The other items rest on contracts and decisions that only your team holds, such as the transfer terms behind (e).

What you get

What your privacy team works from

Findings to correct item (c)

Personal data by source and location, so the categories in the record match what the connected systems hold, including the copies.

A record of each rights request

Access, correction and erasure requests each get a record, searched across the connected databases. Any correction or erasure is made by your team, in the source system.

Capabilities

What IRIS adds to the record

One scan feeds both the inventory and the purpose links, in the sources you connect.

Personal data by location

Classifies personal data in connected databases and files across 103 built-in data types for Indian, US and global formats, each finding tied to its source.

Purposes linked to columns

The purpose registry records each purpose with its legal basis and retention period. It links each purpose to its columns, and flags data that has none.

Rights requests searched

A request searches the personal-data locations your stewards confirmed in connected databases, and records which locations it left out and why.

Evidence for item (g)

Checks sampled values for encryption, masking or hashing, once the check is activated on your install, and shows, from table and view grants, which roles can reach the sensitive tables it found.

Capabilities vary by edition.

Overview

Where the record stays with your team

IRIS doesn’t write the record of processing, manage consent or track where data is sent, so items (a), (d) and (e) stay with your team. Consent records remain in the applications that captured them, outside IRIS.

Rights-request search covers connected databases, not files or mailboxes. National ID formats for the UK, the Gulf and EU countries aren’t among the built-in data types.

Frameworks

Privacy law pages

Each page sets out what that law asks of your records and the evidence IRIS produces for it.

For UK GDPR, UAE PDPL and Saudi PDPL, IRIS maps the privacy lead’s evidence to their controls. A scored readiness view for privacy work isn’t in v1; ask us if you need one.

How it works

Check item (c) against one database first

Pick the system your record names for its largest processing activity and scan it, with the copies around it. The how-it-works page follows that scan, and the DSAR page shows the request record and the purpose registry.

FAQ

Questions DPOs ask

Protect your brand. Start with your data.

Bring your record of processing for one activity. We’ll set it against one database you choose.