Israel PPL
Protection of Privacy Law, 5741-1981 — Knesset
Also known as: Protection of Privacy Law, Privacy Protection Law, Israel PPL 2025, Amendment 13
At a glance
- Status
- In force
- Next deadline
- None announced
- Who must comply
- Anyone who infringes another's privacy, and every controller and processor of a "database": personal data processed digitally, except collections for personal non-business use or contact-only lists (name, address, contact details) of up to 100,000 people. source
- How it is assessed
- Controllers comply on their own. source
- Authority
- Enacted by the Knesset. The Privacy Protection Authority, led by a Head appointed by the government, supervises compliance for databases, inspects, issues orders and imposes monetary sanctions; courts hear criminal cases and civil privacy claims. source
- Enforced by
- Since Amendment 13 the Head of the Privacy Protection Authority can impose fixed monetary sanctions (Article 23KF). source
- Last change
- None recorded yet
Israel's general data protection statute. It governs the registration and operation of databases holding personal information, the duties of database owners and holders, and the rights of the individuals whose data they process. Its enforcement side gives the Privacy Protection Authority administrative fining powers and adds a data protection officer requirement for large and sensitive processors.
Recent changes
No changes recorded yet — we are watching, and nothing has been published.
Key dates
No upcoming datesAmendments
-
Amendment No. 13 (5784-2024) AmendmentCurrent text
The most comprehensive overhaul of Israeli privacy law since 1981, approved by the Knesset on 5 August 2024 and in force since 14 August 2025. source
More
- It updated the core definitions (personal data, and "data of special sensitivity" replacing the earlier "sensitive information"), significantly narrowed database registration (now data brokers and public bodies, plus a notification duty for large databases of especially sensitive data), introduced for the first time a duty to appoint a data protection officer, extended the Authority's supervision and administrative inquiry powers, gave it power to impose monetary sanctions, and widened compensation without proof of damage.
-
—
Protection of Privacy Law, 5741-1981 Major version
The original statute: privacy infringement as a civil wrong and a criminal offence, plus the database chapter. source
Who it applies to
Chapter B applies to anyone who controls or processes a database of personal data in digital form.
- Privacy infringement
- Chapter A protects everyone against privacy infringements such as surveillance, publishing private matters or using information for a purpose other than the one it was given for. source
- Contact lists
- A contact-only list of up to 100,000 people is not a database only if it reveals nothing more about them and its owner holds no other collection with further details on the same people. source
- Registration
- Registration with the Authority is required only for databases whose main purpose is selling or supplying data (over 10,000 people) and for most public-body databases. source source
- Notification
- Other controllers holding data of special sensitivity on more than 100,000 people must notify the Authority instead. source source
- Special sensitivity
- "Data of special sensitivity" covers intimate and family life and sexual orientation, health and medical data, genetic data, biometric identifiers, ethnic origin, criminal record, political or religious views, personality assessments, location and communication data, salary and financial activity, and data confidential by law. source
How compliance is assessed
Controllers comply on their own.
- Certification
- There is no certification. source
- Registration
- Register or notify the database where Article 8A requires it. source
- Data security
- Keep a database definitions document and meet the Privacy Protection (Data Security) Regulations, 5777-2017, which set basic, medium and high security levels by database type. source source
- Data protection officer
- Appoint a data protection officer where Article 17B1 requires one - public bodies, data brokers with over 10,000 people, and organisations whose core activity is large-scale systematic monitoring or large-scale processing of especially sensitive data (for example banks, insurers, hospitals, health funds, mobile operators and search engines). source source
- Data security officer
- Bodies with five or more registrable databases, public bodies, banks, insurers and credit rating firms also need a data security officer. source
- Preliminary opinion
- A controller may ask the Authority for a preliminary opinion on compliance, due within 60 days (Article 17I2). source
Enforcement and penalties
Since Amendment 13 the Head of the Privacy Protection Authority can impose fixed monetary sanctions (Article 23KF).
NIS 150,000
Registration and notification failures; doubled where the database holds data on 1,000,000 or more people. source source
NIS 50 per person approached (NIS 100 for especially sensitive data), at least NIS 30,000
Collecting data without the required notice or unlawful direct mailing. source source
NIS 2 per person in the database (NIS 4 for especially sensitive data), at least NIS 20,000 (NIS 40,000)
Failures such as not appointing a data security officer, or - for public bodies and data brokers only - not appointing a DPO. source source source
- Continuing violations
- Continuing violations add 1% per day. source
- Reductions
- Sanctions are reduced for micro and small enterprises and capped at 5% of turnover on request. source
- Publication
- Every sanction is published on the Authority's website. source
- Inspection
- Authority inspectors can demand information, documents and computer material and enter premises where a database is kept (a residence only by court order). source
- Criminal offence
- Wilful privacy infringement is a crime punishable by up to five years' imprisonment. source
- Court damages
- Courts can award statutory damages of up to NIS 50,000, index-linked (double where intent to harm is proven), and up to NIS 10,000 without proof of damage for specific database breaches such as refusing access or running an unregistered registrable database. source
Documents
- Law text Privacy Protection Law, 5741-1981 - unofficial English translation updated after Amendment 13 (Privacy Protection Authority)
- Guidance Privacy Protection Authority position paper on appointing a DPO under Amendment 13 (Hebrew, 14 July 2026)
- Guidance Privacy Protection Authority professional guide to Amendment 13 (Hebrew, May 2025)
- Law text Protection of Privacy Law on the Knesset legislation database (Hebrew)
Frequently asked questions
When did Israel's privacy law Amendment 13 take effect?
On 14 August 2025. All provisions of Amendment 13, including the duty to appoint a data protection officer and the Authority's power to impose monetary sanctions, entered into force that day. source
When was Amendment 13 to the Protection of Privacy Law passed?
The Knesset approved it on 5 August 2024 as the Protection of Privacy Law (Amendment No. 13), 5784-2024. The Privacy Protection Authority calls it the most comprehensive update of Israeli privacy law since 1981. source
Who must appoint a data protection officer in Israel?
Public bodies and their processors; data brokers holding data on more than 10,000 people; and controllers or processors whose core activity is large-scale systematic monitoring of people or large-scale processing of especially sensitive data, such as banks, insurers, hospitals and health funds (Article 17B1). A monetary sanction for not appointing one applies to public bodies and data brokers: NIS 2 per person in the database (NIS 4 for especially sensitive data), at least NIS 20,000 (NIS 40,000). source
What are the fines under Israel's Amendment 13?
Fixed administrative sanctions set by the law, not a percentage of turnover. Examples: NIS 150,000 (NIS 300,000 for databases of 1,000,000+ people) for registration failures; NIS 50 per person approached (NIS 100 for especially sensitive data), at least NIS 30,000, for collecting data without proper notice; NIS 2-8 per person in the database, with minimums from NIS 20,000 to NIS 200,000, for failures such as a missing DPO (public bodies and data brokers) or unlawful processing; NIS 300,000 for withholding documents from an inspector; and Third Schedule amounts for breaching the Data Security Regulations. They can be reduced to 5% of turnover on request. source
Does Israel have an EU adequacy decision?
Yes, for automated processing: Commission Decision 2011/61/EU covers personal data transferred to Israel for automated processing. The Commission's January 2024 review concluded that Israel continues to provide an adequate level of protection for data transferred from the EU. source
Do Israeli databases still have to be registered?
Only some. After Amendment 13, registration is required for databases whose main purpose is supplying data to others (over 10,000 people) and for public-body databases; controllers with especially sensitive data on more than 100,000 people must notify the Authority instead. source
Verified against official sources on 17 October 2026. We monitor the official sources for this framework. Watching since 20 September 2026. Subscribe to Israel PPL (RSS)