Data Protection in Georgia

Registration in Georgia

The Data Protection Law does not establish an indiscriminate system for registration or notification of data processing activities, however, controllers and / or processors may need to consult Personal Data Protection Service in specific cases after conducting a data protection impact assessment (Article 31), or submit registered processing activities to the Personal Data Protection Service on its request (Article 28), or notify Personal Data Protection Service of incidents which have a potential to cause significant damage and / or pose a significant threat to fundamental human rights and freedoms (Article 29). Also, controllers and processors are required to notify the Personal Data Protection Service about their data protection officer (if one is appointed) under Article 33.

In light of the above, it is evident that the Law prioritizes internal accountability over external mechanisms like registration. For instance, under Article 28 (as stated above) controllers and processors are required to keep comprehensive records of their data processing activities. These records, detailing key aspects of the processing within the organization, must be provided to the Personal Data Protection Service upon request. This approach places a substantial operational responsibility on organizations. To be more precise:

In case of keeping internal logs of data processing activities (Article 28), the controller (and its registered representative, in case one is appointed) is obligated to ensure, in writing or electronically, the internal registration of the following data processing information on: 

  1. the identity / name and contact details of the controller, special representative, personal data protection officer, joint controller, and the processor; 
  2. the objectives of data processing; 
  3. the data subjects and the data categories; 
  4. the categories of data recipients (including the categories of data recipients from another state or international organization); 
  5. the transfer of data to another state or international organization, as well as appropriate guarantees of data protection, including a permit from the Personal Data Protection Service (if any); 
  6. the periods of data storage, and where such periods cannot be specified, the criteria for determining the periods of storage; 
  7. a general description of the organizational and technical measures taken for ensuring data security;
  8. information on incidents (if any). 

Furthermore, a processor is obliged to ensure, in writing or electronically, the internal registration of the following data processing information on: 

  1. the name and contact details of the processor, personal data protection officer, controller, joint controller, and special representative; 
  2. the types of data processing carried out for or on behalf of the controller; 
  3. the transfer of data to another state or international organization, as well as appropriate guarantees of data protection, including a permit from the Personal Data Protection Service, if processor participates in the process of transferring data to another state or international organization; 
  4. a general description of the organizational and technical measures taken for ensuring data security; 
  5. information on incidents (if any).

A controller, co-controller, processor and a special representative are obligated to provide to the Personal Data Protection Service with the information provided for above immediately upon request, but not later than 3 working days after a request.

When it comes to the incidents as stated above (Article 29), the controller is obliged to register an incident, its resulting outcome, the measures taken, and to notify the Personal Data Protection Service about the incident, not later than 72 hours after the identification of the incident, in writing or electronically, except for the case where it is least expected that the incident would cause significant damage and / or pose a significant threat to fundamental human rights and freedoms. Furthermore, a processor is obliged to notify a controller immediately about an incident. (for more, see below Section on Breach Notification).

As for the consultation with the Personal Data Protection Service during the conducting of impact assessment (Article 31), If, as a result of a data protection impact assessment, a high risk of violation of fundamental human rights and freedoms is identified, a controller is obliged to take all necessary measures to mitigate the risk substantially, and where necessary, address the Personal Data Protection Service for consultation. Where the threat of violation of fundamental human rights and freedoms cannot be mitigated by taking additional organizational and technical measures, the data processing shall not be carried out.

Over the course of consultation with the Personal Data Protection Service on the basis of above a controller needs to submit:

  1. information on the authority of the controller, joint controller and a processor;
  2. information on the purposes and means of the planned data processing;
  3. information on security measures for protecting the rights and freedoms of a data subject;
  4. the contact details of a personal data protection officer (if any);
  5. data protection impact assessment;
  6. other (additional) information in the event of a request by the Personal Data Protection Service.

As evident from all the articles mentioned above, the authority is consulted only in specific exceptional cases where there is a potential risk to the rights and freedoms of data subjects. Otherwise, data privacy activities and related protective measures are largely managed and implemented internally.

Back to top