Data processing agreement in Browser automation and web data
Without a published DPA you cannot review the contract before you talk to sales.
7 of 25 vendors we measured here publish it, that is 28%. Last checked 2026-09-06.
28% here against 12% across every category we measure. Browser automation and web data sits above the overall share for this criterion.
Back to Data processing agreement across all categories, or to Browser automation and web data.
Published
Published and readable without a login.
No data processing agreement found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Anchor Browser | 8 addresses checked |
| Apify | 8 addresses checked |
| Axiom | 8 addresses checked |
| Bright Data | 8 addresses checked |
| Browse AI | 8 addresses checked |
| Browserbase | 8 addresses checked |
| Browserless | 8 addresses checked |
| Firecrawl | 8 addresses checked |
| Hyperbrowser | 8 addresses checked |
| Oxylabs | 8 addresses checked |
| ScrapeGraph | 8 addresses checked |
| ScraperAPI | 8 addresses checked |
| ScreenshotAPI | 8 addresses checked |
| ScreenshotOne | 8 addresses checked |
| Steel | 8 addresses checked |
| Thum.io | 8 addresses checked |
| Urlbox | 8 addresses checked |
| Zyte | 8 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| Scrnify | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.