Getting started
Country rules
The rule Galactic Outreach applies to every city it can search: where it sends, where it holds every lead, and the law behind each.
Last updated
How the rule is chosen
Every search is for a city, and each city Galactic can search carries one rule for its country. The rule is set when the queue is built, from the same table the product reads, so this page and the product cannot disagree.
A lead in a country marked opt-in first is held: it is never queued, and the safety checks block any batch that contains one. There is no setting that overrides this. A city outside the table is held too, as unknown jurisdiction.
The rules
Two conditions in the table are yours to keep, because Galactic records them but cannot check them. In the UK and Ireland the address must belong to a company, not a sole trader. In Canada it must be one the business publishes itself, which is what a search collects, and a list you import may not be.
| Country | Cities | What Galactic does | The rule it applies |
|---|---|---|---|
| United States (US) | Atlanta, Austin, Boston, Chicago, Denver, Los Angeles, Miami, New York, San Diego, San Francisco, Seattle | Sends | CAN-SPAM: an opt-out and a real postal address |
| United Kingdom (UK) | London, Manchester | Sends, to company addresses only | PECR corporate subscriber exemption: companies and LLPs only |
| Ireland (IE) | Dublin | Sends, to company addresses only | B2B to corporate addresses, with sender ID and an opt-out |
| Netherlands (NL) | Amsterdam, Rotterdam | Sends | B2B on an opt-out basis |
| France (FR) | Paris | Sends | B2B allowed when relevant to the recipient's profession |
| Canada (CA) | Toronto, Vancouver | Sends, to published addresses only | CASL implied consent from a published address; penalties up to CAD 10M |
| Australia (AU) | Melbourne, Sydney | Sends | Spam Act 2003: inferred consent from a published business address |
| India (IN) | Bangalore, Mumbai | Sends | DPDP: a working unsubscribe and an accurate sender ID |
| Singapore (SG) | Singapore | Sends | Opt-out |
| Hong Kong (HK) | Hong Kong | Sends | UEMO: opt-out |
| Philippines (PH) | Manila | Sends | Data Privacy Act: opt-out |
| Germany (DE) | Berlin, Munich | Holds every lead | UWG §7 requires opt-in, even B2B |
| Spain (ES) | Barcelona, Madrid | Holds every lead | LSSI requires explicit prior consent |
| Poland (PL) | Warsaw | Holds every lead | Opt-in required; the B2B exception is disputed, so held until settled |
| Anywhere else | Any city not listed | Holds every lead | Unknown jurisdiction |
Sources
- FTC: CAN-SPAM Act compliance guide
- ICO: electronic mail marketing (PECR)
- Ireland: S.I. No. 336/2011 (ePrivacy Regulations)
- EU ePrivacy Directive 2002/58/EC, Article 13
- CNIL: commercial prospecting by email (France)
- Canada's Anti-Spam Legislation (CASL)
- Australia: Spam Act 2003
- Singapore: Spam Control Act 2007
- Hong Kong: Unsolicited Electronic Messages Ordinance (Cap. 593)
- Philippines: Data Privacy Act of 2012 (RA 10173)
- Germany: UWG §7
- Spain: LSSI (Ley 34/2002)
- GDPR (EU 2016/679), Articles 14 and 21