Cold Email Law Checker
Pricing
Pay per usage
Cold Email Law Checker
Checks every lead against the cold email law of the recipient's country before you send. 33 countries checked against the law text: whether a first email needs consent for a named person, info@ or gmail address, what the email must contain, and a link to the law.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Ilia Ivanov
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Before you send a cold email campaign to another country, check whether the law there lets you. This Actor gives every lead in your list a verdict for the first unsolicited marketing email to it, based on the recipient's country and the kind of address.
33 countries, each checked against the law text or the regulator's guidance, with a link to the source.
Why
The rules change at every border. Germany, Spain and Italy want consent before the first email, even to a company address. France allows it if the offer relates to the person's job. The US allows it but wants a postal address and an opt-out in every email. Sweden protects people but not companies. Slovakia, Slovenia and Japan care whether the company published the address itself.
Email verifiers tell you whether an address exists. This tells you whether you may write to it.
What you get for each lead
| Field | Example |
|---|---|
law_country | DE |
law_addressType | named, generic (info@, sales@) or personal (gmail) |
law_verdict | ok, cond, consent or unknown |
law_verdictLabel | Consent first |
law_sendWithoutConsent | false |
law_reason | Prior consent required in Germany for this kind of address. |
law_rule | The rule in one paragraph |
law_mustInclude | What the email itself must contain (opt-out, postal address...) |
law_lawSource | Link to the law or the regulator |
law_rulesPage | Page with all verdicts and sources for that country |
law_checked | Date the rules were checked |
Your own fields are kept, so you can filter the dataset and send only the rows you may email. The run summary (counts per verdict) is saved as OUTPUT in the key-value store.
Input
Give it leads in one of three ways:
- Dataset ID from another Actor run, such as a lead scraper. Nested fields like
location.countryare found automatically. - CSV URL of an export.
- Leads as JSON: plain email addresses or objects.
The email, country and source fields are detected automatically. You can set them by name if detection picks the wrong one.
Use the person's country, not the company HQ. The rules follow the recipient: a German employee of a US company is a German recipient. If no country is given, it is guessed from the domain (.de, .fr) and the row says so.
Optional source field. published (the company put the address on its own site or in a register) or vendor (a tool found or guessed it; values like apollo or hunter count as vendor). In Canada, Australia, Japan, the Netherlands, Slovakia and Slovenia this changes the verdict.
Run it automatically after your lead scraper
- Open the lead scraper you already use (or your saved task for it) and go to the Integrations tab.
- Choose Connect Actor or Task, pick Cold Email Law Checker, and trigger it when the run succeeds.
- Keep the prefilled input:
{"datasetId": "{{resource.defaultDatasetId}}"}. AddcountryFieldorsourceFieldif your scraper names them differently.
Every new list then gets its verdicts without you touching it. The checker only gets read access to that one dataset.
Countries covered
| Country | Named person (jane@company) | Generic (info@company) | Personal mailbox (gmail) | Checked |
|---|---|---|---|---|
| Australia | Specific cases | Specific cases | Specific cases | 2026-10-10 |
| Austria | Consent first | Consent first | Consent first | 2026-10-10 |
| Belgium | Consent first | No consent needed | Consent first | 2026-10-10 |
| Bulgaria | Specific cases | Specific cases | Specific cases | 2026-10-14 |
| Canada | Specific cases | Specific cases | Consent first | 2026-10-10 |
| Croatia | Not verified | No consent needed | Consent first | 2026-10-14 |
| Cyprus | Not verified | Not verified | Consent first | 2026-10-14 |
| Czech Republic | Consent first | Consent first | Consent first | 2026-10-10 |
| Denmark | Consent first | Consent first | Consent first | 2026-10-10 |
| Estonia | Not verified | No consent needed | Consent first | 2026-10-14 |
| Finland | Not verified | No consent needed | Consent first | 2026-10-10 |
| France | No consent needed | No consent needed | Not verified | 2026-10-10 |
| Germany | Consent first | Consent first | Consent first | 2026-10-10 |
| Greece | Consent first | Consent first | Consent first | 2026-10-14 |
| Ireland | Specific cases | No consent needed | Consent first | 2026-10-10 |
| Italy | Consent first | Consent first | Consent first | 2026-10-10 |
| Japan | Specific cases | Specific cases | Specific cases | 2026-10-15 |
| Latvia | Not verified | No consent needed | Consent first | 2026-10-14 |
| Liechtenstein | Consent first | Consent first | Consent first | 2026-10-14 |
| Luxembourg | Not verified | No consent needed | Consent first | 2026-10-14 |
| Malta | Consent first | Consent first | Consent first | 2026-10-14 |
| Netherlands | Specific cases | Specific cases | Consent first | 2026-10-10 |
| Norway | Consent first | No consent needed | Consent first | 2026-10-10 |
| Poland | Consent first | Consent first | Consent first | 2026-10-10 |
| Portugal | Not verified | No consent needed | Consent first | 2026-10-11 |
| Singapore | No consent needed | No consent needed | No consent needed | 2026-10-15 |
| Slovakia | Specific cases | Specific cases | Specific cases | 2026-10-14 |
| Slovenia | Specific cases | No consent needed | Consent first | 2026-10-14 |
| Spain | Consent first | Consent first | Consent first | 2026-10-10 |
| Sweden | No consent needed | No consent needed | Consent first | 2026-10-10 |
| Switzerland | Consent first | Consent first | Consent first | 2026-10-10 |
| United Kingdom | No consent needed | No consent needed | Consent first | 2026-10-10 |
| United States | No consent needed | No consent needed | No consent needed | 2026-10-10 |
Not covered yet: everything else. Rows for other countries come back as unknown with the reason.
Limits
This is a research summary, not legal advice. It covers the first unsolicited marketing email to a business recipient. Data protection law (GDPR, UK GDPR) applies separately whenever an address identifies a person. Every verdict links to its source so you can check it.
The same rules power the free web checker at phazww.github.io/can-i-cold-email. Corrections are welcome: open an issue on GitHub.
