Israeli Privacy Shield
Trusted88/100Israeli Privacy Protection Law compliance guidance including Amendment 13 (effective August 14, 2025), database registration, consent requirements, data security, cross-border transfers, breach notification, privacy protection officer appointment, and AI governance. Use when user asks about Israeli privacy law, "haganat pratiut", "tikun 13", data protection in Israel, GDPR compliance for Israeli companies, privacy policy requirements, or database registration. Covers the Privacy Protection Law 1981, Amendment 13, and 2017 Security Regulations. Do NOT use for EU GDPR-only questions without Israeli context.
Trust score 88/100 (Trusted) · 509+ installs · 2 GitHub contributors · MIT license
The Israeli Privacy Protection Law and its security regulations impose specific obligations on any business managing a personal data repository. These requirements differ from GDPR and other international frameworks, and most global compliance tools do not cover the Israeli legal framework. Without dedicated guidance, businesses are exposed to fines and lawsuits.
skills-ilnpx skills-il add skills-il/security-compliance@v1.4.1-israeli-privacy-shield --skill israeli-privacy-shield -a claude-codeInstall on Claude.ai, Claude Desktop, ChatGPT, Manus, or other platforms
- 1. Click "Download ZIP" to download the skill files.
- 2. Open Claude Desktop and go to Customize > Skills.
- 3. Click "+" and select "Upload a skill", then upload the ZIP file.
- 4. Start a new conversation. The skill will activate automatically when relevant.
When to Apply
- When complying with the Israeli Privacy Protection Law (1981) including Amendment 13 (effective August 14, 2025)
- When a business must appoint a Privacy Protection Officer (DPO) under new requirements
- When a data incident occurs and notification to the Privacy Protection Authority is required
- When classifying personal data under the expanded definition (IP, geolocation, online identifiers)
- When building AI governance policies under Amendment 13 automated decision-making rules
- When building a cookie/consent banner for an Israeli or EU-facing Next.js or React site
Try These Prompts
We are a SaaS company storing Israeli customer data. How do I map the personal information we hold to comply with the Privacy Protection Law?
We received a personal data access request from a consumer. What are our obligations under the Israeli Privacy Protection Law and within what timeframe must we respond?
We work with a foreign cloud provider. Do we need a data processing agreement under Israeli law and what must it include?
Build me a GDPR + Amendment 13 compliant consent banner for my Next.js site. Explicit opt-in, equal-weight Reject/Accept, ESC/X dismissal-as-refusal, 12-month re-prompt, localStorage + companion cookie for SSR gating, and cross-tab sync via the storage event.
My consent banner ships in the SSR HTML and is visible for a moment before hydration replaces it. Show me the SSR_SENTINEL pattern with useSyncExternalStore that keeps the banner out of the server render and only shows it after hydration when no choice is stored.
Frequently Asked Questions
Changelog
Added Data Subject Rights (DSR) workflow with 30-day response template, DPIA section, Minors data section (Capacity and Guardianship Law 1962, Biometric ID Law 2009, January 2020 ed-tech audit), expanded fine table with HOT enforcement datapoint, and two new troubleshooting entries (borderline DPO threshold and cross-border transfer to non-adequate country).
May 18, 2026
Amendment 13 overhaul: 72-hour breach notification deadline, DPO appointment thresholds, the 100k-record sensitive-data notification tier, and official reference links.
May 14, 2026
Added implementation guidance for an Amendment 13 + GDPR compliant consent banner: three-phase state model, SSR_SENTINEL pattern keeping the banner out of SSR HTML, cross-tab sync via storage event, dismissal-as-refusal for ESC/X, equal-weight Reject/Accept, tracker gating, Sentry pre-init hydration + mid-session Replay attach, and server-side cookie check. Complete copy-pasteable code in references/consent-banner-implementation.md plus an anti-patterns table citing CJEU Planet49 and EDPB guidance.
Apr 21, 2026
Related Skills
Author: skills-ilGuide Israeli ML teams through the AI governance and compliance stack: Ministry of Innovation December 2023 AI policy principles, Privacy Protection Law (PPL) and Amendment 13 applied to ML training data, sector-specific rules (Bank of Israel Directive 364, Ministry of Health AMAR medical-device AI), and EU AI Act exposure for Israeli exporters. Generates model cards, data statements, and DPIA templates tailored to Israeli context. Use when preparing AI governance docs, answering an enterprise customer's AI risk review, classifying a system under the EU AI Act, or building an internal responsible-AI checklist. Prevents costly compliance gaps when shipping AI to regulated markets. Do NOT use for general PPL policy (use israeli-privacy-shield), web app security (use israeli-appsec-scanner), or SOC/threat triage (use israeli-cybersecurity-ops).
Author: skills-ilCoordinate Israeli-built cybersecurity tools for security operations including threat triage, vulnerability management, compliance checking, and incident response. Use when user mentions security operations, "SOC", vulnerability scanning, threat triage, compliance assessment, or asks to coordinate Wiz, Snyk, Check Point, CyberArk, SentinelOne, Armis, Torq, or Pentera tools. Embeds Israeli security best practices including INCD guidelines and Israeli Privacy Protection Law compliance. Do NOT use for offensive security testing or creating exploits.
Author: skills-ilAudit and ensure Israeli e-commerce legal compliance, Consumer Protection Law, return policies, price display, accessibility, and cookie consent. Use when user asks about "online store compliance Israel", "Chok Hagnat HaTzarchan", "consumer protection Israel", "return policy Israel", "IS 5568 ecommerce", "cookie consent Israel", or "חוק הגנת הצרכן". Covers cooling-off period validation, price display requirements, Hebrew terms of service generation, accessibility compliance (IS 5568), and business disclosure verification. Do NOT use for food-specific compliance (use israeli-food-business-compliance) or privacy/GDPR (use israeli-privacy-shield).
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill