It depends on what you mean by "legal": against Google's terms, against the law, or against privacy rules once you use the data. Those are three different questions with three different answers - here they are, without the hedging.
Le Comptoir du Relais
comptoirdurelais.fr
Brasserie Lipp
brasserielipp.fr
Café de Flore
cafedeflore.fr
Au Pied de Cochon
pieddecochon.com
| Name | Address | Phone | Rating | Website | Emails | Socials | Action |
|---|---|---|---|---|---|---|---|
| Le Comptoir du Relais | 9 Carrefour de l'Odéon, 75006 Paris | +33 1 44 27 07 97 | ★4.6(2,341) | comptoirdurelais.fr | contact@comptoirdurelais.fr - | fbig - | |
| Brasserie Lipp | 151 Bd Saint-Germain, 75006 Paris | +33 1 45 48 53 91 | ★4.3(4,892) | brasserielipp.fr | reservation@brasserielipp.fr - | fbigtw - | |
| Café de Flore | 172 Bd Saint-Germain, 75006 Paris | +33 1 45 48 55 26 | ★4.4(11,203) | cafedeflore.fr | info@cafedeflore.fr - | igfb - | |
| Au Pied de Cochon | 6 Rue Coquillière, 75001 Paris | +33 1 40 13 77 00 | ★4.1(6,784) | pieddecochon.com | contact@pieddecochon.com - | fbig - |
Start with the unambiguous part: scraping Google Maps violates Google's Terms of Service. The terms prohibit accessing the service with automated tools and extracting data in bulk. That is not a gray area - every Maps scraper, browser extension, and "free extractor" operates against the contract Google puts in front of its users.
But a ToS violation is a contract matter, not a crime. The consequences come from Google, not from a prosecutor: CAPTCHAs, IP blocks, terminated accounts, and - for commercial operations at scale - the possibility of civil action. For a business that depends on a steady flow of leads, the practical risk is that your data pipeline disappears overnight, not that anyone goes to jail.
The case law on scraping public data is genuinely unsettled - and this is not legal advice. The landmark US case, hiQ v. LinkedIn, went back and forth for years: courts held that scraping publicly visible pages likely does not violate the federal anti-hacking statute (the CFAA), yet hiQ ultimately lost on breach-of-contractgrounds - the very ToS issue above. In the EU, database rights and unfair-competition rules add further ways a bulk extractor can be liable even when no "hacking" is involved.
The honest summary: courts have been reluctant to criminalize scraping public data, but platforms keep winning on contract. If your business depends on the data, "probably not criminal" is a thin foundation.
Suppose you obtained a business list - scraped or not. Privacy and anti-spam law applies to how you use it, regardless of how it was collected:
None of these ban emailing a business at the address it publishes for that purpose. All of them ban being deceptive or ignoring a no.
Google sells official, licensed access to the same underlying data: the Places API. That is what Maps to Lead uses for every search - no automated browsers, no parsed HTML, no ToS violation.
| Maps scraper | Official Places API (Maps to Lead) | |
|---|---|---|
| Google ToS | Violates it | Compliant - paid, licensed access |
| Legal exposure | Contract claims, unsettled case law | None from Google - it's the product |
| Blocking risk | CAPTCHAs, IP bans, silent failures | No blocking |
| Business continuity | Pipeline can vanish overnight | Stable, supported API |
| Email addresses | Not in Maps at all | Extracted from each business's own website |
The email-enrichment step deserves its own note: Maps to Lead's crawler reads each business's own public website- the homepage and contact page the business published precisely so people can contact it. That is a different activity from scraping Google's platform, both technically and legally: no platform terms are being violated, and the data collected is what the business chose to publish about itself.
No hidden fees. Cancel any time.
Starter
For solo prospectors getting started.
Pro
For growing sales teams and freelancers.
Agency
For agencies and high-volume prospecting.
Generally no - courts (notably in hiQ v. LinkedIn) have been reluctant to treat scraping publicly visible data as criminal hacking. But it does violate Google's Terms of Service, which exposes you to blocks, account termination, and civil contract claims. This isn't legal advice; jurisdiction matters.
Ban: yes, routinely - CAPTCHAs, IP blocks, and account termination are automated and common. Sue: it happens mainly to commercial-scale operations, on breach-of-contract grounds. For most businesses the realistic cost is a lead pipeline that silently breaks.
GDPR cares about use, not just collection. B2B outreach to a business's published contact details can rely on legitimate interest - relevant pitch, honest identification, immediate opt-outs - regardless of the data source. Sole traders' details are personal data under GDPR, so those duties apply in full.
Not of Google Maps. All Maps data comes from the official, paid Google Places API. The email-enrichment step uses our own crawler to read each business's public website - the same pages you'd read in a browser - which involves no Google property at all.
Review texts sit behind the same ToS - bulk-extracting them violates Google's terms, and reviews are also user-generated content with their own copyright questions. The official API exposes rating and review count, which is what Maps to Lead returns for qualification.
Official Google API in, enriched contact list out. From $19/month.
Find leads now