Consent Under Israeli Privacy Law: What the New Guidance Changes

Israel’s Privacy Protection Authority published final guidance on consent. Formal compliance with the letter of the law is no longer enough, consent is now assessed both on content and presentation (informed consent) and on genuine free will. Here’s what it means for your website, app and sign-up forms.

On February 25, 2026, Israel’s Privacy Protection Authority published the final version of its position paper on consent under privacy protection law, following a public-comment draft process. It’s one of the most comprehensive position papers the Authority has issued, and it reflects the legal interpretation the Authority will rely on when exercising its powers, including supervision, database registration and financial sanctions. Its core message is simple to state but far-reaching in practice: formally complying with the letter of the law no longer guarantees that the consent you collected will be considered valid. The paper itself doesn’t address when consent is required in the first place, only how any consent, for any purpose, must be obtained to count as valid.

This isn’t a theoretical point. If you run a website, an app, a sign-up form, a cookie banner, or a privacy policy that relies on user “acceptance,” it’s worth checking whether your mechanism meets the new standard.

Meeting the notice duty is only the starting point

Section 11 of the Privacy Protection Law, 5741-1981, sets a baseline notice duty whenever someone is approached to collect personal data meant to be included in a database. Under the position paper, the person must be told:

  • Whether there is a legal obligation to provide the information, or whether providing it depends on their consent.
  • The purpose for which the information is sought.
  • Who will receive the information and for what purpose.
  • The consequences of declining to provide the information (a duty added by Amendment 13 to the law).
  • Their right to access information about them, under section 13 of the law.
  • Their right to request correction of the information, or to have it deleted if it’s inaccurate, incomplete, unclear or outdated, under section 14 of the law.

This is a familiar list, and many organizations assume that once it appears in a privacy policy or sign-up form, “we’ve done our part.” The position paper makes clear that’s a mistake: meeting the section 11 requirements is only a minimum for the notice duty, and does not by itself guarantee that the consent obtained will be considered “informed.” There’s more: Amendment 13 also added section 8(d)(1) to the law, which bars processing personal data that was created, received, accumulated or collected in violation of the law or any other data-processing law, including data collected without valid consent or another legal basis. In other words, defective consent isn’t just a theoretical problem, it can make the entire collection unlawful.

Informed consent: it’s about what you disclose, and how

Section 3 of the law requires that consent to a privacy intrusion, whether given expressly or implied, be “informed.” Under the position paper, this test has two layers: content, meaning whether the data subject was given the information they reasonably need to decide whether to consent, and presentation, meaning whether that information was presented clearly, accessibly, simply and understandably.

On the content layer, a consent request that doesn’t adequately spell out the types of data collected and the purposes of use, including vague language like “and so on” or “among other things,” may fail the informed-consent test. On the presentation layer, a site whose privacy policy or terms of use aren’t reasonably accessible, or are presented in a convoluted, lengthy, hard-to-follow way, may be found not to have established informed consent, even if every formal detail is buried in the text somewhere.

Case law the position paper cites sets a two-stage test for whether consent is valid: first, whether the practice at issue is expressed clearly in the terms of use, so that a reasonable person could understand it from reading them; and second, how consent is actually obtained in practice, how the user is directed to the terms of use, and how they’re actually required to confirm it.

Also worth knowing: where there’s a significant power imbalance between the parties, the action carries potential for serious privacy harm, or it involves new technology whose implications aren’t yet clear, the informed-consent duty becomes heightened: the party seeking consent must prominently and simply present all material data relevant to the decision, beyond the section 11 minimum.

Free will, and when consent is treated as “suspect”

Alongside the informed-consent requirement sits a separate, independent one: by its nature, consent to a privacy intrusion must be given out of free will. Where there’s a power imbalance between the parties, for example in an employment relationship (including with job candidates), consent given within a consumer-monopoly relationship, or consent required to receive an essential service (public transport, health services, or an essential technology service), the consent may be treated as “suspect,” meaning there’s doubt whether, and to what extent, it can be seen as truly, freely given. In that situation, the burden of showing that consent was given freely may shift to the party that requested it.

To show that consent reflects a genuine choice, the party seeking it can take steps such as offering a reasonable alternative, or not conditioning the service on consent to collect data that isn’t actually needed to provide it. The existence of a reasonable alternative from another provider in the market can also be a fair answer to a claim that consent wasn’t free. That said, where a person genuinely cannot decline the action intruding on their privacy, it will be hard to see their consent as freely given, whether express or implied. Conversely, consent may still be valid even where the data subject has no other practical alternative, as long as the data is genuinely necessary to provide the very service they’re asking for.

No more blanket consent for any future use

The position paper stresses that consent given for one purpose does not, by itself, authorize using the data for other purposes, a principle set out in sections 2(9) and 8(b) of the law. The further a use strays from the primary purpose for which the data was collected, for example targeted advertising, profiling, or personalization, the more the organization needs specific, separate consent for that use, rather than relying on general language in a privacy policy. Where a service seeks to collect data for a purpose materially different from its core business, that must be given prominence within the presentation of usage purposes, separated as much as possible from the rest of the terms, before consent is obtained.

Express, implied, and active vs. passive consent

Consent can be given expressly (a signature, clicking “I agree,” a verbal statement) or implicitly, meaning inferred from the circumstances and a person’s conduct. In the digital context, continuing to browse a site after the information needed for informed consent has been shown will generally count as implied consent to the data collection. That said, courts have repeatedly narrowed reliance on implied consent: sharing certain details with one party doesn’t imply consent to disclosing them to another, and leaving an email inbox open on a computer doesn’t imply consent for someone else to read the messages.

Given that, even where relying on implied consent is legally possible, it’s preferable to seek express consent, particularly when collecting sensitive data or taking an action that could seriously harm privacy. Silence or the absence of an objection, on their own, cannot establish valid consent, unless there are circumstances indicating the data subject genuinely intended to consent and had the awareness needed to do so.

Beyond that, where an agreement includes clauses seeking consent to collect data not needed to provide the service, or to use data for a purpose materially different from the agreement’s main purpose, the position paper recommends that the separate consent for that be obtained in an active format (a dedicated checkbox, opt-in) rather than a passive one (failing to check an objection box, opt-out). And there are two situations where the Authority’s position is that passive consent isn’t enough at all: consent to use data for “profiling” not directly tied to the service’s core purpose, particularly where there’s a power imbalance, and consent to direct-mail services unrelated to the purpose of the underlying transaction.

Manipulative design (“dark patterns”)

The position paper also addresses design tools and “dark patterns” meant to make it harder for a data subject to understand what they’re agreeing to and to improperly influence their decision, not just the wording itself: misleading timing, disrupting the normal flow of use to extract consent, or an interface that makes it hard to understand how to decline. For example, a children’s game app that repeatedly “pops up” a location-data request during gameplay, freezes the game, and offers no simple way to dismiss the recurring prompt, may be found to use a dark pattern. Using such techniques can itself indicate that consent wasn’t given knowingly or out of genuine free will.

Minors and other vulnerable populations

Where consent is directed at populations with particular characteristics, especially where a service or product primarily targets such a population (for example minors, or people with disabilities who cannot consume the information in the standard way), the organization must adapt how it presents information so it genuinely enables understanding, not just a formal presentation identical to what the general public gets.

What about withdrawing consent?

This is a point worth handling carefully rather than generalizing. As a rule, withdrawing consent stops future use of data for the purpose that consent covered, and doesn’t affect the lawfulness of collection and use that preceded it, so long as those were lawful. Whether withdrawal also requires immediate deletion of everything already collected depends on the circumstances and other obligations the organization is subject to, such as regulatory duties, information-security retention needs, or defending legal rights. The Authority recommends granting withdrawal requests wherever possible, even where consent wasn’t contractually revocable to begin with, particularly where continued use would seriously harm the requester’s privacy and the organization can’t point to a legitimate, significant interest in continued processing. Before setting a blanket internal policy on this, it’s worth checking your specific circumstances.

So what should you do this week?

  1. Map every point where you collect consent, on your site, app, and forms, and confirm each one is clear, specific, and written in language the data subject genuinely understands, without “and so on” or “among other things.”
  2. Update your privacy policy and user agreements to remove blanket language, and distinguish between the primary purpose and secondary uses (marketing, profiling, direct mail) that require active, separate consent.
  3. Make sure a convenient withdrawal mechanism exists, one that isn’t harder to use than the process of giving consent in the first place.
  4. If you deal with populations facing power imbalances, minors, or other vulnerable groups, have a professional review your consent mechanism before relying on it.
A checked box isn’t automatically valid consent. The Authority now looks at what happened behind the checkbox: whether the information was properly presented, and whether the choice was genuinely free.

Frequently asked questions

When was the consent position paper published, and what preceded it?

The final version was published on February 25, 2026, after the Authority had earlier published a draft for public comment. It’s considered one of the most comprehensive position papers the Authority has issued, and it reflects the legal interpretation the Authority will rely on when exercising its powers, including imposing financial sanctions.

We already comply with Section 11 of the law, isn’t that enough?

Meeting the Section 11 notice duty is a necessary minimum, but not sufficient on its own. The Authority also examines whether consent was actually given with genuine understanding and free will, not just whether the formal disclosures were shown.

What is “suspect consent,” and when is it relevant to our organization?

Consent may be treated as “suspect” where there’s a power imbalance between the organization and the data subject, for example in an employment relationship with employees or candidates, dependence on a vendor with monopoly-like standing, or where consent is required to receive an essential service. In that situation, the burden of proving consent was freely given may shift to the organization.

Can we still rely on implied consent, like continued browsing on our site?

Sometimes, but courts have repeatedly narrowed reliance on it, and silence alone isn’t enough. The Authority recommends preferring express, active consent wherever possible, particularly for sensitive data or actions that could seriously harm privacy.

When is active, separate consent (opt-in) required, rather than a general consent?

Under the Authority’s position, active, separate consent is required specifically for using data for profiling not directly tied to the service’s core purpose, especially with a power imbalance, and for consent to direct-mail services unrelated to the purpose of the underlying transaction.

Someone asked to withdraw their consent, do we have to delete all their data immediately?

Withdrawing consent generally stops future use of data for the purpose that consent covered, but whether it also requires immediate deletion of already-collected data depends on the circumstances and other obligations you’re subject to, like regulatory duties, information security, or defending legal rights. It’s worth reviewing this carefully before setting a blanket policy.

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