Compliance with GDPR/DAC6
Data processing criteria compliant with GDPR/DAC6¶
In applications compliant with GDPR/DAC6 legislation, the Quick Data Loader processes the data as follows.
| Data source | Target type | Data processing type |
|---|---|---|
| External (uploaded file, Odata etc.) | Data (Amounts, Intercompany) | Data from external sources (Files, Other databases, OData services) are all assumed to be plain data (not encoded or encrypted). No data is encoded or encrypted since no current output dimension provides for encoding or the protection of personal data. |
| Internal query | The selection of plain data is delegated to the parametrizer. | |
| Analytical Workspaces | A check will block the execution of the input fields with the Encode or Personal data protection options enabled. | |
| External source (uploaded file, OData etc.) | Analytical Workspaces | the data will be encoded and/or encrypted if any output fields have the Encode and/or Personal data protection option enabled. |
| Internal query | The selection of data from the source, compatible with the Encode and Personal data protection options defined in the target, is delegated to the parametrizer. | |
| Analytical Workspaces | A check will block execution if a piece of data from the source and one from the target, which have been related, have different values for the Encode and Personal data protection options. |
Note: the preview window for the data to be imported displays the plain data even when it is coded or encrypted.