Skip to main content

ConsentGuard: consent management built for India's DPDP Act

ConsentGuard is FinHub's consent management platform for BFSI. Capture, manage and enforce customer consent across web, mobile, branch, IVR and partner channels, then find, map and assess the personal data behind it, in one console.

  • Purpose-based consent, with notices in 22 Indian languages
  • A customer portal for withdrawals, rights requests and grievances
  • Data Discovery, Data Mapping and DPIA in the same console

See ConsentGuard on FinHub · Book a demo on FinHub

Business person holding a tablet with a security shield icon

Talk to us about ConsentGuard

Four modules

Four modules in one console

Consent & Rights, Data Discovery, Data Mapping and DPIA share the same console, records and roles. Each module has its own page on the FinHub website.

  • Consent & Rights

    Capture purpose-linked consent in 22 Indian languages, give customers a portal to manage it, and resolve every rights request and grievance on the record.

    • Purpose templates
    • 22 languages
    • Customer portal
    • Grievances
    Consent & Rights on FinHub
  • Data Discovery

    Scans databases, file stores and cloud storage such as AWS S3 to show what personal data you hold, and where, with Aadhaar, PAN and account numbers recognised out of the box.

    • Ten connectors
    • Indian identifiers
    • Human review
    Data Discovery on FinHub
  • Data Mapping

    Links each consent to the purpose it serves, the systems that process it and the vendors who receive it, in one logged map.

    • Lineage
    • Third parties
    • Change history
    Data Mapping on FinHub
  • DPIA

    Run Data Protection Impact Assessments and vendor assessments from structured templates, with every answer and decision on one evidence trail.

    • Significant Data Fiduciaries
    • Vendor assessments
    DPIA on FinHub

Customer portal

Customers manage their own consent

After giving consent, a customer gets a secure link by email or SMS to their own Data Principal portal.

  • See every consent

    Every consent they have given, and the purpose it was given for.

  • Withdraw or renew

    Withdraw or renew optional purposes, such as marketing, without calling the branch. Changes are reflected across connected systems.

  • Raise a request

    Raise a rights request or grievance, and track its status.

Regulatory purposes, such as KYC records held under RBI retention rules, stay locked and are clearly marked, so customers understand why.

BFSI journeys

Consent across the lending and banking lifecycle

Separate, purpose-specific consent for each stage, captured inside the journey rather than after it.

  • Digital onboarding

    Capture consent before identity verification, eKYC and account opening.

  • Loan origination

    Consent for credit bureau checks, income verification, underwriting and loan processing.

  • Customer servicing

    Consent for servicing requests, account management and profile updates.

  • Marketing communications

    Separate consent for promotional campaigns across SMS, email, WhatsApp and voice.

  • Cross-sell and telecalling

    Know which customers said yes to cross-sell before a campaign, DSA or telecalling partner touches the list.

  • Collections

    Communication preferences and customer permissions carried through recovery journeys.

For banks, NBFCs, housing finance companies, digital lenders, insurance companies, payment aggregators and gateways, wealth management platforms and stock brokers.

Data Discovery

Find the personal data you hold, and where

Data Discovery scans databases, file stores and cloud storage such as AWS S3, and shows each finding with its category, location and a confidence score. A compliance officer decides what counts as personal data.

  1. Add a read-only credential

    The IT Admin adds a login that can only read. Its secret goes into an encrypted store and is never shown again.

  2. Register the data source

    Test connection reports the server version and latency, or names the fault. A login that can write is refused, with the privilege named.

  3. Build a scan profile

    Choose how many containers to sample and how many records to read in each, manual or scheduled runs, complete or incremental scans, a permitted time window and a maximum run time.

  4. Run the scan

    Results are written one container at a time. One unreadable table does not fail the run; five failures in a row stop it.

  5. Review and confirm

    Nothing reaches the catalogue until a Compliance Officer or Super Admin confirms it, at any confidence. A rejection needs a ground and a reason, and is kept rather than deleted.

  6. Prove it

    Verify the hash-chained audit log's integrity, then export the audit trail or the confirmed catalogue as CSV or PDF for an auditor.

Laptop showing code on a developer's desk
From a read-only login to sign-off

Data Discovery connectors

Ten read-only connectors

Each connector proves at connection time that its login cannot write: a privilege check where the source has one, a write probe where it does not.

  • Structured

    Walks schema, table and column. Incremental scans use change signals the database already keeps.

    • PostgreSQL
    • MySQL
    • Oracle
    • SQL Server
  • Semi-structured

    Collections and indices, held to the same read-only proof.

    • MongoDB
    • Elasticsearch
  • Object storage and file shares

    Delimited files keep their column names and JSON its paths; PDFs and Office documents are read whole, and ZIP and 7z archives are opened.

    • AWS S3 and S3-compatible
    • Azure Blob Storage
    • Google Cloud Storage
    • Mounted filesystem
  • Deep scan (OCR)

    Off by default. When on, it also reads text from scanned PDFs, and from photographs in S3-compatible storage and file shares, on the host itself. Everything it finds goes to review.

    • Photographs
    • scanned PDFs
Banking compliance team reviewing customer data and governance controls
Scored on the value and the field name

Detection

Detection for Indian personal data

Findings are scored on two independent signals, the value and the field name, so a customer_ref column holding twelve digits does not score like aadhaar_no holding the same.

  • Categories

    Aadhaar, PAN, bank account, IFSC, phone, email, name, address, location, gender and date of birth, plus custom categories with your own rules.

  • Validated, not just matched

    Aadhaar numbers are checked with the Verhoeff checksum, and IFSC codes against a registry of real bank prefixes.

  • Fixed confidence tiers

    Verified (95 and above), High (80 to 94), Needs review (50 to 79) and Low (below 50), the same on every install.

  • Review lanes

    Open findings wait in three lanes: likely personal data, needs your judgment, and weak signals, which are parked and counted rather than hidden.

  • Decide a pattern once

    One column across monthly partitions, or one field across a folder of documents, can be confirmed or rejected as one decision.

  • Bulk confirm with a floor

    Bulk confirmation refuses any threshold below 50, so a finding below 50 can only be confirmed one at a time.

Rows of server racks with blue cabling in a data center aisle
Installed next to your data

Data Discovery deployment

Data Discovery runs inside your network

ConsentGuard Scan, the Data Discovery module, ships as a self-contained, single-tenant install. It needs Docker and a host that can reach your data sources, and no internet access, managed cloud service or Kubernetes.

  • No internet at runtime

    Nothing is downloaded at runtime, including detection models, and OCR runs on the host itself.

  • Masked before it is stored

    Sample values are masked before they are written, so the database never holds a raw personal data value for a screen, an API call or a dump to expose.

  • No secrets in the database

    Data source credentials are encrypted with AES-256-GCM outside the database, which holds only a reference.

  • Single sign-on that works air-gapped

    SAML 2.0 sign-in through your identity provider never needs the install to call it. It has been tested with Entra ID and Keycloak.

  • Runners for segmented networks

    Where a source sits on a network the install cannot reach, a runner deployed next to it scans there and sends home only masked findings.

  • Bounded load on production

    Per-source connection caps, permitted time windows and a hard maximum run time keep scans predictable on production systems.

Data Mapping and DPIA

Map where data goes, and assess the risk

Data Mapping starts from what Data Discovery found, and DPIA assesses processing using the flows already documented in Data Mapping.

One map from consent to every downstream system

Data Mapping links each consent to the purpose it serves, the systems that process it and the vendors who receive it.

  • Lineage from the consent, through each purpose, to every system that uses the data
  • Which systems process data for KYC, bureau checks, servicing or marketing, and which fields each pulls
  • The credit bureaus, DSAs, collection agencies and partners that receive customer data
  • Every change to a map is logged
Data Mapping on FinHub
Two people pointing at a laptop screen together
Consent-to-system lineage

Keep exploring

More on protecting BFSI data

  • Data protection and governance

    Aadhaar masking and data governance for banks and NBFCs.

    Data protection
  • BFSI document governance

    A free assessment that maps your documents against DPDP Rule 6 and RBI expectations, with a written gap list.

    Document governance
  • Aadhaar Masking

    Masks Aadhaar numbers and QR codes in KYC and loan files, as an API, in your AWS account or on your own servers.

    Aadhaar Masking
  • Audit Management System

    Configurable audits for BFSI, from schedule to sign-off, with an activity log of who did what and when.

    Audit Management System
  • FinHub

    KYC, KYB and verification APIs for banks and NBFCs behind one integration.

    FinHub
  • DocuSwift

    A serverless document management system on AWS for lenders, with an immutable audit trail.

    DocuSwift

Questions

ConsentGuard questions

ConsentGuard is FinHub's consent management platform for BFSI. It captures, manages and enforces customer consent across digital and offline channels, and its Data Discovery, Data Mapping and DPIA modules find, map and assess the personal data behind that consent.

It enables purpose-based consent collection, consent validation, withdrawal management and audit-ready record keeping, helping organisations build DPDP-ready consent workflows.

Yes. Customers can review, update or withdraw consent through self-service preference management, and changes are reflected across connected systems. Regulatory purposes, such as KYC records held under RBI retention rules, stay locked and are marked as such.

All 22 languages of the Eighth Schedule. You can write your own translation or auto-translate each notice and purpose.

Yes. ConsentGuard provides APIs that integrate with onboarding platforms, CRMs, LOS, DMS, customer portals and internal business applications, and consent can be embedded in web, mobile and assisted journeys with a lightweight script.

PostgreSQL, MySQL, Oracle and SQL Server; MongoDB and Elasticsearch; AWS S3 and other S3-compatible storage, Azure Blob Storage and Google Cloud Storage; and mounted file shares.

No. Every connector proves its login cannot write before it reads anything, and a login that can write is refused. On object stores and file shares the proof is a probe written to a reserved name; if the write succeeds, the source is refused and the probe removed where the login allows it. Sample values are masked before they are stored, and exports record where personal data lives, never what it says.

With deep scan on, it reads text from scanned PDFs, and from photographs in S3-compatible storage and file shares, on the host itself. Azure Blob Storage and Google Cloud Storage read a photograph's metadata only. Everything OCR finds goes to review, and an empty result on a scan means not found, not that nothing is there.

No. It runs inside your network as a single-tenant install on Docker, with no internet access, managed cloud service or Kubernetes.

Next step

Bring ConsentGuard into your consent journeys

Book a demo through FinHub, read about each module on the FinHub website, or tell our team which journeys and systems you want to cover first.

  • Consent & Rights, Data Discovery, Data Mapping and DPIA
  • Notices in 22 Indian languages
  • Human sign-off before anything is catalogued