PROCESSING ACTIVITIES (RoPA) DPDP Act

Every use of personal data, on the record.

Atlas records processing activities across your systems, checks each one against consent and policy, and flags what does not fit.

Under the DPDP Act, your customers can ask how their data has been processed and who it has been shared with. You can only answer if the record exists. With 750+ connectors to systems such as Salesforce, SAP and Darwinbox, Atlas keeps that record for you.

750+ connectors · RESTful APIs · File imports · Consent checks before processing

Know what happens to your data. Prove it.

A record of processing that builds itself from your systems, checks itself against consent and policy, and is ready whenever someone asks.

A living record, not a spreadsheet

The processing review dashboard shows every activity with its purpose, the systems involved and the consent status behind it, updated as your systems work.

750+

Connectors to the systems you run

Plus RESTful APIs and file imports for everything else.

Consent checked first

Valid consent is verified before personal data is processed.

Violations flagged

Off-purpose processing and unauthorised sharing trigger instant alerts.

"What did you do with my data?" Answered.

When a customer asks under Section 11, Atlas generates their processing record and sends it automatically.

Every system mapped

See how data flows between systems, vendors and purposes.

Audit-ready

Ready-to-submit audit summaries and evidence trails for every activity.

01REGISTER

Start with a complete list of your systems

Systems, vendors, data categories and attributes in one inventory.

Add systems one at a time, or import them in bulk from a CSV, for example an export from Active Directory, with maker and checker review on every entry. Record which data categories and attributes each system holds and how often it processes them, add the vendors that handle personal data for you, and trigger a vendor risk assessment as they come on board.

Learn more
02MAP

See how data moves, and why

System Map, System Links and a Data Map built from your policies and purposes.

Link the systems that share data with each other and see the whole network as a visual map. Create your policies and purposes, or import them in bulk from Excel templates, and Atlas builds a Data Map that ties every data attribute to the purpose it serves. Results from Data Discovery feed straight in, and alerts tell you when a policy, purpose or mapping is incomplete.

Learn more
03CAPTURE

Processing recorded as it happens

Connectors and APIs for modern systems, file imports and scheduling for the rest.

Connected systems record their processing activities into a central log automatically, through 750+ connectors and RESTful APIs. Legacy or regulated systems without an API upload their processing logs securely using custom file-mapping templates. Recurring internal activities such as payroll or subscription billing can be scheduled once from the screen, so nothing goes unrecorded.

Learn more
04CHECK

No valid consent, no processing

Consent checks before personal data is used.

Before an activity runs, Atlas checks that valid consent exists for that person and that purpose. Connectors push consent changes into each connected system, so a withdrawal in the Privacy Center reaches your CRM and campaign tools and the next activity is checked against it. Every check is recorded against the activity as evidence.

Learn more
05FLAG

Catch processing that should not happen

Policy violations, unauthorised sharing and unregistered activity, flagged in real time.

Atlas compares each activity with your approved policies and declared purposes. Processing that does not match is flagged, sharing with systems that are not linked or authorised raises an alert, and unregistered processing triggers an instant notification to your privacy team. You find the problem before an auditor or a customer does.

Learn more
06ANSWER

Answer Section 11 requests in minutes

Automated RoPA generation for Data Principal requests.

Section 11 of the DPDP Act lets a Data Principal ask for a summary of their personal data being processed, the processing activities involved, and who it has been shared with. When a request comes in through the Privacy Center, Atlas builds that record from the processing log, keyed to the customer, and sends it automatically. No digging through systems, no manual reports.

Learn more
07GOVERN

Keep only what you need, and know where it goes

Data minimisation insights and a cross-border transfer register.

Data maps surface orphaned data attributes and purposes, the data you hold with no current reason to keep it, so you can act on minimisation and retention. RoPA entries also record where data is transferred outside India, giving you a cross-border transfer register you can review alongside everything else. Processing trends highlight unusual patterns over time.

Learn more
08PROVE

Evidence for every activity, ready to submit

Audit trails, activity reports and audit summaries.

Every activity carries a verifiable evidence trail: what was processed, by which system, for which purpose and under which consent. Activity reports show frequency, purpose and systems, every change to your inventory and mappings is logged, and audit summaries are ready to hand to your internal governance team or a regulator. Export anything to CSV.

Learn more
CONNECTORS

750+ connectors to the systems you already run

Connect Atlas to your CRM, ERP, HR and other business systems so consent, processing records and logs stay in step without manual work.

SalesforceCRMCustomer consent and activity
SAPERP and billingInvoicing, orders, finance
DarwinboxHREmployee data and payroll
+ 750 moreAcross the tools your teams use every dayAsk us about yours

What every connector does

Push consent changes

When a customer gives, changes or withdraws consent, Atlas pushes the update by webhook into the consent fields of each connected system. Your systems check consent locally before they process, with no call back to Atlas each time.

Record processing

Processing activities in each connected system are logged into your RoPA automatically, with the system, purpose and consent behind them, so the record builds itself as your business runs.

Send notifications and logs

Connected systems send notifications and audit logs back to Atlas, so alerts, evidence and your processing dashboard always reflect what is really happening across your estate.

WHAT YOUR TEAM ADDS

A small change on your side, then the connector does the work

Connectors link Atlas to your systems, but each system still needs somewhere to keep consent. In most cases that means adding a consent ID and consent preference fields to the customer or employee record. Once those fields are in place, Atlas keeps them up to date and your system checks them before it processes. We give your application teams a clear standard to follow, so the change is the same in every system.

Also connected across Atlas

Data Discovery: MySQLMariaDBOracleSQL ServerPostgreSQLAWSAzureGoogle Cloud
Everything else: RESTful APIsFile importsEmailSMSWhatsAppSlack alerts

From a list of systems to an audit-ready record in four steps

  1. 01

    Register

    List your systems, vendors, data attributes, policies and purposes, or import them in bulk.

  2. 02

    Connect

    Link your systems through connectors, APIs or file imports, and add the consent fields each one needs.

  3. 03

    Check

    Every activity is recorded and checked against consent and policy, with alerts for anything that does not fit.

  4. 04

    Prove

    Answer customer requests automatically and hand audit summaries to your Board or the regulator.

Could you answer "what did you do with my data?" today?

See Atlas connect to systems like yours, record processing automatically and generate a customer's processing record in a 30 minute demo.

The free gap assessment covers a single department or division.

Frequently Asked Questions

Everything you need to know about processing records and connectors on Atlas.

Ask us anything
WHY RoPA MATTERS
Why do we need a record of processing under the DPDP Act?

Section 11 gives Data Principals the right to ask for a summary of their personal data being processed, the processing activities involved, and the identities of those it has been shared with. You can only answer accurately if you keep a record of what each system does with personal data.

What does Atlas record for each activity?

The system, the purpose, the data involved, the consent status and the time, together with an evidence trail you can show to an auditor or regulator.

Can Atlas answer customer requests about processing automatically?

Yes. When a Data Principal asks through the Privacy Center, Atlas generates their processing record from the log and sends it to them.

CONNECTORS AND INTEGRATION
Which systems can Atlas connect to?

Atlas offers 750+ connectors, including Salesforce, SAP and Darwinbox. Systems without a connector can use RESTful APIs, and legacy systems can upload processing logs through file imports.

What do the connectors do?

They push consent changes into each connected system, record processing activities into your RoPA automatically, and send notifications and audit logs back to Atlas.

Do our application teams need to change anything?

A little. Each system needs somewhere to store consent, usually a consent ID and consent preference fields on the customer or employee record. Once those are in place, Atlas keeps them up to date and the connector handles the rest. We provide a standard for your teams to follow.

How do our systems know if consent is valid?

Atlas pushes every consent change to connected systems by webhook. Each system then checks consent locally before it processes, without calling Atlas every time.

What about activities that do not come from a system, like payroll?

Recurring internal activities such as payroll or subscription billing can be scheduled from the screen once and recorded automatically after that.

MAPPING, ALERTS AND EVIDENCE
How do we get our systems into Atlas?

Add them one by one or import them in bulk from a CSV, for example from Active Directory, with maker and checker review. Policies and purposes can be imported from Excel templates.

What happens when processing does not match policy?

Atlas flags processing that does not match approved policies or declared purposes, alerts you to sharing with unlinked or unauthorised systems, and notifies your team about unregistered processing.

Does Atlas track cross-border transfers?

Yes. RoPA entries record where data is transferred outside India, giving you a cross-border transfer register.

What reports can we get?

Activity reports by frequency, purpose and system, processing trends over time, ready-to-submit audit summaries and CSV exports.

Trusted by 250+ customers worldwide

TTK Duruva Ujjivan Jana UIDAI Equitas Yes Bank