Data governance, privacy, and security
Federated Audience Composition provides several services and tools that let you comply with your business practices, legal obligations, and development processes.
These services can be arranged into three categories:
Data governance data-governance
You can use data governance to manage and identify your customer’s data, ensuring it’s properly labeled to abide restrictions defined by your organization or by legal regulations.
Data usage labels data-usage-labels
You can use data usage labels to categorize datasets and fields based on the governance policies that apply to that data. After you create an audience using compositions, you can apply the appropriate data labels on the resulting schema to ensure it abides to the required usage restrictions.
For more information on using data labels in Federated Audience Composition, please read the apply access labels section.
Privacy
Federated Audience Composition provides the federated data for ÃÛ¶¹ÊÓƵ Experience Platform and ÃÛ¶¹ÊÓƵ Journey Optimizer to use, and ensures the privacy of your user’s data is respected.
Privacy Service privacy-service
Since Federated Audience Composition does not store any of the customer data from any of the data warehouses, you can use ÃÛ¶¹ÊÓƵ Experience Platform Privacy Service to comply with data subject and data delete requests.
For example, when you create an audience using the save activity block in the composition canvas, the resulting audience is stored in the data lake in Experience Platform as an external audience. This external audience is marked with its identity field and identity namespace. As a result, you can use Privacy Service to access and remove those profiles with an external audience.
Alternatively, after creating a profile enrichment by using the save profile activity in the composition canvas, the resulting enrichment is stored in Experience Platform as a profile-enabled schema and profile-enabled dataset. This enrichment data is marked with an identity field and identity namespace. As a result, you can use Privacy Service to access and clean these profiles.
For more information on Privacy Service, please read the Privacy Service overview.
Privacy requests privacy-requests
In Privacy Service, you can create and manage individual privacy requests to access and delete customer data from Federated Audience Composition. Privacy Service provides both a user interface and a RESTful API to help you manage customer data requests.
For more information on creating and managing privacy requests, please read the privacy jobs in the Privacy Service UI guide.
Consent policy enforcement consent
Federated Audience Composition, through Experience Platform, offers tools that let you automate your consent enforcement, ensuring you are activating audiences based on the consent provided to your customers.
For example, when you create an audience using the save activity block in the composition canvas, the resulting audience is stored in the data lake in Experience Platform as an external audience. Experience Platform automatically supports consent validation during activation. For more information, please read the Segmentation Service FAQ.
Alternatively, after you create a profile enrichment by using the save profile activity in the composition canvas, the resulting enrichment is stored in Experience Platform as a profile-enabled schema and profile-enabled dataset. For existing profiles, available consent attributes are automatically honored during activation. For new profiles, consent attributes provided during the profile ingestion are automatically honored during activation. For more information on applying consents to profiles, please read the consents and preferences field group guide.
For more information on applying consents, please read the manage policies UI guide.
Data Lifecycle data-lifecycle
Since Federated Audience Composition does not store any of the customer data from any of the data warehouses, you can use Experience Platform to handle the data lifecycle. With Advanced Data Lifecycle Management, you can manage your data lifecycle at both a dataset and record level.
For example, when you create an audience by using the save activity block in the composition canvas, the resulting audience is stored in the data lake in Experience Platform as an external audience. Since this data is not stored in Federated Audience Composition, the audience data and the corresponding datasets is automatically deleted when the audience is delete in Audience Portal.
Alternatively, after you create a profile enrichment by using the save profile activity in the composition canvas, the resulting enrichment is stored in Experience Platform as a profile-enabled schema and profile-enabled dataset. As a result, you can Data Lifecycle to access and clean the profiles.
For more information on using Data Lifecycle, please read the Data Lifecycle overview.
Security security
Data security ensures your data is kept safeguarded in Federated Audience Composition.
Encryption encryption
Federated Audience Composition provides encryption through data-at-rest encryption, data-in-transit encryption, and customer-managed keys.
Data at rest refers to the customer data that is used within Federated Audience Composition. The data is encrypted by the cloud service provider, and is used in Federated Audience Composition in its encrypted form.
Data in transit refer to the customer data as it moves from one component to another in Federated Audience Composition. The data is kept encrypted throughout Federated Audience Composition components using TLS 1.3 over HTTPS.
For more information on how ÃÛ¶¹ÊÓƵ handles data encryption, please read the guide on data encryption in Experience Platform.
Customer managed keys customer-managed-keys
Customer managed keys let you have control of your data, by letting you use your own encryption keys to encrypt your data. Since Federated Audience Composition does not store any of the customer data, you can use customer managed keys directly on the resulting audiences and enrichments, since they’ll be stored in the data lake on Experience Platform.
For more information on customer managed keys, please read the customer managed keys guide.
Audit log audit-log
All create, read, update, and delete operations performed in Federated Audience Composition are logged in the audit trail. You can use this audit log to track these actions, enforce accountability, and support compliance audits.
For more information, please read the Audit Trail overview.
Access control access-control
You can control access to Federated Audience Composition at both a field and role based level. You can use these access controls to enforce data governance policies, limit exposure of sensitive information, and align access with user responsibilities.
For more information on access control in Federated Audience Composition, please read the access control guide.
Data localization data-localization
Federated Audience Composition does not store any customer data. As a result, you need to ensure that you only connect your external databases with the matching sandbox region to keep your data in the same region. If you connect a different region’s database to a sandbox, ÃÛ¶¹ÊÓƵ is not responsible for data localization.
Next steps next-steps
After reading this guide, you have a better understanding about the data governance, privacy, and security features in use for Federated Audience Composition, including data usage labels, privacy compliance, consent enforcement, data lifecycle management, and access control.