Data recently published in Globes from the Israeli Privacy Protection Authority (PPA) should be top of mind for every executive team and board in Israel.
Since Amendment 13 to the Privacy Protection Law entered into force, regulatory enforcement has shifted from theory into aggressive execution:
- 178 supervision, inquiry, and audit proceedings have already been initiated.
- 158 of those cases remain actively open.
- ~244 cross-sector enforcement audits are running in parallel.
To be accurate: these figures do not automatically translate into 178 fines. Instead, they represent active enforcement and inspection proceedings at various stages. Yet amidst all the boardroom concern over administrative sanctions and expanded enforcement powers, there is a strategic mechanism built directly into Amendment 13 that is getting almost zero attention.
The Overlooked Tool: Preliminary Opinions (Section 17T2)
Under Section 17T2 of the amended law, a database controller, a processor, or an entity preparing to become one can formally apply to the PPA for a Preliminary Opinion regarding whether a planned database and its data processing activities comply with the law and its regulations.
Why does this matter right now?
Consider a common scenario: your company is preparing to launch a new AI system that processes customers’ personal data. Your engineering team has already built the architecture, and leadership is eager to go to market. However, there is a substantial, unresolved legal question regarding the legality of how that data is processed.
Instead of ignoring the gray area, or waiting to become Case #179 in a PPA audit, your organization can evaluate whether to proactively consult the regulator before launch.
A Global Shift: From Punitive Audits to Pre-Launch Dialogue
Israel is not alone in creating proactive compliance channels. Across leading privacy jurisdictions, regulators are increasingly recognizing that complex technologies like AI require structured, pre-launch legal clarity rather than purely reactive enforcement:
- In the UK: The Information Commissioner’s Office (ICO) operates an active Regulatory Sandbox, allowing organizations developing innovative products that rely on personal data to engage directly with regulatory teams and resolve complex compliance questions before going live.
- In the European Union: Under Article 57 of the EU AI Act, member states are establishing AI Regulatory Sandboxes designed to give tech companies controlled regulatory guidance and legal certainty prior to market deployment.
While Israel’s Section 17T2 is not an ongoing technical “sandbox” environment, it functions as a targeted regulatory pre-ruling mechanism. The underlying philosophy is identical: smart regulation rewards organizations that surface legal ambiguities early, rather than gambling on compliance after launch.
Why New Tech Launches Require Early DPO Governance
This is precisely where the role of a Data Protection Officer (DPO) becomes critical. An effective DPO is not someone who pulls the emergency brake five minutes before production deployment. An effective DPO is embedded in the planning phase, surfacing the right questions so the business can move forward responsibly.
Before launching a new system or AI product, every organization and DPO should run through a 5-point pre-launch checklist:
- Purpose Definition: Have the exact purposes of data processing been clearly defined?
- Legal Basis: Is there a solid, defensible legal justification for the planned processing?
- Data & Risk Mapping: Have all data types, recipients, and privacy risks been thoroughly mapped?
- Legal Ambiguity: Is there a substantial legal question that has not received a clear answer in existing law or PPA guidelines?
- Pre-Launch Escalation: Should the organization consider applying for a Preliminary Opinion before launch?
How the Preliminary Opinion Process Works in Practice
It is essential to set realistic expectations: a Preliminary Opinion is not a blanket approval for a product, does not replace an organization’s ongoing statutory obligations, and not every scenario is suitable for the process. Furthermore, the PPA will not issue an opinion where a clear regulatory position already exists, or when the request relates to an active, pending enforcement proceeding.
According to the official PPA Preliminary Opinion Guidelines, a generic inquiry asking “Does our system comply with the law?” will not suffice. A valid application must include:
- Precise Legal Framing: An exact definition of the specific legal question at issue.
- Legal Interpretation: A detailed legal analysis addressing that question.
- Full Factual Disclosure: A complete description of all relevant technical and operational facts.
- Supporting Evidence & Affidavit: Relevant documentation accompanied by a formal declaration verifying the accuracy of the facts.
- Prior Regulatory History: Information on any previous inquiries or proceedings connected to the matter.
Under Section 17T2(c) of the law, the PPA is required to issue its opinion within 60 days from receiving the complete application or supplementary documents (subject to extensions in special circumstances).
While this mechanism isn’t meant for every minor technical update, knowing when and how to utilize it, alongside reviewing previously published PPA Preliminary Opinions for guidance, is the exact difference between reactive compliance and true Privacy by Design.
The Pre-Launch DPO Test
Amendment 13 was not designed solely to penalize violations. It also provides structured tools to manage compliance questions before they escalate into enforcement actions.
Ask your leadership team this week:
In your organization, is the DPO involved in decisions around new products and technologies before development begins, or only when the system is already built and waiting to go live?
Go to the official PPA Preliminary Opinion Application Form: Ministry of Justice Portal


