SYSTEM MAPPING DPDPA Compliance

Every system. Every connection. One map.

See your whole systems landscape, internal, SaaS, vendor-run and external, and the personal data that flows between them.

Atlas keeps an inventory of every system, how each one connects to the others, the data attributes it collects and the purposes it collects them for. For vendor systems, you can see at a glance whether the risk assessment and data processing agreement are in place and up to date.

System inventory · Connections and data flows · Attributes and purposes · Vendor DPAs and risk assessments

Your systems landscape, on one page.

Which systems hold personal data, who runs them, what they collect, why, and where it goes next. Atlas keeps the answer in one place.

Every system, in one register

Record each system with its owner, type and description, whether you build it, rent it as SaaS, a vendor runs it for you or it belongs to a partner outside your organisation.

Demo data · RA = risk assessment

Every attribute, tied to a purpose

Each system lists the data attributes it collects and the purposes each one serves.

Every kind of system

Built in-house, rented, run by a vendor or owned by a partner.

750+

Connectors ready

Including Salesforce, SAP and Darwinbox.

Vendor systems, kept in check

Every vendor-run system shows whether its data processing agreement is signed and its risk assessment is current. Vendors get automatic reminders before certificates expire.

Orphaned data, flagged

Attributes no purpose justifies, ready for minimisation.

Import in bulk

Load systems from a simple template instead of retyping them.

01INVENTORY

Know every system that touches personal data

One register for internal, SaaS, vendor-run and external systems.

Most organisations cannot list every system that holds customer or employee data, let alone who owns each one. Atlas gives you a single inventory: each system with its description, business owner, department, type and where it is hosted. It becomes the starting point for every other DPDP Act control, from notices and consent to rights requests and breach response.

02CONNECT

See how your systems connect

The big picture of your systems landscape, and the data moving through it.

Record where each system gets its data from and where it sends it next. Atlas draws those links into one view of your landscape, so you can follow personal data from the web form that collects it, through the systems that process it, to the vendors and partners that receive it. When someone asks where a customer's data goes, you can show them.

03VENDORS

No vendor system without a signed DPA

Risk assessments and data processing agreements, kept up to date.

Under the DPDP Act, you stay responsible for what your processors do with your data. Every vendor-run system in Atlas is linked to its vendor risk assessment and data processing agreement, so you can see at a glance which are signed, current or overdue. Add certificate expiry dates and vendors receive automatic reminders to upload renewed certificates before they lapse.

04ATTRIBUTES

Know what each system collects

An inventory of personal data attributes, system by system.

For every system, list the personal data attributes it collects, stores or shares: name, mobile number, PAN, salary, health details and the rest. System owners can declare them, and Atlas Data Discovery scans confirm what is actually there, so the inventory reflects reality rather than memory.

05PURPOSES

Every attribute, mapped to why you hold it

Purposes that drive your notices, consent and records of processing.

Map each data attribute to the purposes it is collected for, such as account servicing, credit checks or marketing. Those purposes flow into your consent notices and records of processing, so what you tell customers matches what your systems actually do. Attributes with no purpose behind them are flagged, giving you a concrete list for data minimisation.

06POLICIES

Apply minimisation and retention where the data lives

Policies set per system and attribute, not in a document nobody reads.

Set how long each attribute may be kept, when it must be erased once its purpose is over, and what each system should no longer collect. Because policies sit against the systems and attributes themselves, owners can see exactly what applies to them, and your API integrations can act on them in the systems that hold the data.

07SHARING

Answer who you shared data with

Every recipient, location and transfer, on record.

Under Section 11 of the DPDP Act, a Data Principal can ask how their data was processed and who it was shared with. With system connections, hosting locations and recipients recorded, including transfers outside India, your records of processing hold the answer. You reply from evidence, not from a round of emails to every department.

08VERIFY

Check the map against what is really there

Discovery scans that confirm, correct and extend your system map.

A map built from interviews is only as good as people's memory. Atlas Data Discovery scans connected systems for personal data and shows where findings differ from what owners declared: an attribute nobody listed, or data held without a matching purpose. Shadow systems that were never registered can be scanned too, as long as Atlas can connect to them.

09ONBOARD

Build the map without months of spreadsheets

Bulk import, ready connectors and hands-on help when you need it.

Load systems in bulk from a simple template, one file per system, instead of keying them in. Over 750 connectors, including Salesforce, SAP and Darwinbox, link Atlas to your applications. And because mapping means time with busy system owners, our team can sit with them and complete it for you as an optional, one-time assisted data mapping service.

From a list of systems to a living map in four steps

  1. 01

    List

    Add every system with its owner, type and hosting, by hand, by bulk import or with our team.

  2. 02

    Connect

    Record where each system gets data from and sends it to, internal or external.

  3. 03

    Describe

    Map each system's data attributes to purposes and policies, and confirm them with discovery scans.

  4. 04

    Govern

    Keep vendor DPAs and risk assessments current, and keep the map up to date as systems change.

Can you name every system that holds your customers' data?

See how Atlas maps your systems, their connections and the data they hold. We will walk you through a systems landscape like your own in a 30 minute demo.

The free gap assessment covers a single department or division.

Frequently Asked Questions

Everything you need to know about mapping your systems on Atlas.

Ask us anything
GETTING STARTED
What is system mapping in Atlas?

An inventory of every system that handles personal data, how each one connects to other systems, the data attributes it collects and the purposes it collects them for. Together they give you a big-picture view of your systems landscape.

Why do we need it for the DPDP Act?

You cannot give accurate notices, honour consent, answer rights requests or respond to a breach without knowing which systems hold personal data and where it flows. Data Principals can also ask how their data was processed and who it was shared with, and your system map is how you answer.

Which kinds of systems can we map?

Internal systems you build or host, SaaS applications, systems run for you by vendors and external systems owned by partners such as credit bureaus or payment providers.

How long does mapping take?

It depends on how many systems you have and how available their owners are. You can import systems in bulk from a template, connect applications through our connectors, and use our optional assisted data mapping service, where our team works directly with your system owners.

DATA, PURPOSES AND POLICIES
What do we record for each system?

Its description, owner, department, type and hosting location, the systems it receives data from and sends data to, the personal data attributes it holds, and the purposes and policies that apply to each attribute.

How do purposes link to consent?

Each attribute is mapped to the purposes it serves. Those purposes feed your consent notices and records of processing, so what you tell people matches what your systems actually do.

What happens to data with no purpose?

Atlas flags attributes that no purpose justifies. That gives you a concrete list of data to stop collecting or erase, which supports data minimisation under the DPDP Act.

Does the map stay accurate over time?

Atlas Data Discovery scans connected systems and highlights personal data that owners did not declare, so you can correct the map. Shadow systems that were never registered can be scanned too, if Atlas can connect to them.

VENDORS AND DEPLOYMENT
How does Atlas handle vendor systems?

Each vendor-run system is linked to its vendor risk assessment and data processing agreement, so you can see which are signed, current or overdue. Vendors get automatic reminders to upload renewed certificates before they expire.

Can we record transfers outside India?

Yes. Hosting locations and recipients are recorded for each system, and cross-border transfers are captured in your records of processing.

Which systems can Atlas connect to?

Over 750 connectors are available, including Salesforce, SAP and Darwinbox. Some systems need small changes on their side, such as fields to store consent preferences.

Where can Atlas be deployed?

In the FRS Labs cloud as SaaS, in your own AWS or Azure account, or on your own servers.

Trusted by 250+ customers worldwide

TTK Duruva Ujjivan Jana UIDAI Equitas Yes Bank