On July 14, 2026, Israel’s Privacy Protection Authority published its position paper on the duty to appoint a Data Protection Officer (DPO) under Amendment 13 to the Privacy Protection Law. The paper sets out the Authority’s position on the scope of the duty, the officer’s responsibilities, the qualifications required, and the officer’s standing within the organization. The duty itself already took effect on August 14, 2025. It’s one of the most significant changes in the most comprehensive overhaul the law has seen since it was enacted in 1981, and its scope is far wider than most organizations assume. Even if you’ve never thought of yourselves as a “privacy-sensitive organization,” it’s worth checking.
Worth knowing: the Authority will rely on this paper when exercising its powers, including imposing financial sanctions on organizations that fail to comply. It was published after a public-comment draft stage and now represents the Authority’s full position.
Who must appoint a DPO, four triggers, and one is enough
Under section 17ב1(a) of the law, the duty applies to any organization falling into one of four categories. Meeting just one is enough:
- A public body, and any external “holder” processing data on its behalf. Government ministries, local authorities, health funds, hospitals, higher-education institutions, and more. And here’s the part that surprises private organizations most: the duty also applies to any external party processing personal data for a public body, meaning a SaaS vendor, subcontractor, or service provider that stores, processes, or even just views data on behalf of a local authority, government ministry, or health fund counts as a “holder” and must appoint its own DPO, even though it isn’t a public body itself.
- An organization whose main business is trading in personal data, including direct-mail services, with a database covering more than 10,000 people. This targets organizations that collect personal data in order to pass it to others, as a course of business or for consideration.
- An organization whose main business involves ongoing, systematic monitoring of individuals at significant scale. This covers location-tracking apps, health-tracking wearables, smart vehicles and IoT devices, connected security cameras, and profiling for targeted advertising, personalization, credit scoring, insurance underwriting, or fraud detection.
- An organization whose main business involves significant-scale processing of specially sensitive information. The law explicitly names banks, insurance companies, hospitals, and health funds as covered by this trigger, but the Authority is clear this is an illustrative “white list,” not a closed one.
The term “significant scale” (relevant to triggers 3 and 4) has no fixed numeric threshold, the Authority weighs it case by case: number of data subjects, their share of a given population, the volume and variety of data, the duration and frequency of processing, and geographic reach. Even a database with a modest number of data subjects may still count as “significant scale” if the other factors are substantial.
Also worth noting what the law does not require: processing sensitive data only for secondary, ancillary purposes, like ordinary HR administration, does not trigger category 4, unless that processing is directly tied to the organization’s core activity.
Beyond the legal duty: when a voluntary appointment makes sense
The Authority recommends considering a voluntary appointment even for organizations not legally required to make one, particularly “quasi-public bodies” subject to at least some principles of public law. And for everyone else: appointing a DPO under section 17ב1(a)(3) or (4) may earn an organization a 10% reduction on a financial sanction, if one is later imposed for other violations of the law, a direct financial incentive, not just a risk-management consideration.
What knowledge and qualifications the officer must have
The law requires the officer to have “the knowledge and skills required to properly fulfill the role”, a flexible standard assessed against the organization’s profile, but the position paper spells out three areas that must be present:
- Deep, provable command of Israeli privacy law, full and comprehensive mastery of the country’s privacy legislation and regulation: the Privacy Protection Law, case law, regulations, and the Authority’s guidance (not foreign law like GDPR, though familiarity helps in multinational organizations). Acquired mainly through significant hands-on experience, for example as a privacy officer or supporting the organization’s privacy work on the legal side, and preferably supplemented by formal training of at least 40 hours offered or endorsed by the Authority. That training counts as “basic training”, but is neither mandatory nor sufficient on its own without further experience or education.
- Adequate technological understanding of information security and data flows in the organization, not necessarily a computer-science degree, but enough to promote privacy by design, privacy-enhancing technologies, and privacy impact assessments.
- Familiarity with the organization’s business and structure, its areas of activity, division of responsibilities and work processes (especially data-processing flows), corporate structure, and its sector, market, and sectoral regulation. This familiarity can come from prior work in the organization, experience at other organizations in the same sector, or proactive study of the field, and must be enough to identify privacy risks and effectively apply the law, regulations, and privacy principles in everyday processes. Particular attention should also go to vulnerable data-subject populations (minors, the elderly, people with special needs, new immigrants).
What the officer actually does, six statutory duties
Section 17ב2(a) of the law lists six core components of the role:
- Serve as a proactive professional authority and advisor to management and staff, throughout the personal-data processing lifecycle.
- Prepare and lead a periodic training program for employees.
- Prepare an ongoing compliance-monitoring program, and report findings to management, ideally at least annually.
- Ensure the organization maintains and updates a security procedure and a database-definitions document, approved by management.
- Handle data subjects’ requests, access, correction, deletion, opting out of direct mail, and similar rights.
- Serve as the organization’s official point of contact with the Privacy Protection Authority.
Beyond the formal list, the Authority clarifies that the officer’s broader mission is to promote a “privacy culture” within the organization, beyond the legal minimum. The law does not impose personal liability on the officer for violations; the role is advisory, educational, and one of oversight and control, not one that carries the organization’s legal liability.
Two conditions that would disqualify a “paper” appointment
The position paper highlights two status requirements the Authority treats as key indicators of whether an appointment is real, not merely formal:
- Direct reporting to the CEO, the officer must report directly to the CEO, or to an employee who reports directly to the CEO and no one else. Not a deputy CEO, not general counsel, not any other intermediate function.
- No conflict of interest, the officer cannot hold another role, or report to someone, with authority or responsibility over data-processing policy. In particular, this rules out combining the role with positions like marketing manager, customer manager, CFO, IT manager, or CTO.
What about the CISO? Can one person hold both roles?
The position paper addresses this directly: it isn’t categorically prohibited, but the Authority recommends against it in most cases. The reasons: (1) a CISO doesn’t necessarily have the deep privacy-law knowledge the law requires of a DPO; (2) the information-security officer bears personal responsibility for the organization’s security, which can conflict with privacy considerations (e.g., broad employee monitoring for security purposes, which may itself harm privacy); (3) a security officer doesn’t necessarily meet the direct-CEO-reporting requirement; (4) in larger organizations, each role carries enough of a workload to justify a dedicated person. In organizations legally required to appoint a security officer, combining the roles is especially problematic.
Placing the DPO in the legal department: possible, but handle with care
Placing the officer within the legal department is possible, as long as it does not create a conflict of interest. That said, the Authority stresses this will not necessarily deliver the best result, because of the fundamental difference between the role of legal counsel (ensuring compliance with the law) and that of the DPO (advancing privacy protection beyond the legal minimum), and because of the difference in the knowledge and skills each requires. If the role is nonetheless given to someone who also serves as legal counsel, the officer must take organizational measures that clearly separate the two hats, for example a separate signature in the DPO capacity, or a dedicated email address for data-protection matters only.
Internal or outsourced, and what to do now
The law explicitly permits engaging the officer as an external service provider, being a salaried employee isn’t mandatory. An in-house officer is generally preferable for closer familiarity and availability, but for many organizations, especially small and mid-sized ones, outsourcing is the practical path, as long as the officer is given the time, access, and resources the role requires.
So what should you do this week?
- Check which of the four triggers might apply to you, with particular attention to the “holder” question if you serve a public-sector client, and to the scale of sensitive or monitored data you process.
- If the duty applies, decide between an internal appointment or an external DPO-as-a-service, and confirm the candidate meets the knowledge requirements.
- Confirm the reporting line runs directly to the CEO, and that there’s no built-in conflict of interest in the role.
- If you’re not sure whether the duty applies to you, a one-time, structured assessment beats assuming it doesn’t.
The broad reach of the “holder” trigger for public-sector work, and the flexible definition of “significant scale,” mean far more organizations are covered than most assume.
Frequently asked questions
When exactly did the DPO appointment duty take effect?
Amendment 13 to the Privacy Protection Law was approved by the Knesset on August 5, 2024, and all its provisions, including the DPO appointment duty, took effect on August 14, 2025. The draft position paper interpreting the duty was published for public comment on July 23, 2025, and the position paper was published on July 14, 2026. The Authority has said its interpretation guides its enforcement decisions, including the imposition of financial sanctions.
We’re a small-to-mid-size private company, are we required to appoint a DPO?
It depends on whether you meet one of the law’s four triggers: being a public body or a “holder” processing for one; trading in data or providing direct-mail services covering more than 10,000 people; ongoing, systematic monitoring at significant scale; or significant-scale processing of specially sensitive data. Company size itself isn’t the test.
What exactly is an external “holder” that must appoint a DPO even though it isn’t a public body?
Any external party, a SaaS vendor, contractor, or service provider, that processes personal data on behalf of a public body (a government ministry, local authority, health fund, etc.) is considered a “holder” of that body’s database, and so is itself required to appoint a DPO, even if it’s a fully private company.
Can an organization’s CISO also serve as its DPO?
The law doesn’t categorically ban it, but the Authority recommends against combining the roles in most cases, due to knowledge gaps, conflict-of-interest risk, and the direct-CEO-reporting requirement that a security officer doesn’t always meet. In organizations legally required to appoint a security officer, combining the roles is especially problematic.
Can the organization’s legal counsel also serve as the DPO?
Yes, provided there is no conflict of interest. But the Authority stresses that placing the DPO in the legal department is not necessarily optimal, given the difference between legal counsel (ensuring compliance) and the DPO (advancing privacy beyond the minimum). If one person holds both roles, they must take organizational measures to separate the two hats, such as a separate signature in the DPO capacity or a dedicated email address for privacy matters only.
Can we use an external DPO instead of appointing an in-house employee?
Yes. The law explicitly permits engaging the officer as an external service provider, as long as they’re given the time, access, and resources the role requires.
What counts as “significant scale” for the appointment duty?
There is no fixed numeric threshold. The Authority weighs the full circumstances: the number of data subjects and their share of a population, the volume and range of data types, and the duration and frequency of processing. Even a database with a modest number of data subjects may count as significant scale if the other factors are substantial.
What happens to an organization that is required to appoint a DPO but does not?
The duty took effect on 14 August 2025, and the Authority will rely on its position paper when exercising its powers, including imposing financial sanctions. Conversely, appointing a DPO under the monitoring or sensitive-data triggers may even earn a 10% reduction on a sanction imposed for other violations.
The above is general information only and does not constitute legal advice. For guidance tailored to your specific circumstances — talk to us.
Sources
Want to know what applies to your company?
Talk to us