One inventory of purposes
Every purpose your organisation processes personal data for, each with its legal basis, how long the data may be kept and the events that end that period.
Demo dataPurposes, legal bases, retention and sharing, defined once and applied system by system, so everyone knows what data they may hold and why.
Every purpose your organisation processes personal data for, each with its legal basis, how long the data may be kept and the events that end that period.
Demo dataTie each retention period to the event that starts the clock, not a date someone has to remember.
Consent or a legitimate use under the DPDP Act, recorded once.
The frequency of processing for every purpose.
For every system, see the consent behind the data, who can access it, each attribute, the purposes it serves, where it is shared and how often it is processed.
See which attributes a system captures and which it receives.
Download the data map for an audit, a DPIA or your Board.
A single purpose inventory, grouped the way your business works.
List every purpose your organisation uses personal data for, from account activation and billing to marketing and legal requests, grouped by area. Each purpose is written in plain language once and reused everywhere: in system policies, in consent notices and in your records of processing. No more three teams describing the same purpose three different ways.
Consent or a legitimate use, set for every purpose.
The DPDP Act allows processing on the basis of consent, or for certain legitimate uses set out in Section 7. Atlas records the legal basis for each purpose, with a note on why it applies. Purposes that rely on consent are linked to your consent notices, so a purpose can never quietly run without the consent it needs.
Policies applied to each system, attribute by attribute.
For every system, define which data attributes it is allowed to collect, which it may process, which it may share with other systems or vendors, and for which purposes. System owners see exactly what applies to them. Anything outside the policy, such as a new field nobody approved, stands out instead of slipping through.
Retention periods with the triggers that start the clock.
The DPDP Act expects you to erase personal data once its purpose is served, unless a law requires you to keep it. For each purpose, set the retention period and the events that end it, such as an account being deleted, consent being withdrawn or a loan being closed. Atlas tracks what is due and passes erasure requests to your systems through API and webhook integration, while respecting legal retention periods.
Shared systems and inherited data attributes, side by side.
Record which systems each system shares data with, and which attributes it inherits from others rather than capturing itself. When the billing system receives a customer’s address from the CRM, you can see where it came from and which purposes and policies travel with it. Nothing arrives in a system without a source you can point to.
People with access and the frequency of processing for every system.
Record who has access to each system’s personal data and how often each purpose runs: daily, weekly or once. It is the detail auditors and DPIAs ask for, and it shows you where access is wider than the purpose needs. Combined with the Rule 6 security safeguards, it gives a clear picture of who can see what.
A visual data map, from capture to frequency of processing.
Once policies and purposes are defined, Atlas draws a data map for each system. It shows the consent behind the data, who has access, every data attribute, the purposes each attribute serves, the systems it is shared with and how often it is processed. Zoom in, follow a single attribute, and download the map for an audit, a DPIA or your Board.
Define a purpose once and every module uses it.
The purposes you define here are the same ones your consent notices list, your systems check before processing and your records of processing report against. When a customer withdraws consent for a purpose, Atlas knows which systems, attributes and vendors are affected. When a Data Principal asks how their data was used, the answer is already mapped.
Attributes with no purpose, and data held outside policy, flagged.
When every attribute must map to a purpose, the gaps become obvious. Atlas flags attributes that no purpose justifies, and compares discovery scan results with each system’s policy to show personal data held where it is not allowed. You get a concrete list to stop collecting, erase or justify, which is what data minimisation looks like in practice.
Build your purpose inventory with a legal basis, retention period and triggers for each purpose.
Set each system’s policy: what it may collect, process and share, and for which purposes.
Add access, shared systems, inherited attributes and frequency, and see the data map come together.
Use the same purposes in notices and consent checks, act on retention and fix data held outside policy.
See how Atlas turns purposes and policies into a clear data map for every system. We will build one for a system like yours in a 30 minute demo.
The free gap assessment covers a single department or division.
Everything you need to know about policies, purposes and data maps on Atlas.
Ask us anythingA single list of every reason your organisation processes personal data, grouped by area such as account management, marketing or legal and compliance. Each purpose carries its legal basis, retention period and the events that end it.
The two the DPDP Act allows: consent, and the legitimate uses set out in Section 7. Purposes that rely on consent are linked to your consent notices so they cannot run without it.
Because the DPDP Act only allows processing on one of those grounds. Recording the basis for each purpose shows you have thought about it, and it is the first thing an auditor or the Board will ask about.
Which data attributes the system may collect, process and share, and for which purposes. Anything held outside that policy stands out, so it can be removed or justified.
The events that end a retention period or start its clock, such as an account being deleted, consent being withdrawn or a loan being closed. They let retention follow what actually happens to a customer rather than a fixed calendar date.
Atlas tracks what is due for erasure and sends the request to your systems through API and webhook integration. The deletion is carried out by the systems that hold the data, subject to any period a law requires you to keep it.
For each system: the consent behind the data, the people with access, every data attribute, the purposes each attribute serves, the systems it is shared with and how often it is processed.
Attributes a system receives from another system rather than capturing itself, such as a billing system receiving a customer’s address from the CRM. Atlas shows where each one came from.
Yes. Download it for audits, DPIAs, Board reviews or to share with system owners.
The same purposes appear in your consent notices, in the consent checks your systems run before processing and in your records of processing. When someone withdraws consent or asks how their data was used, Atlas already knows which systems and attributes are involved.
It flags attributes that no purpose justifies, and compares discovery scan results with each system’s policy to show personal data held where it is not allowed.
In the FRS Labs cloud as SaaS, in your own AWS or Azure account, or on your own servers.