Amendment 13 to Israel's Privacy Protection Law has changed the rules of the game for every business that holds personal information about customers, employees, or suppliers — which is almost every business. The problem is that the law itself is written in legal language, and it is hard to work out from it exactly what needs to be done on Monday morning. The following checklist translates the main requirements into concrete actions.
Mapping Your Databases — The Step Most Often Skipped
You cannot protect information you do not know you have. The first and most important step is a complete mapping: which databases exist in the business, what type of information they contain, who accesses them, and where they are stored — including old Excel files and forgotten shared folders.
Key Obligations You Should Make Sure Are in Place
- Registering databases that are subject to registration, according to the type and volume of information.
- Appointing a Data Protection Officer (DPO) where the law requires it, depending on the size and type of activity.
- Information security procedures documented in writing — not just "common practice" that no one ever wrote down.
- An incident response mechanism for security events, including reporting to the Privacy Protection Authority where required.
- Informed consent and transparency toward customers regarding the collection and use of information.
The Most Common Implementation Mistake
Many businesses treat Amendment 13 as a one-time project: they write a policy document, file it in a drawer, and move on. In practice, the Privacy Protection Authority expects a living mechanism — procedures that are kept up to date, periodic reviews, and documentation showing that the business actually operates according to the policy it wrote, not merely that it has one on paper.
What Actually Happens When You Fail to Comply
The Privacy Protection Authority has already shown that it enforces in practice, including significant fines on businesses that failed to meet the basic requirements. Beyond the fine itself, a security incident that comes to light because proper procedures were missing damages customer trust in a way that is much harder to repair.
Questions and Answers
- Which businesses are required to appoint a Data Protection Officer?
- The obligation depends on factors such as the volume and type of information processed — businesses that process sensitive information on a large scale, or for which data processing is a core part of their business activity, usually fall under this obligation. It is advisable to check the exact criteria with legal counsel.
- Does a small business also need to register a database?
- Not every database is subject to registration — it depends on the type and volume of information. But even a small business that holds sensitive information, such as health data or financial information, may fall under the registration requirement.
- How long does it take to implement the requirements from scratch?
- An initial mapping and the fixing of the most basic gaps can be completed within a few weeks. Building a full, sustainable mechanism, with up-to-date procedures and periodic reviews, is an ongoing process rather than a project with a finish line.
