ConsentGuard · Data Mapping
ConsentGuard Data Mapping links each consent to the purpose it serves, the systems that process it and the vendors who receive it. One visual, logged map in place of spreadsheets no one trusts.
- Consent-to-system lineage
- Change history on record
- Built for audits
Trusted Across Indian BFSI
Banks, NBFCs, housing finance companies and co-operative banks run verification, Aadhaar masking and document workflows on FinHub, inside their own compliance and audit requirements.
Prüfens Advisory
The Challenge
"Where Did My Data Go?" Needs a Better Answer Than a Spreadsheet
Under DPDP, customers can ask for a summary of how their data is processed and who it was shared with. Answering that from spreadsheets and email threads is slow and hard to defend.
Flows live in people's heads. Data moves from onboarding to LOS, LMS, bureau and collections, but no single view shows it.
Spreadsheets go stale. A data flow register updated once a year can't reflect a vendor added last month.
Purpose drift goes unseen. Data collected for KYC quietly ends up in a marketing list.
Audits turn into reconstruction. Teams rebuild history from emails because changes were never logged.
Capabilities
One Map From Consent to Every Downstream System
Visual Data Lineage
Follow customer data from the consent it was collected under, through each purpose, to every system that uses it.
Purpose-to-System Links
See which systems process data for KYC, bureau checks, servicing or marketing, and which data fields each one pulls.
Third-Party Visibility
Record the credit bureaus, DSAs, collection agencies and partners that receive customer data.
Data Element Detail
Track exactly which fields move, such as Aadhaar number, PAN, CIBIL score, mobile and email.
Change History on Record
Every change to a map is logged, so you can show what was processed where, and when.
Feeds From Discovery
Start from what Data Discovery found, not from a blank sheet.
How it works
Map It Once. Keep It Current.
Start From Consent
Pull in consent templates and purposes from Consent & Rights.
BFSI Use Cases
Built for Lending and Banking Data Flows
Loan Lifecycle Mapping
Trace a borrower's data from application to LOS, bureau, disbursal, LMS and collections.
Bureau & Partner Sharing
Show exactly what goes to credit bureaus, co-lending partners and DSAs, and under which purpose.
Access Request Responses
Answer a customer's "who has my data" request from the map, not from a manual hunt.
Purpose Change Control
Catch the moment data starts moving to a new system or purpose, before an auditor does.
Who It's For
The Teams That Live With This Every Day
DPOs & Compliance Teams
A living record of processing you can show on demand.
Enterprise Architects
A clear view of how personal data crosses your application landscape.
Vendor & Partnership Teams
Know which partners receive customer data and why.
Internal & External Auditors
A logged trail of what changed and when.
Why FinHub
Why FinHub
Consent Is the Anchor
Every map starts from the consent and purpose behind it, not from a system list.
Speaks BFSI
LOS, LMS, bureaus, DSAs and collections are first-class, not custom fields.
Logged by Default
Changes can't quietly overwrite history.
One Console
Discovery, Mapping, Consent and DPIA share the same records and roles.
FAQ
Data Mapping, Common Questions
Data mapping documents how personal data is collected, which purposes it serves, which systems process it and who it is shared with. It is the evidence behind most DPDP obligations.
Across ConsentGuard
A Map Is Only as Good as What Feeds It
Replace the Spreadsheet With a Map You Can Defend
Show auditors, the Board and your customers exactly where data goes, and why, from one logged view.