Consent Management: Mapping Fides Data Uses to Regulations & Frameworks
In this tutorial we'll walk through how to map Data Uses in Astralis to major privacy regulations when configuring your systems.
After reading this, you'll be familiar with how data uses map to regulations such as GDPR and CCPA, as well as frameworks like IAB TCF.
Prerequisites
For this tutorial you'll need:
- The role of
OwnerorContributorfor your Astralis organization. - At least one system with a data use on your data map. Read how to add systems to the Data Map now.
What are Data Uses?
Data uses are the purpose for which your organization uses data. For example, if you use a customer's email address to send marketing information, the data use might be "Email Marketing." Astralis contains a comprehensive set of Data uses that have already been mapped to major regulations so that you don't have to do this.
As such, when you are adding a vendor or system to Astralis, you can select from existing data uses and these will automatically map to the appropriate regulations based on the location of the user.
The remainder of this document contains a list of the mapping between major regulations and frameworks to Astralis.
Fides Data Uses → GDPR
The below diagram illustrates the relationship between Fides Data Uses and the primary categories of consent under the ePrivacy directive and GDPR:
| GDPR Consent Category | Fides Data Use | Fides Ontology |
|---|---|---|
| Analytics and analysis | Analytics | analytics |
| Strictly necessary data processing, essential to the service. | Essential | essential |
| Functional, personalization or other non-essential enhancements. | Functional | functional |
| Advertising or marketing activities. | Marketing | marketing |
Fides Data Uses → CCPA
The below diagram illustrates the relationship between Fides Data Uses and the primary categories of consent under the ePrivacy directive and GDPR:
| CCPA / Other US Opt-Out Consents | Fides Data Use | Fides Ontology |
|---|---|---|
| Opt out of Data Sales, Sharing & Targeted Advertising | First Party Targeted, Third Party Targeted | marketing.advertising.first_party.targeted, marketing.advertising.third_party.targeted |
Fides Data Uses → IAB TCF 2.2
The below diagram illustrates the relationship between Fides Data Uses and IAB TCF 2.2 11 primary purposes:
| TCF # | TCF Purpose | Fides Data Use | Fides Ontology |
|---|---|---|---|
| 1 | Store and/or access information on a device | Storage | functional.storage |
| 2 | Use limited data to select advertising | Frequency Capping, Negative Targeting | marketing.advertising.frequency_capping, marketing.advertising.negative_targeting |
| 3 | Create profiles for personalised advertising | Profiling | marketing.advertising.profiling |
| 4 | Use profiles to select personalised advertising | First Party Targeted, Third Party Targeted | marketing.advertising.first_party.targeted, marketing.advertising.third_party.targeted |
| 5 | Create profiles to personalise content | Profiling | personalize.content.profiling |
| 6 | Use profiles to select personalised content | Profiled | personalize.content.profiled |
| 7 | Measure advertising performance | Ad Performance | analytics.reporting.ad_performance |
| 8 | Measure content performance | Content Performance | analytics.reporting.content_performance |
| 9 | Understand audiences through statistics or combinations of data from different sources | Campaign Insights | analytics.reporting.campaign_insights |
| 10 | Develop and improve services | Improve Service | functional.service.improve |
| 11 | Use limited data to select content | Limited | personalize.content.limited |
