Overview#

Data Privacy is information relevant or pertaining to privacy aspects of a given data value

Individual Consented#

RPs may have specific legal, policy, or business requirements regarding whether a user consented to the release of a specific value. This element enables organizations to meet those requirements, ensuring that they’ve gained express consent from an Entity. Recommended values include:
  • Yes - The individual expressly consented to the release of the attribute’s value for the purposes of the transaction.
  • No - The individual has not expressly consented to the release of the attribute’s value.
  • Unknown - It is not known by the provider whether or not the individual has expressly consented to release of the attribute.

Date Consented#

In addition to requiring information around whether the individual has consented to release of the attribute value, some RPs may wish to understand when that consent was received. Individual sentiments towards privacy and specific pieces of data may change over time. As a result, organizations may wish to employ the date consented metadata element when leveraging an attribute value in an access or eligibility decision.

Acceptable Uses#

This explains to RPs what business cases the metadata can be used to support according to policy restrictions conveyed by the AP.

For example, the attribute value might purely be useful in authorization, determining a user's eligibility for services; alternatively, values might be eligible for use beyond the initially intended purpose, or not eligible for any further disclosure. Additionally, organizational Entity or Trust Frameworks might also create their own categories of acceptable uses based on their policies.

Recommended values for this element include:

  • Authorization - The value can be used to determine user eligibility for services or privileges and can be used to provide those services.
  • Secondary Use - The value may be used for purposes beyond that for which they were initially divulged. Additional use requires separate, explicit consent from user at initiation.
  • No Further Disclosure - The attribute value should not be passed on to other parties for any purpose unless required by law.

Cache Time to Live#

This metadata element describes the length of time which a specific attribute value may reside in cache memory for use again in future transactions. Due to the sensitivity of certain attributes values, this metadata element enables the parties involved to properly cache and handle the values they are sending and retrieving as part of their transactions. Unlike many of the other metadata elements in this schema, the cache time to live enables attribute providers to express requirements to the RP around the protection of the information they are delivering as part of an assertion. In some cases the time to live may be dictated by regulation or law and this information needs to be relayed to RP systems so data are handled accordingly. The more sensitive an attribute value, the shorter time it will likely be enabled to live in temporary memory. As an example, the cache time to live for something like a credit card CVV may be just a couple of seconds, whereas the cache time to live for birth date may be substantially longer — potentially hours or days.

Data Deletion Date#

This refers to long-term holding of data. Minimizing data, and indicating the retention time for this data, is a generally accepted privacy tenant. Some attribute values produce little to no privacy risk for individuals, and can potentially be used forever without producing any negative consequences. Other values are more likely to produce problems for individuals; a deletion date ensures that this sensitive information is disposed of at a certain point.

More Information#

There might be more information for this subject on one of the following:

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-2) was last changed on 02-Aug-2016 10:49 by jim