Copyright and scraped data What you actually own after a scrape

Copyright protects expression, not facts

The single most useful thing to understand about copyright and scraped data is this: copyright protects original creative expression, not raw facts. A business name, a street address, a phone number, and a star rating are facts. Nobody invented them in a creative sense, so nobody holds a copyright over the fact itself.

The U.S. Copyright Office is explicit that ideas, procedures, and mere listings of information without original authorship are not protected. That is why a phone directory of names and numbers, arranged in the obvious alphabetical way, has historically been treated as uncopyrightable. What copyright can reach is the original way facts are selected, coordinated, and arranged into something expressive.

So when you capture a list of local businesses from Google Maps, the individual data points are not somebody's copyrighted work. This is educational context, not legal advice, and the picture gets more nuanced once you look at compilations, databases, and the terms you agreed to. Let us walk through each layer.

Where a copyright can appear

The classic reference point in the United States is the Supreme Court decision in Feist Publications v. Rural Telephone, which held that a plain white pages directory lacked the minimal creativity needed for copyright. Facts are free for all to use, and a simple, mechanical arrangement of them adds nothing protectable.

The flip side is that a genuinely original compilation can be protected, but only in its creative selection and arrangement, never in the underlying facts. If you copy someone's curated, editorially organized directory wholesale, you may be copying their expression. If you gather the same facts yourself and organize them your own way, you are not.

Review text is a useful edge case. A single star rating is a fact. A long, personally written review is creative expression and can carry its own copyright held by its author. That distinction matters when you think about what you store and display, and it is one reason Vonsel treats reviews as signals to analyze rather than content to republish.

Database rights are a separate layer

Outside the copyright question, the European Union created a distinct protection worth knowing about. Under the EU Database Directive, a maker who puts substantial investment into obtaining, verifying, or presenting the contents of a database can hold a sui generis database right, even when no single fact is copyrightable.

That right can be infringed by extracting or reusing a substantial part of a protected database. In practice this is aimed at wholesale copying of large curated datasets, not at a salesperson compiling a modest list of local prospects. Still, it is why the smart move is to build your own database from primary facts and add your own investment on top, rather than lift someone else's finished dataset.

The encouraging read for a legitimate user is that the same principle protects you. When you invest effort to clean, enrich, and structure a list, the resulting compilation is genuinely your work product, not a copy of anyone else's.

Terms, privacy, and platform limits

Copyright is only one lens. A platform's terms of service is a contract, and those terms often restrict automated access regardless of whether the data is copyrightable. That contractual question is independent of copyright, and we cover it in more depth in is it legal to scrape Google Maps and in our terms of service explainer.

Privacy law is a third track. When a record identifies a person, such as an owner's personal mobile or a named individual, data protection rules like the GDPR may apply on top of everything else. Business contact details for a company are treated more leniently in many places than personal data, but the safe posture is to focus on business information and honor opt outs.

There are also practical platform limits that are neither copyright nor privacy. Maps typically returns up to around 120 results per search, and aggressive automated access can trigger CAPTCHAs, rate limits, or blocks. Those are engineering realities, and they are one more reason to prefer a measured, browser based capture over hammering the site.

How to stay on the safe side

The extension is the means, the database is the end

The Vonsel Chrome extension is simply the means: it captures business facts from Google Maps at a sensible pace and hands them to the dashboard. What matters legally and commercially is what happens next. Inside Vonsel, that raw material becomes a mapped CRM with reviews intelligence, AI email drafted per business, and a database enriched and contextualized with the pain points that make it useful.

That transformation is the whole point of this article. A pile of copied facts is fragile and generic. A dataset you have selected, cleaned, structured, and enriched with your own work is genuinely your own, and far more valuable to sell from or sell into. For the wider tradeoffs of raw data versus a real asset, compare scraped Maps data against bought lists.

None of this is a substitute for advice from a qualified lawyer in your jurisdiction, and rules differ by country. The goal here is to give you an accurate mental model so you can build responsibly and browse the rest of our legal library with more confidence.