Skip to main content
Vendor Management

Know which vendors hold your users' data, and on what terms

Build a register of processors and partners, link each one to the processing activities it supports, and keep its contract, risk tier and review date in one place.

You stay responsible for what your vendors do

Under Section 8 of the Digital Personal Data Protection Act, 2023 a Data Fiduciary remains responsible for personal data processed on its behalf, and may engage a Data Processor only under a valid contract. If your payment gateway, CRM or delivery partner mishandles data, the obligation is still yours.

Most companies cannot say, without a week of emails, which vendors receive personal data, whether the data leaves India, or whether a signed data processing agreement exists for each one.

What the Vendor Management module does

  • Vendor register

    Record each vendor's role as processor or fiduciary, its category, where data is stored, backed up and supported from, and whether it is a critical service.

  • Start from what you already use

    Add vendors from your cookie scan results, from a built-in library of common services such as AWS, Google Cloud, Razorpay and Zoho CRM, by CSV import or by hand.

  • Mapped to processing activities

    Link each vendor to the activities it supports and the data categories it receives, including whether children's data is involved.

  • Automatic risk tier

    Vendors are tiered High, Medium or Low from four factors: high-impact data, more than 10,000 people, data leaving India and critical service. Children's data is always High. You can override a tier with a reason.

  • Contracts and key clauses

    Upload the DPA or other agreement and record the clauses that matter: breach notice period, sub-processor approval, deletion on termination, audit rights and location limits. Contracts expiring within 60 days are flagged.

  • Reviews and export

    Record each assessment and see the next review date in the register. Export the full register as PDF or CSV for an audit.

How it works

  1. Add your vendors

    Start with the vendors the cookie scanner already detected, then add the rest from the library, a CSV file or manually.

  2. Map them to your activities

    Say which processing activities each vendor supports and what data it receives. The risk tier is calculated from this.

  3. Attach the contracts

    Upload each agreement and note its key clauses. The register shows which vendors have no contract on file.

  4. Review on schedule

    Record an assessment for each vendor and work from the "needs attention" list as review dates and contract expiries approach.

Questions teams ask

Does Consently send security questionnaires to vendors?

No. An assessment in Consently records your review of the evidence a vendor publishes, such as its certifications and policies, and sets the next review date. It does not send or score questionnaires.

How is the risk tier decided?

From four factors: whether the vendor handles high-impact data, whether more than 10,000 people are involved, whether data leaves India, and whether the service is critical. Two or more factors is High, one is Medium, none is Low. Any vendor receiving children's data is High.

How does this connect to rights requests?

When you answer an access request, you can include a section listing who the person's data has been shared with, drawn from the vendor register.

Who in our company can see the vendor register?

Account owners and admins. Vendor contact details are stored encrypted.

Get your vendor register out of email

Book a demo and build the first ten vendors with us.