Customer Data Erasure
Personally Identifiable Information (PII) is information that identifies an individual, or that could be used in combination with other information to identify an individual. Many countries have data privacy laws governing the use of such information. A key aspect of these laws is an organization’s obligation to erase personal information when there is no compelling reason to retain it. This obligation can be fulfilled either by deleting the data or altering it so it can no longer be associated with an individual.
Object Erasure is an existing capability designed to support the right to erasure requirements. It provides configuration and processes that can be extended to implement the appropriate policies for PII data within Oracle Utilities Customer Cloud Service, Oracle Utilities Customer Care and Billing Cloud Service, and Oracle Utilities Billing Cloud Service. In previous releases, application-owned erasure logic obfuscated PII data on the root tables for the Person, Account, and Service Agreement maintenance objects and removed certain related data; the exception being characteristics, data areas and owned attachments.
In this release, customer data erasure has been enhanced to optionally remove additional PII data when processing a Person, Account, or Service Agreement (SA) record, including:
- Person
- Characteristics (CI_PER_CHAR)
- Person data area (CI_PER.PER_DATA_AREA)
- Owned attachments (F1_ATTACHMENT and related child tables) linked to the specific person record
- Account
- Characteristics (CI_ACCT_CHAR)
- Account data area (CI_ACCT.ACCT_DATA_AREA)
- Owned attachments (F1_ATTACHMENT and related child tables) linked to the specific account record
- Service Agreement
- Characteristics (CI_SA_CHAR)
- Service agreement data area (CI_SA.SA_DATA_AREA)
- Owned attachments (F1_ATTACHMENT and related child tables) linked to the specific service agreement record
This helps utilities support their data privacy "right to erasure" obligations more completely and consistently using out-of-the-box functionality by enabling removal of PII data that may be stored outside the core Person, Account, or Service Agreement tables.
Steps to enable and configure
To enable and configure this feature, refer to the Person, Account and Service Agreement Obfuscation Algorithms section of the Administrative User Guide for more information.
Key resources
Refer to the Data Privacy and Data Privacy Addendum sections of the Administrative User Guide for more information.