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

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Data privacy

# Data privacy in Instance Data Replication {#ariaid-title1}

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

The ability of replication sets to host multiple remote consumers in Instance Data Replication (IDR) means that there are
potential data privacy issues to consider.

Replications sets in IDR serve multiple instances with
multiple consumers. A replication set can have a single customer or can have multiple customers.
A consumer could also be located within the same geographic region as the producer or located in
a different geographical region.

Depending on how you configure your replication set, you can have data sharing internally,
between offices of the same company, or externally, extending across multiple companies. You can
also confine data sharing to a single location or region, or you can share data across all
regions.

An active replication set occurs after the producer instance administrator approves a consumer
subscription. An active replication set involves data transfer, which could include transfer of
personal data, between geographical regions. The data transfer between different geographical
regions could subject the data to differing personal data regulations.

During the approval process, if IDR determines that the
consumer and producer instances are in different geographical regions, it alerts the producer
before activation. This alert should make administrators aware of the potential for differing
data transfer regulations between regions.

Once a replication set is active, a replication set with multiple consumers might have specific
discrete rules which direct specific data to specific consumers. Any modification of a discrete
rule on an active replication set which spans multiple consumers has the potential to expose
data. This data exposure can include personal data, which might be viewable by unintended
consumers that subscribe to the replication set.

If you set bi-direction between a producer and consumer instance, the consumer can originate
data that shares back to the producer instance. This data can also potentially reach any other
consumer that is part of the replication set.
**Zugehörige Konzepte**   

* [Domain separation and IDR](https://servicenow-prod.fluidtopics.net/W8LXvFQ6WkErBu5atYl~WA "Instance Data Replication (IDR) functions at the data level, which means it does not explicitly support domain separation.")  
**Zugehörige Verweise**   

* [Adapter descriptions for Instance Data Replication](https://servicenow-prod.fluidtopics.net/pq84zn~7k8P_dPGAcmlgeQ "Adapters modify the producer data before inserting the data on consumer instances in Instance Data Replication (IDR).")
* [Excluded tables in Instance Data Replication](https://servicenow-prod.fluidtopics.net/CGHsifCYjKLdsrUMKb5zHg "You can't replicate certain tables in Instance Data Replication (IDR). Child tables of tables in the exclusion list are also excluded.")
* [Instance Data Replication system properties](https://servicenow-prod.fluidtopics.net/KlZt_rJv~Wx_PKOYhg64nA "These system properties control the behavior of the Instance Data Replication (IDR) application.")
* [Instance Data Replication roles](https://servicenow-prod.fluidtopics.net/PaT2NYw_nNMtoO~NPzJq8Q#instance-data-replication-roles "Instance Data Replication (IDR) is installed with these roles.")