> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # Israel Sender & Marketing Rules (Spam Law 2008) > Plan Israeli A2P messaging around the Communications Law (Bezeq and Broadcasting) spam amendment of 2008, the Privacy Protection Law 5741-1981, aggregator-routed alphanumeric sender registration, and Hebrew and English STOP handling. # Israel Sender & Marketing Rules (Spam Law 2008) Israel regulates commercial messaging through the spam amendment to the **Communications Law (Bezeq and Broadcasting), 5742-1982**, enacted in 2008 (Amendment No. 40, commonly "the Spam Law" or Section 30A), administered with the **Ministry of Communications**, and personal data through the **Protection of Privacy Law, 5741-1981**, enforced by the **Protection of Privacy Authority (PPA)**. Israel's regime is one of the stricter marketing regimes in the market category: it is **opt-in**, with a statutory definition of consent, and it grants every recipient a standing right to withdraw consent — so both the consent record and the opt-out machinery are statutory duties, not house rules. Israel's data-protection posture is its own: the Privacy Protection Law applies to processing in Israel regardless of where your organization sits, and regimes such as Canada's PIPEDA or the EU's GDPR apply to Israeli residents only through their own extraterritorial reach — confirm which privacy statutes actually bind your program with counsel rather than assuming a familiar framework carries over. **Scope.** Your organization owns the lawful basis for each market. Orbit ships tenant-owned controls only — the consent ledger, suppression, keyword aliases, quiet hours, sender-registration tracking, and the send-gate — defaults-open; you configure them for Israel. This page is documentation, not legal advice. Enforcement exposure is real: the Spam Law provides statutory damages per message without proof of loss, and class actions over unsolicited SMS are common in Israeli practice. The PPA administers fines under the Privacy Protection Law. Have counsel review your consent text and footer identity before you send into `IL`. *** ## 1. Sender IDs: registration via the Israeli aggregator Read the live `IL` row of `GET /compliance/country-rules?channel=sms` on [Country Compliance Requirements](/compliance/country-requirements) before you provision. Israel has no public regulator-held sender registry for A2P brands; alphanumeric sender IDs are registered through the Israeli aggregator and the licensed operators that terminate your route. An identity that is not registered for the route is rewritten or filtered at the operator edge. ```bash theme={null} curl "https://api.orbit.devotel.io/api/v1/compliance/country-rules?channel=sms&country=IL" \ -H "Authorization: Bearer $ORBIT_API_KEY" ``` File the alphanumeric sender through [Sender-ID Registration](/compliance/sender-id-registration) and keep `IL` traffic in rehearsal until the entry reports `approved`. Where the live row reports `registration: required` without an approved entry, the [send-gate](/compliance/send-gates) holds `IL` traffic — intended behavior, not a fault. The Spam Law also expects each message to identify the sender and how to contact them; carry that identity in your content layer, not only in the sender-ID field. *** ## 2. Opt-in consent under the Spam Law The Spam Law prohibits sending a commercial message without the recipient's prior consent as the statute defines it — documented, purpose-specific consent, captured and evidenced on the [consent ledger](/compliance/consent-management) before the first send. A number collected to complete an order does not carry marketing consent with it. The tenant-owned [unknown-marketing policy](/compliance/consent-default-policy) at its `refuse` default is the correct posture for Israel-bound promotional traffic given the statutory-damages exposure. Consent under the Spam Law is revocable at any time, and the revocation must be honored — which is what makes the Hebrew and English STOP machinery below a statutory duty rather than a courtesy. The Privacy Protection Law adds the data-side layer: purpose limitation at collection, a database registration posture for your marketing database as the PPA requires, and data-subject rights routed through your [DSAR](/compliance/dsar) process. *** ## 3. Dual Hebrew/English STOP Israeli recipients reply in Hebrew and English, and the statute cares that withdrawal works, not which alphabet it arrives in. Publish the opt-out terms in both languages in your consent text and footers and extend the [Opt-Out Keyword Alias Table](/compliance/opt-out-keyword-alias-table) with `IL`-targeted Hebrew aliases — `עצור` (stop) and `הסר` (unsubscribe) alongside the seeded `STOP` family: | Direction | Aliases to cover `IL` | | - | - | | Opt-out | `עצור`, `הסר`, `STOP` | | Opt-in | `START` | The matcher's case-folding and Unicode normalisation write the same suppression row for `עצור`, `STOP` and `stop`; set the auto-reply to acknowledge in both languages. Route `IL` revocations at scope `all` so a contact who stops your SMS is not then emailed by the same program, and keep the revocation record — under the statutory-damages regime, the suppression row is your evidence. *** ## 4. Marketing-window posture Israel has no codified no-send window for marketing SMS; the practical exposure is the statutory-damages and consumer-protection framing of harassment, so keep marketing to reasonable recipient-local hours. Set tenant quiet hours over the evening and overnight hours (21:00–08:00 recipient-local is the conservative convention) on [Quiet-Hours Configuration](/guides/quiet-hours-configuration) and validate the `+972` resolution with [Quiet-Hours Preview](/compliance/quiet-hours-preview). Israel shifts between **UTC+2 and UTC+3** on its daylight-saving schedule — and note the Friday-afternoon to Saturday-evening window, when a large share of the audience observes Shabbat; tightening the window for it is a campaign-level call, not a platform change. *** ## 5. Obligations → Orbit surface table | Spam Law / PPA obligation | Orbit surface that carries it | | - | - | | Prior statutory consent for commercial messages | [Consent Management](/compliance/consent-management); [unknown-marketing policy](/compliance/consent-default-policy) at `refuse` | | Sender identification in each message | Content-layer footer carrying the sender identity and contact path, alongside the registered sender-ID | | Alphanumeric sender registration via aggregator | [Sender-ID Registration](/compliance/sender-id-registration); the [send-gate](/compliance/send-gates) holds `IL` traffic until `approved` | | Revocation honored at any time | [Opt-Out Keyword Alias Table](/compliance/opt-out-keyword-alias-table) Hebrew + English aliases; suppression at scope `all` via [Opt-Out & Suppression Lists](/compliance/opt-out-suppression) | | Database registration + data-subject rights (Privacy Law) | [DSAR](/compliance/dsar) process; records kept on the consent ledger | | Reasonable-hours marketing | [Quiet-Hours Configuration](/guides/quiet-hours-configuration), validated with [Quiet-Hours Preview](/compliance/quiet-hours-preview) | | Restricted content | [Restricted & Prohibited Industries](/compliance/restricted-industries) | *** ## 6. Launch checklist 1. Treat `IL` marketing as opt-in under the statutory definition; no promotional send without a consent row. 2. Read the live `IL` row per channel: sender types, registration level, stop requirement. 3. File the alphanumeric sender through your Israeli aggregator path and wait for `approved`. 4. Publish Hebrew + English STOP terms and confirm both write suppression rows with a two-language auto-reply. 5. Carry the sender identity and contact path inside each message's content layer. 6. Set tenant quiet hours over the recipient-local evening window; decide the Shabbat posture per campaign. 7. Confirm which privacy statutes bind your program (Israeli, EU, other) with counsel. 8. Test sender rendering, opt-out handling and delivery reporting with a small audience first. *** ## Frequently asked questions **Does Orbit register my sender in Israel?** No — registration runs through your Israeli aggregator and the licensed operators, as in every market. Orbit tracks the `IL` entry and gates send-time traffic on it. **Is Israeli marketing opt-in or opt-out?** Opt-in, statutorily. The Spam Law defines consent and requires it before the first commercial message; the standing revocation right then makes the STOP machinery a statutory duty as well. **Do I need Hebrew STOP keywords if my messages are in English?** Yes where Hebrew speakers appear in your audience — revocation must work in the language a recipient replies in. The alias-table extension makes `עצור` and `הסר` land in the same suppression row as `STOP`. *** ## Related references * [Country Compliance Requirements](/compliance/country-requirements) — the live `IL` row this page expands. * [Sender-ID Registration](/compliance/sender-id-registration) — the submit-and-track flow. * [Consent Management](/compliance/consent-management) — the consent record contract. * [Opt-Out Keyword Alias Table](/compliance/opt-out-keyword-alias-table) — the custom-alias path for Hebrew terms. * [Quiet-Hours Configuration](/guides/quiet-hours-configuration) — the window control. * [Regional Posture Hub](/compliance/country-rules-directory) — the index this page is listed in. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.