Legal experts warn Meta's new terms still grant broad scraping permissions
niemanlab.org
niemanlab.org
Never rely on robots.txt. Configure it, but do not rely on it. A bot will do what a bot can do. Their bots are trivial to spot so close the connection, bonus if done silently closing the socket and inhibiting first RST from web daemon and second RST from the OS.
Make of that what you will.
flat files, a tarpit, maybe zip bombs as the sibling suggested. Nothing calculated. I'd go with zipped Brothers Grimm
> All rights reserved. No part of this book may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without permission in writing from the publisher.
For AI, wasn't the book first "reproduced or transmitted" into a training system?
How would we reformulate it today?
Not once have I had someone I work for in this capacity even ask about robots.txt
Similar to saying world hunger would be solved in everyone who could donated $100 to those in need. Sure it may be true but foot stomping about why isn’t it organically happening is missing the point.
But, because this person could be anyone, anywhere your words are hollow and empty. You are impotent to stop their future actions.
The internet is not a society. The internet is all societies. Hell, more and more it's not even human societies.
And may be or could be part of the solution by them taking upon themself to implement it in an ethical manner by having the bots and scrapers respect robots.txt; unless the spec specifically says not to in that case I agree with finding new clients or another job
The internet is built on scrapers though - Google is a scraper, and an opt-out one at that.
Conversely, if an obviously automated visitor does not fetch robots.txt, that can be an instant ban, kind of like a reverse honey pot, if you will.
So it can have some nonzero value in the overall context; it's just silly to think of it as a blocking mechanism.
In short, robots.txt documents what access is allowed; it states the policy. Enforcing it the job of something else.
Someone you work for in this capacity shouldn't ask about robots.txt because that's the sort of detail for which they have you to deal with.
I've enjoyed the arms race with scrapers as they have taught me a lot over the years. Some of them leave me funny messages in my logs and seem to enjoy working around my crude mitigations almost as if it were a puzzle. Which of your scrapers can parse this post without the help of a real browser or headless chrome? [1] I am curious how far the tools have evolved and how someone with your experience instruments them if you are willing to share.
I suggest doing it, actually. Could be a fun project. I suggest not making the script make any extra requests on your main account just in case - anything already on the page is free for scraping.
Whilst I assume you meant to say “scrape”, I can’t help but appreciate the poetry of that typo.
I would never in a thousand years accept such a one-sided, despicable business relationship as their proposed terms seek to establish.
It's already bad enough they hoover up your customer lists and cross-link to their own - for purposes of gaining insight on individuals who never consented to it.
Now they're trying to use their monopoly over a form of social networking to bully you into arbitrary contract terms for a largely unrelated product.
You don't need Meta as much as you think. And in aggregate, they need their customers far more than those customers need them.
There are much friendlier ecosystems in which to engage with your users.
My bank advertises with Meta and included my account in some kind of upload list (probably Meta Ads Manager). I noticed their logo while poking around in Facebook's settings, under Audience-based Advertising. I was livid.
As far as I'm concerned they had no business telling a creepy company like Meta who I bank with. I certainly never consented to that.
I dug up my original banking agreement - a 5-page document on aging, yellowed parchment that I signed over a decade ago. Nothing in there about them being able to unilaterally change terms without notice. I also printed out their latest, 30+ page standard banking agreement which (after making inquiries) they seemed to think applied to my account.
I brought both in to my bank manager and put them on the table. At a high level, I pointed how ridiculous the size had grown to, and he was sympathetic.
In terms of details, I'd highlighted several portions that pertain to privacy, and we walked through the differences together. I underscored how none of them were needed to provide me banking services, how the benefits they conveyed were solely to TD, and how they were harmful to me as a customer.
In the end, he agreed to formally acknowledge on file that I did not agree to the new terms.
You may disagree over how much effect that will have in practice, but the acknowledgment was not just a bureaucratic exercise. It established very firm evidence that I never agreed to the new contract, or any terms the bank might rely on as a basis for the objectionable practices. It would become material if those practices cause me damage in the future, significant enough to litigate. i.e. They knew they lacked agreement, and continued to provide me banking services.
He also worked with internal departments to toggle all available opt-out flags.
I was fortunate in this case the manager comprehended my concerns and seemed to want to keep me as a customer. I recognize not everyone would necessarily get as far.
It really disgusts me that some of the most degenerate practices of silicon valley are spreading to other industries. With lawyers more broadly adopting some of the most viciously one-sided legal language big tech pioneered.
I for one am not on board, and refuse to be bullied into providing some kind of imaginary consent. I say 'imaginary', because I don't think anyone in their right mind who reads and understands such terms would ever agree to them willingly.
The Danger List
Your robots.txt "Do Not Scrape" signs become legally useless: robots.txt is just a voluntary preference, not a law. While Meta says in PR statements that it will respect robots.txt, it left that promise out of the binding legal contract. By keeping your business account active, you are signing a contract that legally authorizes Meta to ignore your site’s block-lists.
- Meta can create fake accounts to bypass registration walls: The terms explicitly authorize Meta to "create test credentials" to crawl your site. Legal experts warn this gives Meta permission to sign up as a fake user to scrape gated content behind login screens or basic paywalls that anonymous bots usually can't see.
- Your entire domain is fair game, not just links you post: Because the terms cover any domain "associated with your products or services" (or shared by regular users on Meta), Meta isn't just scraping the specific landing pages you run ads for—it has a green light to crawl your entire website from top to bottom.
- AI training is still allowed through a backdoor: Removing the word "train" is a PR smokescreen. The contract still lets Meta scrape your site to "develop, improve, and research... advertising and business products." Because "business products" isn't strictly defined—and Meta builds AI tools for businesses "developing" legally covers training AI models on your proprietary articles, data, and work.
- Third-party companies get the same access: The terms grant these scraping rights to "any entity acting on our behalf," meaning external contractors or third-party scraping vendors hired by Meta also have legal cover to harvest your site.
- It is a non-negotiable hostage situation (Zero Opt-Out): There is no toggle or form to reject this before the October 30 deadline. Your only legal way to decline is to completely delete your commercial presence across Facebook, Instagram, Threads, and WhatsApp—forcing you to choose between surrendering your content for free or losing access to your audience.
The Bottom Line: Starting October 30, their updated terms give it sweeping permission to scrape entire websites linked to any Meta Business account (Facebook, Instagram, Threads, WhatsApp). Despite a last-minute wording tweak after backlash, legal experts warn the rules still let Meta harvest publisher content to build AI tools—with zero option to opt out.
1. What Exact Things Can Meta Do?
If you have a Meta Business account, you authorize Meta (and its third-party partners) to:
a) Deploy automated bots: Use web scrapers, crawlers, spiders, and user agents on your site. b) Bypass basic walls: Create "test credentials" to access, index, cache, analyze, and collect your content. c) Monitor continuously: Periodically pull updates from your domains, web pages, and URLs.
2. What is the Extent of the Scraping? - What gets scraped: Any domain, webpage, URL, or content "associated with" your business or shared by users on Meta platforms. Legal experts note this is broad enough to let Meta scrape entire websites, not just specific landing pages. - - Who it affects: Virtually every news organization and business that uses a Meta account to manage Facebook Pages, Instagram profiles, Threads, or WhatsApp channels.
How it expanded:
- Previously: Meta could only scrape your site if you specifically used its generative AI ad features, and only to "optimize your ads."
- Now: It applies to all business accounts by default, and scraped data can be used for all "advertising and business products" (plus platform security/integrity).
3. Why Legal Experts Say Meta's "Fix" Changes Nothing
After initial outrage, Meta revised the text on Friday to remove the word "train" and claimed it still respects robots.txt (the code websites use to block scrapers). Legal experts aren't buying it for three reasons:- "Develop" still means "Train": Meta replaced "train" with permission to "develop, improve, research, and maintain advertising and business products." Attorneys point out that "business products" isn't strictly defined, and "developing" AI business tools naturally includes training AI models on your data.
- The robots.txt loophole: While a Meta spokesperson publicly promised to respect robots.txt flags, Meta refused to put that promise into the actual legal terms. Because robots.txt is voluntary, signing a contract that explicitly authorizes scraping legally overrides your robots.txt preferences.
- Take it or leave it: There is no opt-out. To avoid giving Meta permission to scrape their websites, businesses and news outlets would have to abandon Facebook, Instagram, Threads, and WhatsApp entirely before October 30.