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.
Personal data inventory. GDPR Article 30.
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.
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.
When each team describes its systems for the record, a warehouse copy nobody mentions never reaches it, however much personal data it holds.
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.
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 | In the record | What the systems show | From IRIS |
|---|---|---|---|
| (a) Controller and DPO contact details | Example Retail Ltd; the DPO at dpo@example.com | Nothing in a data store answers this | Not produced by IRIS |
| (b) Purposes of the processing | Order fulfillment; order emails | Purpose registry entry linked to crm.person.email and orders.shipping_address | Produces part of this: the link from purpose to columns, where your edition has the registry |
| (c) Categories of data subjects and personal data | Customers: name, email, delivery address | Findings add date of birth in orders.customer_profile, which the record doesn’t list | Produces part of this: the data categories in connected sources; the data subject categories stay yours |
| (d) Categories of recipients | Payment processor; delivery partner | Not visible in a data store | Not produced by IRIS |
| (e) Transfers to third countries | Support desk in India, under standard contractual clauses | Not visible in a data store | Not produced by IRIS: it doesn’t track where data is sent |
| (f) Time limits for erasure | Order records 6 years; marketing preferences 2 years | The retention period you set on each purpose, linked to its columns; IRIS doesn’t compare it with the age of the data | Produces part of this, where your edition has the purpose registry |
| (g) Security measures | Encryption at rest, as the record states it before any check | Protection check: customer.phone masked, email in plain form; four roles can read crm.person | Part: the protection check on sampled values, once activated on your install, and role access from table and view grants |
| Not an Article 30 item | Nothing listed | Finding: analytics.marketing_extract.email, a copy with no linked purpose | Produces this: a flag on data with no linked purpose, where your edition has the registry |
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).
Personal data by source and location, so the categories in the record match what the connected systems hold, including the copies.
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.
One scan feeds both the inventory and the purpose links, in the sources you connect.
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.
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.
A request searches the personal-data locations your stewards confirmed in connected databases, and records which locations it left out and why.
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.
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.
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.
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.
No. It evidences parts of items (b), (c), (f) and (g) from the systems you connect, as the table shows. Your team keeps the record itself.
No. It doesn’t collect or check consent records, or connect to consent platforms today. Its purpose registry records the legal basis your team assigns.
Yes, where your team has recorded a legal hold on that data in the catalog. The request leaves it out of the erasure task and keeps the hold as the reason, and the held record is still reported.
You can skip it only if three conditions all hold, on the text in force on November 8, 2026. Article 30(5) lifts the duty only if the processing is occasional, unlikely to put people’s rights at risk and free of special category or criminal offence data.
Bring your record of processing for one activity. We’ll set it against one database you choose.