SaaS Ranking

Named privacy contact in Browser automation and web data

"Contact us" is not a privacy contact. A named officer or a dedicated address is.

4 of 25 vendors we measured here publish it, that is 16%. Last checked 2026-09-06.

16% here against 40% across every category we measure. Browser automation and web data sits below the overall share for this criterion.

Back to Named privacy contact across all categories, or to Browser automation and web data.

Published

A data protection officer or a dedicated privacy address is named.

VendorWhat we found
Axiom https://axiom.ai/privacy-policy/
Browse AI https://www.browse.ai/legal/privacy
Browser Use https://browser-use.com/privacy
Oxylabs https://oxylabs.io/legal/privacy

No named privacy contact 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.

VendorWhat we found
Anchor Browser 7 addresses checked
Apify 7 addresses checked
Bright Data 7 addresses checked
Browserbase 7 addresses checked
Browserless 7 addresses checked
Firecrawl 7 addresses checked
Hyperbrowser 7 addresses checked
Microlink 7 addresses checked
ScrapeGraph 7 addresses checked
ScraperAPI 7 addresses checked
Scrapfly 7 addresses checked
ScrapingAnt 7 addresses checked
ScrapingBee 7 addresses checked
Scrapingdog 7 addresses checked
ScreenshotAPI 7 addresses checked
ScreenshotOne 7 addresses checked
Steel 7 addresses checked
Thum.io 7 addresses checked
Urlbox 7 addresses checked
ZenRows 7 addresses checked
Zyte 7 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.

VendorWhat 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.