Cookie settings

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

Skip to content
Skip to content

DSAR tracking. Purpose registry.

Track each data subject request, from search to versioned response.

IRIS logs access, correction and erasure requests and searches connected databases for the person. Your team makes the change in the source system.

One request’s search record

A data subject request from Example Subject to see their data, received November 2, 2026 and looked up by email address. Each location shows its reason.

Records
SourceStatusReasonOwner
CRM database: crm.personSearched: 1 record foundMatched on the email addressCRM application owner
Core banking database: cbs.customer_masterSearched: 1 record foundMatched on the email address; the customer number links the cards recordCore banking DBA
Cards database: cards.card_customerSearched: 1 record foundMatched through the linked customer numberCards platform owner
Loans archive databaseExcludedUnder legal hold: loan records kept for the period the law sets, noted on the requestLending platform owner
Marketing analytics databaseExcludedNot yet a confirmed personal-data location; listed for the data steward to reviewData steward
HR document libraryNot searchedDSAR search covers connected databases, not filesHR operations lead
Capabilities

What DSAR and purpose cover

A senior leader at a large private bank asked for this module in a demo: his team still handled these requests by hand.

One record per request

Gives each access, correction and erasure request one record, with its outcome, any legal hold and its history.

Search from confirmed locations

Searches the personal-data locations stewards have confirmed in connected databases, by email address, mobile number or PAN.

What was searched, and what wasn’t

Records which locations were searched and which were excluded, with the reason for each, before the search runs.

Approvals, deadlines and owner tasks

Requires the number of approvals you set, runs deadline clocks on your business calendar and sends source owners tasks, including through an external task page.

A response you can version

Produces the response as a PDF and keeps each version, so you can show what was sent and when.

Products a person holds

Lists the products a person holds across their customer numbers, from the columns an administrator maps during setup.

Capabilities vary by edition.

How it works

How a request runs

  1. Log the request

    Record the request type, the person and how their identity was verified.

  2. Search databases

    IRIS searches confirmed personal-data locations and records each exclusion with its reason.

  3. Change at source

    Source owners make any correction or erasure in their own systems, outside IRIS.

  4. Record and close

    Record the outcome, approve the response and close the request. The history stays on the record.

In the product

DSAR and purpose in IRIS

DSAR

Each request, its deadline and its owner

Access, correction and erasure requests each get one record. Approvals need the quorum you set, and deadline clocks follow your business calendar.

  • Phases from receipt to response, each with an owner and a deadline
  • Tasks for source owners, including an external task page
Explore evidence
IRIS data subject request showing its status, the search status, the response deadline and the phases completed so far
One request’s status, its response deadline and the phases completed so far.
Search

Search starts from confirmed locations

Search covers personal-data locations confirmed in connected databases. It looks up the person by email address, mobile number or PAN.

  • Searched and excluded locations recorded, with reasons
  • Lookups by email address, mobile number or PAN
Explore the data catalog
IRIS data explorer listing personal-data patterns such as person name, address, email and mobile number with their context
Browse personal data by pattern across the whole organization, then drill into where it lives.
Questions

Questions a privacy team gets asked

Is each request on time?

Each request has a deadline clock on your business calendar, so the requests coming due show first.

Can we show the regulator what we did?

Each request keeps its search record, its history and every version of the response.

Does DSAR work widen access to data?

Search covers only locations your stewards have confirmed, and a request moves forward only after the approvals you set.

Why do we hold this data?

The purpose registry links each purpose to its data columns, and IRIS flags data with no linked purpose.

Overview

Why you hold it, written down

The purpose registry records each processing purpose with its legal basis, retention period and status, and links it to the data columns it covers. Your DPO fills the legal-basis list in your organization’s own terms.

IRIS then flags data with no linked purpose, and purposes past their retention period, so your privacy team can review the gaps. Consent records stay in the systems that collected them.

To see where DSAR search fits among the steps of a scan, follow one on the how-it-works page.

FAQ

Questions about DSAR and purpose

Protect your brand. Start with your data.

Bring your last three requests. We’ll show you what their record would look like in IRIS.