---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Exploring Data Privacy

# Exploring Data Privacy {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Use Data Privacy to classify sensitive data and to remove personally identifiable
information (PII) from user data in a production instance and anonymize data in non-production
instances. Once anonymized, the user data is no longer considered regulated private
information.
Developers must work with data on non-production instances to ensure that their implementations are working as expected. While importing data from your production instance is a useful way to simulate production, it
presents a security risk. Administrators can use data privacy to provide developers with data that does not contain private information to work safely in a non-production environment.

## Data classification {#data-privacy__section_ht2_yc1_xvb}

Identify and classify your sensitive data according to pre-defined criteria determined by the level of sensitivity of the data types in your instance. Data sensitivity
levels help determine how each type of classified data should be handled. There are several pre-defined classes provided with base level data privacy. Use the classification section of Data Privacy to label and group data within
your instance. Add classes, view data class structure and classify data. Group data by type, using pre-defined or user-defined data classifications.

## User data anonymization {#data-privacy__section_qd5_3nr_brb}

As an administrator, you define whether to anonymize all information for all users or for a subset of users. When anonymized, data for the selected user records is
replaced with randomized values or values you define. When replacing values, the data structure can be preserved using various techniques.

## Data privacy options {#data-privacy__section_hfy_vgx_vvb}

* [Data privacy (Classic)](https://servicenow-prod.fluidtopics.net/TTVDmuZBAOgxoWUo~PMUzA "Data privacy (Classic) is available as a family release. The last family updates were released in the Tokyo launch."): First use the data classification app to group your data by type, using pre-defined or user-defined data classifications. Then create data privacy techniques and jobs to anonymize PII.
* [Data privacy](https://servicenow-prod.fluidtopics.net/XHOfN~eFiYYliRIfKMlxhg "The data privacy store app is a Next Experience refresh for data classification and data privacy with modern look, feel, and usability. Data privacy store app is supported in Utah and above.") (Store App): Classify and anonymize your data all from within the data privacy app.
{#data-privacy__ul_ify_vgx_vvb}

## Installation details {#data-privacy__section_mtp_zsz_tfc}

You must have the following applications installed on your instance:

* Data Privacy (Classic) \[com.glide.data_privacy\]
* Data Privacy \[sn_dp_store_app\]
* Data Discovery \[sn_data_discovery\]
* Data Discovery APIs\[com.glide.data_discovery\]
{#data-privacy__ul_jd3_btz_tfc}  
Here is the how the installation works:

* Installing the Data Privacy Store App will auto install the Data Discovery Store App, Data Privacy (Classic) plug-in, and the Data Classification plugin.
* Installing the Data Discovery Store App will auto install the Data Discovery APIs plugin
{#data-privacy__ul_jgt_btz_tfc}

## Considerations {#data-privacy__section_j4v_fsr_brb}

* Only classified data can be anonymized. For information on data classes and classification, see [Data classification](https://servicenow-prod.fluidtopics.net/lTzMDApKb~I4lO2wqMzTBA "Group data by type, using pre-defined or user-defined data classifications. If you have an assigned data classification administrator or auditor role, you can administer different data classes or visually analyze the current state of different types of data within the instance.") (Classic) or [Data classification](https://servicenow-prod.fluidtopics.net/6MbHL3kbHWhPzPexrEsgXA "Group data by type, using pre-defined or user-defined data classifications. If you have an assigned data classification administrator or auditor role, you can administer different data classes or visually analyze the current state of different types of data within the instance.") Store App.
* PII in logs and other auditing data are not anonymized.
* Only structured data can be anonymized. Unstructured data, such as Journal fields, comments, attachments, and other fields where partial text may represent PII is not anonymized. See [Supported field types for anonymization](https://servicenow-prod.fluidtopics.net/F7Ag_SbM~OXwVtrCdsxvIA "Check which field types are supported when anonymizing data.") for more information.
* Integrations with single sign-on (SSO) systems may resynchronize user information from their source of truth systems. There is no mechanism in place to ensure the permanency of the de-identification of sys_user data. For information on user administration and sys_users see [User Administration](https://www.servicenow.com/docs/access?context=c_UserAdministration&version=australia&pubname=australia-platform-administration&ft:locale=en-US).
{#data-privacy__ul_ry4_gsr_brb}