DPO DPO Israel
Open as Markdown
I live on a kibbutz. This service was written from the inside.

DPO for Kibbutzim

Amendment 13 implementation for kibbutzim and cooperative societies — led by a Data Protection Officer with deep kibbutz experience, himself a kibbutz member.

The service covers the three core components of compliance: mapping the kibbutz data registers, annual training for employees and role-holders, and ongoing compliance checks — from community management to the clinic, education, and CCTV.

Kibbutz member · First call free · No commitment

Data protection officer for kibbutzim — guarding the data, protecting the community
How it works

Our work process with kibbutzim

01

On-site mapping

The privacy consultant comes to the kibbutz — several sessions, online also possible — to precisely map the data registers and information systems.

02

Gap survey and recommendations

The kibbutz management (or the client) receives a presentation with a gap survey and recommendations. The survey can also be presented by the privacy consultant in person.

03

Verifying the gaps are closed

After the recommendations are implemented, the consultant verifies that every gap has actually been closed.

04

Course and certificates

Role-holders in the kibbutz complete our e-learning course, and everyone who finishes receives a certificate.

05

Ongoing accompaniment

The course is retaken every two years, and once a year the privacy consultant visits the kibbutz to check that no new gaps have opened and no new vulnerabilities exist.

24/7

Emergency — data leak

In an emergency involving a leak of sensitive data, the Data Protection Officer is available 24/7 to advise on the correct next steps for Amendment 13 compliance. More on incident response

From the field

Where Amendment 13 meets everyday kibbutz practice

Patterns that repeat across many kibbutzim. The details differ from one kibbutz to another — the duties under Amendment 13 to the Privacy Protection Law are the same.

Event sign-ups

Kibbutz databases circulate freely and are very exposed. For example, in event sign-ups ("summer party", "health day" or any other event), many kibbutzim simply publish an Excel/Google Sheets file with residents' names, and people fill in their number of participants. This is an example of data exposure (residents' details, where they live) that our Data Protection Officer raises in the gap survey — and resolves with correct solutions, in full compliance, adapted to the kibbutz and how it operates.

Committees

An absorption-committee protocol with personal impressions of a family, or a welfare discussion about a member in hardship — emailed to a wide list because "that is how it has always been done". Transparency about decisions is a kibbutz value; exposing personal details is a matter of law. The arrangement: separate the published decision from the details that stay in committee, plus a short briefing for the chairs.

Education

The allergy list on the kindergarten fridge, end-of-year photos going up on the website, assessments passed around by email. Data about minors is sensitive data under Amendment 13, with higher security requirements. We set how it is stored, how it moves and who sees it — without slowing down the daily work of the kindergartens and school.

HR and branches

Contracts, salaries, evaluations and medical certificates — sometimes in a shared folder every branch manager can open. Employee and medical data are among the most sensitive under the law, and the duties fall on the kibbutz as an employer. Role-based permissions and access logging — a small technical change, a big compliance win.

Check where your kibbutz stands on Amendment 13

Kibbutz secretaries, community managers, committee chairs — a free 30-minute intro call, and you'll know where you stand and what the first steps are.

Or directly: 054-871-9609 · WhatsApp

Data registers

Typical kibbutz data registers and their sensitivity tiers

This is what we map in the first phase — and the sensitivity tier each register gets. Each register also requires a database definitions document per the Authority's requirements.

Register Sensitivity
Kibbutz members Basic – Medium
Welfare High
Kibbutz clinic Special-sensitive
Education — kindergartens & school High
Branch employees Medium
Absorption High
CCTV Medium – High
Kibbutz corporations & factories Varies
Expansion / residential neighborhood Medium

Amendment 13 for kibbutzim — FAQ

Must a kibbutz appoint a Data Protection Officer?

Amendment 13 applies to every Israeli entity that processes personal data, and a kibbutz processes personal data at scale — members, children, employees, clinic patients, welfare applicants. A kibbutz is a cooperative society, not a public body, so the automatic DPO obligation does not apply; but if it processes sensitive personal data on a large scale (members + welfare + health + education + minors) — which is almost always the case — it falls under the category that triggers the obligation to appoint a DPO. Full guide: who must appoint a DPO.

Does it matter whether the kibbutz is renewing, cooperative, or hybrid?

Mostly for the scope of work. A cooperative kibbutz (~12%) has one central member database — concentrated and easier to control. In a renewing kibbutz (~76%) each household is an economic unit: distributed registers, asset allocation, individual salary data — that is where most of the regulatory complexity sits. A hybrid kibbutz runs both models in parallel. The legal duties are identical in all three — only the mapping effort changes.

What about kibbutz corporations — factories, agriculture, subsidiaries?

A commercial entity owned by the kibbutz is a separate legal person. If it is a vendor to a public body, trades in data, or processes sensitive data at scale — it requires its own DPO. Most large kibbutz factories already qualify, even if the kibbutz itself does not.

Brit Pikuach audit circular 55/19 — is it still relevant?

Partially. The June 2019 circular charted a useful path for database mapping and security tiering. But it predates Amendment 13 — it does not mention the DPO obligation, the new monetary penalties (hundreds of thousands to millions of NIS), or the personal liability of decision-makers. A kibbutz that relies only on the 2019 baseline does not meet Amendment 13.

Kibbutz CCTV — what does Amendment 13 say?

A camera in a kibbutz public space is a database. You need: visible signage, a defined and proportionate purpose, a matching security tier, and a retention and deletion policy. In a kibbutz it is especially sensitive because cameras also capture children who are not members (expansion residents, visitors) — which mandates a higher security tier.

Who in the kibbutz should be the Data Protection Officer? The secretary? The community manager?

Neither. Both the secretary and the community manager make business decisions that the DPO is supposed to oversee — an inherent conflict of interest, and the Authority has been clear about it. The practical model for kibbutzim: an outsourced DPO who works with the committees and management but is not subordinate to them. The appointment is formalized with a DPO appointment letter.

Kibbutz WhatsApp groups — direct marketing?

Depends on the content. Organizational announcements to members are internal communications. But trade groups ("for sale", "looking for") with auto-added members, or promotional broadcasts from kibbutz businesses, can fall under the direct-marketing rules. The review is content-by-content, not platform-by-platform.

How much does a DPO service for a kibbutz cost?

Depends on the kibbutz size, complexity (cooperative / renewing), number of corporate subsidiaries, and number of databases. Have a look at the tiers, or just talk to us — the intro call is free.

More questions? Talk to us directly.