Understand where personal data lives, why it exists and where it moves.
Explore the direction for a connected view of personal data across systems, applications, teams, vendors and processing activities.
- Discover
- Map
- Understand
- Maintain
- SalesforceOwner: Sales OperationsName, Email, Phone, Customer ID
- HubSpotOwner: MarketingEmail, Marketing Preferences
- SnowflakeOwner: Data TeamAggregated customer data
- ZendeskOwner: SupportName, Email, Support History
- HubSpotSalesforcePreference state
- SalesforceSnowflakeCustomer profile
- ZendeskSnowflakeSupport history
What Data Mapping is intended to help you accomplish
Privacy data mapping is the process of identifying what personal data an organisation processes, where that data is stored, why it is used, and how it moves between systems, teams and vendors. ConsentCenter Data Mapping is being built around this picture — the focus areas below reflect current product direction, and detailed capabilities will be published as the build is finalised.
Data visibility
Know where personal data lives
See how Data Mapping is being built to show where personal data is stored, why it is used and how it moves.
Intended outcomes for your team
- Discover systems, applications and third-party vendors
- Map data movement, processing purpose and ownership
- Keep the inventory current as the organisation changes
How Data Mapping is being designed to work
This sequence reflects the current product direction, from initial discovery through keeping the data picture current.
Discover
Identify the systems, applications and vendors across the organisation that are likely to hold personal data.
Map
Build a structured view of how that data moves between systems, teams and third parties.
Understand
See the purpose behind each processing activity and who owns it, in language a privacy team and the business both understand.
Maintain
Keep the picture current as systems, vendors and processing activities change, rather than a static point-in-time exercise.
See the systems around personal data.
Select a system in this illustrative landscape to see the kind of ownership, purpose and data context that Data Mapping is being designed to surface.
Data Mapping is in development. This is a product-direction illustration, not a representation of shipped functionality.
CRM · Salesforce
Illustrative example
- Data
- Name · Email · Phone · Customer ID
- Purpose
- Customer management
- Owner
- Sales Operations
- Connected
- 3 systems
Select a system to see an illustrative example of what Data Mapping is designed to surface.
Add DSAR when the next workflow needs it.
See how mapped systems are intended to support privacy rights fulfilment.
What teams ask about Data Mapping
Practical answers about scope, setup and how this product fits into a wider privacy program.
Data Mapping is ConsentCenter’s newest product and is still being finalised. This page reflects the current product direction rather than a complete list of shipped capabilities — talk to us for the latest build status.
Cookie Consent and UCPM tell you what a person agreed to and what technologies are collecting data. Data Mapping is being designed to show where that data goes — context that can help DSAR teams act on a privacy rights request.
The current product direction is standalone first, with planned connections to DSAR and UCPM when shared data context would help.
Want the latest Data Mapping build update?
Tell us what you need to map. We will share the current product direction and where the build stands.