> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enricho.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Cold email compliance

> The compliance check of Email Intelligence: where the recipient is, whether a cold email to them is allowed under that country's law, and what you must do. 71 countries.

Before you send a cold email, the `compliance` check of [Email Intelligence](https://docs.enricho.co/intelligence/email-intelligence.md) tells you whether that email is allowed. The law that protects an inbox is the law of the recipient's country, not yours, so Enricho first works out where the recipient is, then applies that country's rules.

```json theme={null}
"compliance": {
  "recipient_type": "business",
  "country_code": "XX",
  "country_source": "company_hq",
  "country_confidence": "medium",
  "verdict": "consent_required",
  "law": "The country's anti-spam law, with the articles that apply",
  "reason": "Cold email to business addresses in XX needs the recipient's prior consent.",
  "conditions": ["Identify yourself as the sender.", "Give a free, easy opt-out in every email."],
  "exceptions": ["Existing customers may be emailed about your own similar products if they could refuse at collection and in every message."],
  "sources": ["https://regulator.example/guidance"]
}
```

The response also carries `rules_version` (the date the rules were last reviewed) and a `disclaimer`.

> [!WARNING]
>
> Compliance is a summary of each country's cold-email rules, not legal advice. Check with counsel before relying on a verdict, especially for `consent_required` exceptions you plan to use.

## Verdicts

| `verdict` | What to do |
| - | - |
| `allowed` | You may send without prior consent, **if you meet every item in `conditions`** (identify yourself, offer an unsubscribe, honour opt-outs…). |
| `consent_required` | Don't send unless the recipient opted in, or one of the `exceptions` clearly applies to you. |
| `do_not_send` | A throwaway inbox, or a domain that can't receive email. |
| `unknown` | No country found, or no rules for that country yet. Free. |

## Step 1: where is the recipient?

Enricho uses the best source it has, in this order:

| `country_source` | `country_confidence` | How it was found |
| - | - | - |
| `person_record` | `high` | Enricho holds a record of the person with this exact address, and knows where they are. |
| `name_match` | `medium` | Someone with the name in the address (`anna.schmidt@`) works at the domain's company; their location. |
| `company_hq` | `medium` | The head office of the domain's company. The person may work elsewhere. For a shared inbox (`info@`), which belongs to the company itself, confidence is `high`. |
| `domain_tld` | `low` | The domain's country ending. Endings used worldwide (`.io`, `.co`, `.ai`…) are ignored. |

When confidence is `medium` or `low` and the verdict matters, confirm the country yourself, or add the `identity` check to see who the person is.

## Step 2: business or personal?

Most laws treat a company address differently from a personal mailbox. `recipient_type` is `personal` for mailboxes at personal providers (Gmail, Outlook, iCloud…) and `business` for everything else. The same country can give `allowed` for one and `consent_required` for the other.

Some countries also let you email a **generic company address** (`info@`, `sales@`) without consent, even where named business addresses need it. Enricho applies that automatically when the address is a shared inbox.

## Step 3: the rule

Each country's rule was researched from its legislation and regulator guidance. `law` names the statute, and `sources` links the official pages it was checked against. Where a law's position on business email was unclear, the stricter answer (`consent_required`) is returned, never the looser one.

## Countries covered

Verdicts below are before any exception. "Exceptions" means the law has narrow ways to send without consent (most often, existing customers and your own similar products); they are returned in `exceptions`.

| Country | Code | Business address | Personal mailbox | `info@` without consent | Exceptions |
| - | - | - | - | - | - |
| Argentina | AR | Allowed | Allowed | — | — |
| Australia | AU | Consent required | Consent required | — | Yes |
| Austria | AT | Consent required | Consent required | — | Yes |
| Bangladesh | BD | Consent required | Consent required | — | — |
| Belgium | BE | Consent required | Consent required | Yes | Yes |
| Brazil | BR | Allowed | Consent required | — | Yes |
| Bulgaria | BG | Allowed | Consent required | — | Yes |
| Canada | CA | Consent required | Consent required | — | Yes |
| Chile | CL | Allowed | Allowed | — | — |
| China | CN | Consent required | Consent required | — | — |
| Colombia | CO | Consent required | Consent required | — | Yes |
| Croatia | HR | Allowed | Consent required | — | Yes |
| Cyprus | CY | Allowed | Consent required | — | Yes |
| Czechia | CZ | Consent required | Consent required | — | Yes |
| Denmark | DK | Consent required | Consent required | — | Yes |
| Egypt | EG | Consent required | Consent required | — | — |
| Estonia | EE | Allowed | Consent required | — | Yes |
| Finland | FI | Allowed | Consent required | — | Yes |
| France | FR | Allowed | Consent required | — | Yes |
| Germany | DE | Consent required | Consent required | — | Yes |
| Greece | GR | Consent required | Consent required | — | Yes |
| Hong Kong | HK | Allowed | Consent required | — | Yes |
| Hungary | HU | Allowed | Consent required | — | Yes |
| Iceland | IS | Consent required | Consent required | — | Yes |
| India | IN | Consent required | Consent required | — | Yes |
| Indonesia | ID | Consent required | Consent required | — | Yes |
| Ireland | IE | Allowed | Consent required | — | Yes |
| Israel | IL | Consent required | Consent required | — | Yes |
| Italy | IT | Consent required | Consent required | — | Yes |
| Japan | JP | Consent required | Consent required | — | Yes |
| Kazakhstan | KZ | Consent required | Consent required | — | — |
| Kenya | KE | Consent required | Consent required | — | — |
| Latvia | LV | Allowed | Consent required | — | Yes |
| Liechtenstein | LI | Consent required | Consent required | — | Yes |
| Lithuania | LT | Consent required | Consent required | — | Yes |
| Luxembourg | LU | Consent required | Consent required | — | Yes |
| Malaysia | MY | Consent required | Consent required | — | — |
| Malta | MT | Consent required | Consent required | — | Yes |
| Mexico | MX | Allowed | Consent required | — | Yes |
| Morocco | MA | Consent required | Consent required | — | Yes |
| Nepal | NP | Consent required | Consent required | — | — |
| Netherlands | NL | Consent required | Consent required | — | Yes |
| New Zealand | NZ | Consent required | Consent required | — | Yes |
| Nigeria | NG | Consent required | Consent required | — | — |
| Norway | NO | Consent required | Consent required | Yes | Yes |
| Pakistan | PK | Consent required | Consent required | — | — |
| Peru | PE | Consent required | Consent required | — | — |
| Philippines | PH | Consent required | Consent required | — | Yes |
| Poland | PL | Consent required | Consent required | — | Yes |
| Portugal | PT | Allowed | Consent required | — | Yes |
| Qatar | QA | Consent required | Consent required | — | — |
| Romania | RO | Consent required | Consent required | — | Yes |
| Russia | RU | Consent required | Consent required | — | — |
| Saudi Arabia | SA | Consent required | Consent required | — | Yes |
| Singapore | SG | Allowed | Consent required | — | Yes |
| Slovakia | SK | Consent required | Consent required | — | Yes |
| Slovenia | SI | Allowed | Consent required | — | Yes |
| South Africa | ZA | Consent required | Consent required | — | Yes |
| South Korea | KR | Consent required | Consent required | — | Yes |
| Spain | ES | Consent required | Consent required | — | Yes |
| Sri Lanka | LK | Consent required | Consent required | — | — |
| Sweden | SE | Allowed | Consent required | — | Yes |
| Switzerland | CH | Consent required | Consent required | — | Yes |
| Taiwan | TW | Allowed | Allowed | — | — |
| Thailand | TH | Consent required | Consent required | — | Yes |
| Türkiye | TR | Allowed | Consent required | — | Yes |
| Ukraine | UA | Consent required | Consent required | — | Yes |
| United Arab Emirates | AE | Consent required | Consent required | — | — |
| United Kingdom | GB | Allowed | Consent required | — | Yes |
| United States | US | Allowed | Allowed | — | — |
| Vietnam | VN | Consent required | Consent required | — | — |

Rules reviewed 2026-11-10 (`rules_version`). Addresses in other countries return `unknown`, free of charge. Want a country added? [Email support](mailto:support@enricho.co).

## Credits

Each compliance answer costs 1 credit (\$0.02). `unknown` verdicts and malformed addresses are free, and checking the same address again within a year is free.

## Use it in a sending workflow

1. Run `validity` and `compliance` together on your list (up to 50 addresses per request).
2. Drop `invalid` and `do_not_send` addresses.
3. Keep `allowed` addresses, and meet every item in their `conditions`.
4. Hold `consent_required` addresses unless you have consent or an exception clearly applies.

The [batching recipe](https://docs.enricho.co/api-reference/recipes.md#clean-a-list-before-a-campaign) does this for a list of any size.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.