Container which specify legal content for the role related to the GDPR. E.g which law enforce the presence of the attribute, who is a recipient of the data, to which purposes are data used etc.
| Name | Type | Multiplicity | Description |
|---|---|---|---|
| controllerName |
property string |
[0,1] | Name of the company, organization which controls data processing |
| controllerContact |
property string |
[0,1] | Contact information about company, organization which controls data processing |
| dpoContact |
property string |
[0,1] | Contact information for data privacy officer |
| processingPurposesDescription |
property string |
[0,1] | Purposes for processing, e. |
| legitimateInterestDescription |
property string |
[0,1] | Legitimate interest for data processing. |
| dataRecipientDescription |
property string |
[0,1] | Contains information about recipient of the data. |
| periodOfStorageDescription |
property string |
[0,1] | How long we need to store the data (e. |
| dataErasureDescription |
property string |
[0,1] | Description of data erasure practices, especially the period for data erasure. |
| automatedDecisionMakingDescription |
property string |
[0,1] | Description whether automated decision making (e. |
| securityMeasuresDescription |
property string |
[0,1] | Description of the security measures that apply to data processing (e. |
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Flags: RAM,runtime
Multiplicity: [0,1]
Purposes for processing, e.g marketing, contract,...
This is a free-form field that can be used to describe data processing
purposes in a human-readable form suitable to be displayed to user.
This is NOT structured information. Structured information schema
is planned for future midPoint releases.
Flags: RAM,runtime
Multiplicity: [0,1]
Legitimate interest for data processing. This may be a legislation that allows
data processing, consent or other lawful basis.
This is a free-form field that can be used to describe legitimate
interests in a human-readable form suitable to be displayed to user.
This is NOT structured information. Structured information schema
is planned for future midPoint releases.
Flags: RAM,runtime
Multiplicity: [0,1]
Contains information about recipient of the data.
This is a free-form field that can be used to describe recipients
in a human-readable form suitable to be displayed to user.
This is NOT structured information. Structured information schema
is planned for future midPoint releases.
Flags: RAM,runtime
Multiplicity: [0,1]
How long we need to store the data (e.g after the employee left the organization)
This is a free-form field that can be used to describe storage period
in a human-readable form suitable to be displayed to user.
This is NOT structured information. Structured information schema
is planned for future midPoint releases.
Flags: RAM,runtime
Multiplicity: [0,1]
Description of data erasure practices, especially the period for data erasure.
This is a free-form field that can be used to describe data erasure
in a human-readable form suitable to be displayed to user.
This is NOT structured information. Structured information schema
is planned for future midPoint releases.
Flags: RAM,runtime
Multiplicity: [0,1]
Description whether automated decision making (e.g. profiling) is part of the
data processing.
This is a free-form field that can be used to describe automated decision making
in a human-readable form suitable to be displayed to user.
This is NOT structured information. Structured information schema
is planned for future midPoint releases.
Flags: RAM,runtime
Multiplicity: [0,1]
Description of the security measures that apply to data processing
(e.g. pseudonymization, confidentiality, ...)
This is a free-form field that can be used to describe security measures
in a human-readable form suitable to be displayed to user.
This is NOT structured information. Structured information schema
is planned for future midPoint releases.