Back to Insights Compliance

Revolutionizing Data Protection: A Guide to Implementing Amendment 13 to the Privacy Protection Law

Background
On August 5, 2024, the Knesset approved the second and third readings of Amendment No. 13 to the Protection of Privacy Law, 5741–1981. The law will take effect one year after its publication and includes a series of comprehensive changes to Israel’s outdated Protection of Privacy Law. This is the most significant amendment to the law since 1996. The amendment updates, among other things, legal definitions to expand the law’s scope; reduces the archaic database registration requirement; mandates certain organizations to appoint a Data Protection Officer (DPO); grants broad enforcement powers to the Privacy Protection Authority, and more. It impacts every organization in Israel that processes personal data. However, the amendment still does not address substantive arrangements established in modern data protection legislation. Absent issues include the expansion of the legal basis for processing beyond informed consent, the granting of data subject rights (such as the “Right to be Forgotten”), the obligation for data minimization, and more.

Key Implications
* Improved organizational understanding and proper handling regarding the collection of personal data and providing data subjects with the right to access their information.
* Expansion of personal data requiring enhanced protection by increasing the types of information to which the law applies.
* Increased compliance necessity due to broader application of legal provisions to any action related to data.
* Option to appoint an organizational representative (a controlling stakeholder or person authorized by the CEO) instead of a Database Manager.
* Revised requirements for Information Security Officer appointments for controlling stakeholders or holders of five databases requiring registration or notification.
* Requirement to appoint a Data Protection Officer (DPO) in specific organizations to improve compliance and protect personal data from exposure and/or compromise.
* Abolishment of the database registration requirement at the Ministry of Justice for most organizations.
* Increased deterrence against failure to protect personal data due to stricter financial sanctions for violations and the expansion of criminal offenses related to private databases.

Improved Privacy Protection: Expanding Definitions and Strengthening Rights

Key Changes in Amendment 13
* Expanding the definition of “Personal Data” and replacing the term “Sensitive Information” with “Highly Sensitive Information.”
* Reducing database registration obligations and replacing them with a notification requirement to the Authority for large and sensitive databases.
* Mandatory appointment of a Data Protection Officer (DPO) in companies, organizations, and public bodies.
* Expanding legal support for the Right of Access (Review).
* Broadening the obligation of notification during personal data collection.
* New prohibitions regarding the unlawful processing of information.
* Expanding the criminal investigation and enforcement powers of the Privacy Protection Authority.
* Expanding court authority to award statutory damages without proof of injury.
* Expanded financial sanctions.
* Authority for courts to issue orders to cease processing or delete information.
* Expansion of criminal offenses related to private databases.

Revised Fundamental Concepts
* Personal Data: Specific types of data related to a person, as well as data concerning an identified or identifiable individual.
* Highly Sensitive Information: Genetic data, biometric identifiers, criminal records, personality characteristic assessments, and location and traffic data.
* Database Owner (Controller): One who, alone or with others, determines the purposes of processing the data in the database.
* Holder (Processor): An external party to the Database Owner who processes information on their behalf.
* Database Manager: The Database Owner. Regarding a public body, the CEO of the body that owns or holds the database, or an individual authorized by the CEO to manage it.

Abolishment of Registration Requirements
The requirement to register databases has been effectively abolished for the private sector, except for organizations engaged in data trading or direct mailing services. Registration remains mandatory in the following cases:
* A public body, excluding databases containing only information about its employees.
* An organization whose primary purpose is collecting personal data for disclosure to others as a business or for consideration, including direct mailing services, if the database contains information on 10,000 or more individuals.
Databases currently registered but not required to be under the new law will remained registered unless the owner requests removal.

Notification Requirement to the Authority
When to notify? For databases containing highly sensitive information regarding 100,000 or more individuals, the Owner must notify the Privacy Protection Authority of the database, provide the DPO’s details (if required), and attach the database definition document.

The Right of Access (Review)
An individual has the right to review the information held about them in a database. This is the primary way for a data subject to verify that their information is being used lawfully. This right is exercised by contacting the organization holding the data. If the organization refuses access, it must provide a justification.

Appointment of a Data Protection Officer (DPO)
The DPO’s role is to ensure that the Database Owner and Holders comply with the law and to promote privacy and information security. The DPO does not have to be an employee. Their reporting line and/or additional roles must not create a conflict of interest.
Mandatory appointment applies to:
* A Database Owner that is a public body or a Holder of a public body’s database (including local authorities and government ministries, excluding security agencies).
* An owner whose primary purpose is data trading or direct mailing for over 10,000 people.
* An owner or holder whose core activities involve processing operations that require regular monitoring of individuals (e.g., cellular companies, online search engines).
* An owner or holder whose core activity is processing highly sensitive data on a large scale (e.g., banks, insurance companies, hospitals, and HMOs).

Responsibilities of the DPO
The DPO serves as a professional authority and knowledge center, advising management and employees, preparing and overseeing training and audit plans, and reporting findings to management. They handle data subject inquiries, ensure information security procedures are in place, and serve as the point of contact for the Privacy Protection Authority. They must possess professional knowledge of privacy laws, technology, and information security. These provisions are substantially similar to those in the GDPR.

Change in the Database Manager Role
The powers of the Database Manager will be transferred to the Database Owner, who may appoint a manager at their discretion. The personal liability of the Database Manager regarding information security under Section 17 of the law will be abolished.

Expansion of Notification Obligations
The amendment expands the duty of disclosure when requesting personal data. The requester must now provide: the name and contact details of the Database Owner; notice of the right to access and correct the data (per Sections 13 and 14); and the consequences of refusing to provide the information.

Financial Sanctions
Non-compliance will result in significantly higher financial sanctions:
* Database registration/notification violations: 150,000 NIS per offense for standard databases; 300,000 NIS for databases with over a million data subjects.
* Regulation-related violations:
* Minor violations: 20,000 NIS (Intermediate security) – 80,000 NIS (High security).
* Standard violations: 40,000 NIS (Intermediate security) – 160,000 NIS (High security).
* Severe violations: 80,000 NIS (Intermediate security) – 320,000 NIS (High security).
* For databases with over one million subjects, all sanction amounts are doubled.

Recommended Compliance Plan
1. Update and draft database definition documents.
2. Redefine data types (Personal / Highly Sensitive).
3. Evaluate and eliminate redundant or unnecessary data.
4. Update collection and notification processes (including Privacy Policies).
5. Separate or merge databases as needed.
6. Update security levels as required.
7. Map current data Holders (Processors).
8. Update privacy policy in accordance with Section 11 duties.
9. Verify the requirement to appoint a DPO and appoint one if applicable.
10. Conduct a Data Protection Impact Assessment (DPIA).
11. Proactively delete redundant database registrations.

Continue the Conversation

Facing a cybersecurity challenge? Let's talk about how a managed program can strengthen your resilience.

Start a conversation