Who this actually applies to
The law doesn't distinguish between a "large business" and a "small business" when defining a database. The moment a lead form on your site collects a name, phone number, or email address, and stores it somewhere - an inbox, a spreadsheet, or a CRM account - you're running a database. That's as true for a law office with three clients a month as it is for a large service chain. The assumption that "this only applies to tech companies and big data" is exactly why small businesses get caught unprepared.
What actually changed under Amendment 13
- The duty to register databases with the Privacy Protection Authority was significantly narrowed, and now applies only to cases defined in the law - not by default to every database.
- A new duty to appoint a Data Protection Officer (DPO) was added for entities that meet certain conditions, mainly those processing sensitive data or data at large scale.
- The Privacy Protection Authority was given broader investigative and enforcement powers, including the ability to impose significant fines for violations.
- The amendment brings Israel closer to the EU's GDPR, and preserves its adequacy status with the EU - which makes it easier for Israeli businesses working with European tools and vendors.
Per a summary by law firm Goldfarb Seligman, the Knesset passed Amendment 13 on August 5, 2024, and it took effect on August 14, 2025 (source: goldfarb.com).
A narrower registration duty doesn't mean "no obligations"
This is the most common mistake we hear from clients: "I heard they relaxed the registration rules, so we're fine." The relaxed registration rule doesn't cancel data security duties, documentation, or restrictions on how data is used - it only changes who has to formally report the database's existence. Per a summary by international law firm DLA Piper, a database that isn't subject to standard registration still must be reported to the Privacy Protection Authority if it holds especially sensitive data on more than 100,000 people (source: dlapiperdataprotection.com).
How this touches your CRM account
If your site is connected to GoHighLevel, HubSpot, or any other CRM, the data you collect in a lead form doesn't disappear - it flows straight into a pipeline, a mailing list, and SMS and email automations. That means a few concrete things are worth checking:
- Documented consent on the form - a separate checkbox (not pre-checked) that explains why the data is collected and where it goes, not just an automatic "submit."
- A linked, clear privacy policy - a page explaining what data is collected, how long it's kept, and who else sees it (including the CRM vendor itself).
- A map of every database the business holds - including old spreadsheets and an inbox, not just the active CRM.
- Checking whether the volume and sensitivity of your data justifies a DPO - even when it's not mandatory, it's sometimes the right move to show real preparedness.
What's actually worth doing, without the panic
Real preparedness doesn't require halting the business. It requires order: knowing which databases exist, what happens in them, and who's responsible for them. In the projects we build at May I, that looks like this: a privacy policy page that's accurate to what the site actually does, a lead form with an explicit consent checkbox before data goes to the CRM, and data-retention settings in GoHighLevel that don't leave old data sitting around with no purpose. This doesn't replace legal advice tailored to your specific business - but it's what your technical infrastructure needs to support.
Not sure if your site and CRM are ready?
We build lead forms and set up GoHighLevel accounts that start from the right foundation - documented consent, an accurate privacy policy, and orderly data retention.
Get started