Transferring Personal Data Abroad: What Regulation 2(4) Requires of Foreign Cloud Vendors

Israel’s Privacy Protection Authority published final guidance interpreting regulation 2(4), the contractual pathway for transferring personal data outside Israel. The Authority makes clear there’s no shortcut, and spells out exactly what the recipient must commit to, and what does count as a legitimate "necessary modification."

On April 13, 2026, Israel’s Privacy Protection Authority published its position paper interpreting regulation 2(4) of the Privacy Protection Regulations (Transfer of Information to Databases Outside State Borders), 5761-2001, to guide the exercise of the powers granted to it under the Privacy Protection Law. If your company transfers personal data to cloud providers, SaaS tools, or other services hosted outside Israel, including US providers like AWS, Google Cloud, or Microsoft Azure, this guidance applies directly to you.

Regulation 1 prohibits, regulation 2 opens four pathways

Regulation 1 of the regulations bars transferring personal data from a database in Israel outside the country’s borders, unless the destination country’s law ensures a level of data protection no lower than that required under Israeli law, with necessary modifications. Regulation 2 sets out four additional pathways, which apply "notwithstanding regulation 1," and meeting just one is enough: the data subject’s consent (2(1)); a situation where consent cannot be obtained and the transfer is necessary to protect the person’s health or bodily integrity (2(2)); a transfer to an entity under the database controller’s control, which has ensured privacy protection after the transfer (2(3)); and a transfer to someone who has contractually committed to the controller to comply with the conditions for holding and using data that apply to a database in Israel, with necessary modifications (2(4)). This is the pathway most Israeli tech companies actually rely on when transferring data to a cloud provider or overseas service provider, because unlike regulation 1, it doesn’t depend at all on the destination country, only on a specific, concrete contractual commitment from the recipient.

The key clarification: "necessary modifications" isn’t a safety valve

The position paper focuses mainly on interpreting the phrase "with necessary modifications", and this is the point most worth understanding: the Authority explicitly clarifies that regulation 2(4) will not apply where the recipient in the foreign country doesn’t commit to complying with the conditions for holding and using data that apply to a database in Israel, on the grounds that its own personal or organizational circumstances don’t allow it to do so, and therefore, in its view, that counts as a "necessary modification." This is not a subjective standard. In other words, the fact that a large cloud provider doesn’t typically customize its standard data processing agreements to the specific requirements of foreign law, including Israeli law, does not by itself count as a legitimate "necessary modification" that excuses you from the requirement.

That said, the position paper also recognizes that a full commitment to comply with every condition applying to a database in Israel won’t always be fully achievable in every country, partly given the legal framework in the destination country. It’s also worth stressing: nothing in regulation 2(4), or in how it’s interpreted in the position paper, relieves the controller of an Israeli database, or a holder, of the substantive obligations they’re subject to under the Privacy Protection Law and its regulations, even after the data has already been transferred abroad.

What the agreement with the recipient actually needs to include

An agreement for transferring personal data under regulation 2(4) must include a commitment from the recipient to uphold, toward data subjects, obligations identical or substantially similar to those set out in Israeli privacy law, including:

  • Use limitation, a prohibition on using the personal data for a purpose other than the one for which it was given to the Israeli database controller (sections 2(9) and 8(b) of the law).
  • Data subject rights, a commitment to grant access to the data (section 13 of the law) and the ability to request its correction or deletion (section 14 of the law).
  • Confidentiality regarding personal data that reaches the recipient by virtue of its role (section 16 of the law).
  • Data security, via one of two paths: committing to comply with the substantive obligations under the Privacy Protection (Data Security) Regulations, 5777-2017, subject to regulation 19 regarding holders, or alternatively, declaring and committing that the organization is certified under ISO/IEC 27001, complies with the standard including the relevant controls in Annex A, and meets the obligations under the specific data-security regulations listed in the Authority’s Guideline 3/2018.

The practical implication: a generic data processing agreement (DPA) that a foreign cloud provider offers as a default to all its customers worldwide will often not be enough, by itself, to satisfy regulation 2(4), unless it includes, or is supplemented by an addendum including, these specific commitments. Relying on EU mechanisms like GDPR Standard Contractual Clauses also isn’t automatically equivalent to satisfying regulation 2(4), since this is an independent Israeli pathway that requires concrete alignment with Israeli law’s requirements, not just European ones.

Database registration: an example of a modification that is allowed

Not every gap between Israeli and foreign law disqualifies reliance on regulation 2(4). The position paper gives a concrete example of a modification that will in fact be treated as "necessary": a recipient’s failure to comply with the duty to register a database or notify the Authority, under sections 8a(a) and 8a(b) of the law, will be accepted as a "necessary modification" for regulation 2(4) purposes, so long as the destination country has no similar duty for that type of database. That said, where the Israeli law itself also applies directly to the recipient abroad, for example because its own database is subject to it, it will also be bound by the registration or notification duty.

Data originating in Europe, and what goes beyond the Privacy Protection Law

Where the Israeli database from which data is transferred under regulation 2(4) also contains data that originated in the European Economic Area, the controller needs to ensure the recipient also commits, as part of its overall regulation 2(4) commitment, to the substantive obligations under the Privacy Protection Regulations (Provisions Regarding Information Transferred to Israel from the European Economic Area), 5783-2023. Since January 1, 2025, these regulations also apply to personal data held in an Israeli database alongside data transferred from the European Economic Area, not just to databases dedicated exclusively to European data.

Finally, it’s worth remembering that regulation 2(4) isn’t limited to the Privacy Protection Law and its regulations, but more broadly to the "conditions for holding and using data that apply to a database in Israel." Where other privacy or data-protection laws apply to the transferred data, such as sector-specific rules for finance or health, the recipient must commit to those too, and it’s worth checking whether they include provisions that specifically restrict transferring the data to a foreign country. It’s also worth noting that transferring personal data abroad is separately subject to regulation 3 of the regulations, which addresses onward transfer to an additional country.

So what should you do this week?

  1. Map every foreign vendor that receives personal data from you, including cloud providers, SaaS tools, and subcontractors.
  2. For each vendor, check which pathway under regulation 2 actually applies, and if you’re relying on regulation 2(4), confirm the existing agreement includes all four substantive commitments: use limitation, data subject rights, confidentiality, and data security.
  3. Confirm the agreement includes a clear path to meeting data security requirements, whether through a direct commitment to the data security regulations or through ISO/IEC 27001 certification.
  4. If the data includes information that originated in Europe, confirm the commitment also covers the obligations under the EEA-transfer regulations.
The Authority makes clear that "necessary modifications" isn’t a free pass, and isn’t a subjective standard. A foreign cloud vendor’s commercial constraints don’t make a substantive requirement of Israeli law irrelevant, but the absence of a database-registration duty in the destination country can count as a legitimate necessary modification.

Frequently asked questions

When was the regulation 2(4) position paper published?

It was published on April 13, 2026, to guide the exercise of the powers granted to the Authority under the Privacy Protection Law.

What is regulation 2(4), and how does it differ from regulation 1 and other pathways in regulation 2?

Regulation 1 sets a general prohibition on transferring data abroad unless the destination country's law ensures adequate protection. Regulation 2 sets four additional pathways that apply notwithstanding regulation 1. Regulation 2(4) is the contractual pathway: it allows transferring data when the recipient has contractually committed to comply with the conditions for holding and using data that apply to a database in Israel, with necessary modifications, regardless of the destination country.

Is it enough for the foreign vendor to sign a generic DPA that it gives to all its customers?

Usually not. The position paper makes clear that "necessary modifications" doesn't let the recipient drop substantive Israeli-law obligations due to its own commercial or organizational constraints. A standard generic agreement, without alignment to the specific requirements the paper sets out, will usually fall short.

Is there one obligation that can legitimately be dropped without undermining reliance on regulation 2(4)?

Yes. The Authority clarifies that a recipient's failure to comply with the duty to register a database or notify the Authority, under sections 8a(a) and 8a(b) of the law, will be accepted as a "necessary modification" for regulation 2(4) purposes, so long as the destination country has no similar duty for that type of database.

What does the data security piece require to rely on regulation 2(4)?

There are two alternative paths: the recipient commits to comply with the substantive obligations under the Privacy Protection (Data Security) Regulations, 5777-2017, subject to regulation 19 regarding holders, or declares and commits that the organization is certified under ISO/IEC 27001 and complies with its requirements and the Annex A controls, including the specific regulations listed in the Authority's Guideline 3/2018.

What if the data we transfer includes data that originated in Europe?

If the Israeli database also contains data transferred from the European Economic Area, the controller needs the recipient to also commit to the substantive obligations under the Privacy Protection Regulations (Provisions Regarding Information Transferred to Israel from the European Economic Area), 5783-2023, as part of its regulation 2(4) commitment.

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

Meet your legal department.

Leave your details and Tal will get back to you within one business day. We map what you need, and you leave knowing exactly what it costs.

  • No commitment, no hourly billing
  • A fixed price before any work starts
  • Every output signed off by a lawyer

Prefer to pick a time yourself? Book a call in the calendar

We use these details only to get back to you. Privacy Policy

Thanks, we got it.

Tal will get back to you within one business day.

Leave your details