Back to results
US 8,606,746 B2Granted
Privacy management policy hub
AssigneeOracle International Corporation
InventorsHwee Har Yeap, Catherine You, Qin Lu, Jane Li, Weiwei Hsieh, Lindy H. Chan
Life of this patent
Estimating the term…
Abstract
A system architecture is disclosed that includes a privacy management system. In particular, the privacy management system provides a policy hub for maintaining and managing customer privacy information. The privacy management system maintains a master data database for customer information and customer privacy preferences, and a rules database for privacy rules. The privacy management system captures, synchronizes, and stores customer privacy data. Privacy rules may be authored using a privacy management vocabulary, and can be customized for an enterprise's privacy policies.
Claims26
A privacy management system comprising:
- a privacy database, wherein
- the privacy database comprises a privacy sharing preference of a customer,
- the privacy sharing preference is configured to control sharing of personally identifiable information (PII) of the customer, and
- the PII comprises
- a first portion, and
- a second portion;
- a processor;
- and
- a memory coupled to the processor, the memory storing instructions executable by the processor, the instructions configured to implement a privacy process module, wherein
- the privacy process module is communicatively coupled to the privacy database,
- the privacy process module is configured to
- receive an insert record request from a source, wherein
- the insert record request comprises privacy data of the customer, and
- the source is an external computer system, and
- determine whether a best version record associated with the customer exists in the privacy database, wherein
- the best version record comprises a most current representation of the privacy sharing preference,
- the privacy process module comprises a survivorship engine, wherein the survivorship engine is configured to
- determine whether the source is trusted,
- determine whether the privacy data can be used to update the best version record, in response to a determination that the source is trusted,
- identify one or more fields of the privacy data that can be used to update one or more fields of the best version record, based on survivorship rules, and
- update the one or more fields of the best version record to produce an updated best version record, and
- the privacy process module is further configured to
- store a revision history of the best version record, wherein
- the revision history comprises at least a portion of the privacy data, the best version record, and the updated best version record,
- determine whether the privacy data comprises at least one of opt-in information of the customer, wherein
- the opt-in information indicates at least the first portion can be shared, or
- opt-out information of the customer, wherein
- the opt-out information indicates at least the second portion should not be shared,
- define a default privacy sharing preference that indicates at least one of
- the first portion is shared, or
- the second portion is not shared, and
- update the best version record with the default privacy sharing preference.
29 more elements
A method comprising:
- receiving, at a privacy management computer system, an insert record request from a source, wherein
- the insert record request comprises privacy data of a customer, and
- the source is an external computer system;
- determining whether a best version record associated with the customer exists in a privacy database, wherein
- the best version record comprises a most current representation of a privacy sharing preference of the customer,
- the privacy sharing preference is configured to control sharing of personally identifiable information (PII) of the customer, and
- the PII comprises
- a first portion, and
- a second portion;
- determining whether the source is trusted;
- determining whether the privacy data can be used to update the best version record, in response to a determination that the source is trusted;
- identifying one or more fields of the privacy data that can be used to update one or more fields of the best version record, based on survivorship rules;
- updating the one or more fields of the best version record to produce an updated best version record;
- storing a revision history of the best version record, wherein
- the revision history comprises at least a portion of the privacy data, the best version record, and the updated best version record;
- determining whether the privacy data comprises at least one of
- opt-in information of the customer, wherein
- the opt-in information indicates at least the first portion can be shared, or
- opt-out information of the customer, wherein
- the opt-out information indicates at least the second portion should not be shared;
- defining a default privacy sharing preference that indicates at least one of the first portion is shared, or
- the second portion is not shared;
- and
- updating the best version record with the default privacy sharing preference.
21 more elements
A non-transitory computer program product comprising non-transitory computer readable storage media comprising a plurality of instructions executable on a computer system, wherein the plurality of instructions are configured to:
- receive an insert record request from a source, wherein
- the insert record request comprises privacy data of a customer, and
- the source is an external computer system;
- determine whether a best version record associated with the customer exists in a privacy database, wherein
- the best version record comprises a most current representation of a privacy sharing preference of the customer,
- the privacy sharing preference is configured to control sharing of personally identifiable information (PII) of the customer, and
- the PII comprises
- a first portion, and
- a second portion;
- determine whether the source is trusted;
- determine whether the privacy data can be used to update the best version record, in response to a determination that the source is trusted;
- identify one or more fields of the privacy data that can be used to update one or more fields of the best version record, based on survivorship rules;
- update the one or more fields of the best version record to produce an updated best version record;
- store a revision history of the best version record, wherein
- the revision history comprises at least a portion of the privacy data, the best version record, and the updated best version record;
- determine whether the privacy data comprises at least one of
- opt-in information of the customer, wherein
- the opt-in information indicates at least the first portion can be shared, or
- opt-out information of the customer, wherein
- the opt-out information indicates at least the second portion should not be shared;
- define a default privacy sharing preference that indicates at least one of
- the first portion is shared, or
- the second portion is not shared;
- and
- update the best version record with the default privacy sharing preference.
22 more elements
Dependencies are inferred from the claim text.