Strategies for Complying with Data Residency Laws in Adobe RTCDP – Is Tokenization a Solution? | Community
Skip to main content
D
dwade4ever_001
Level 2
January 29, 2024
Solved

Strategies for Complying with Data Residency Laws in Adobe RTCDP – Is Tokenization a Solution?

  • January 29, 2024
  • 2 replies
  • 1373 views

Hi Adobe RTCDP Experts,

I am exploring solutions for complying with data residency laws while using Adobe Real-Time Customer Data Platform (RTCDP). Specifically, I am looking at how to handle personal data that originates from countries with strict data residency regulations.

Can tokenization of identifiers be used within RTCDP to meet these legal requirements? If so, how does one typically implement this approach in the platform? Additionally, are there any other recommended strategies within RTCDP for managing data residency?

Any insights or guidance on this matter would be greatly appreciated.

Thank you!

Best,
CK

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by brekrut
     

    I would refer to the attached screenshot regarding the data residency which Adobe has implemented.

     

     

     

    I would look into data label for identify data label which can support your data requirements.

     

     

    2 replies

    brekrut
    Adobe Employee
    brekrutAdobe EmployeeAccepted solution
    Adobe Employee
    January 29, 2024
     

    I would refer to the attached screenshot regarding the data residency which Adobe has implemented.

     

     

     

    I would look into data label for identify data label which can support your data requirements.

     

     

      akshaykapil23
      akshaykapil23
      Level 3
      February 21, 2024

      Hello @dwade4ever_001  Please refer the DUEL policies, This speaks about all the leagalities that we may adhere for data collection. 

       

      https://experienceleague.adobe.com/docs/experience-platform/data-governance/labels/reference.html?lang=en

        Terms & ConditionsAccessibility statement

        Loading footer...