In cases of repetitive projects, executed on the same group of respondents (e.g. doctors or teachers database), it is recommended to register the database in the central respondents database. This will ensure instant access to contacts history and to all changes within a single group of projects.

In addition to the aforementioned benefits of executing multiple projects using a shared database, the 'Central Database' constitutes a significant facility with respect to the GDPR. It improves Personal Data Administrator's (PDA's) management of personal data files processed by the company using the CADAS system. This applies in particular to the company ability to enforce new rights of data subjects (e.g. rights to: view, forget, move to another administrator, etc.) This functionality ensures:

  1. Unified pseudonymisation of personal data from registered databases. In projects being executed, respondent data is identified with an unique key, which is additionally stored independently in the central database and which is protected by organizational measures preventing third-party access.
  2. Instant look-up of all information related to a specific person by their unique nickname. Other functions of the system can also be used in this context (e.g.: notification of objections during the surveying session, e.g. the “Robinson list” or datasets scanning to list records with fields with specific values). This functionality allows you to quickly respond to requests of persons whose data is processed as well as to efficiently fulfil obligations requiring notification of all interested parties in the event of personal data security breaches.

The decision regarding who in the company should have access to the central database should be made by the company's Data Protection Officer or by another person acting under the authority and on behalf of the PDA (the Personal Data Administrator as defined in the GDPR).