Chrome Web Store Privacy API

Endpoint facts

Method

GET

API path

/chromewebstore/privacy

Auth

apiKey

Credits

1 credit/request

Platform

ChromeWebStore

Response schema

#/definitions/chromewebstore.privacyResponseDoc

MCP tool

chromewebstore_privacy

Overview

Returns an extension's privacy disclosures as the store renders them: the developer's data-use statement, whether it collects data, the standard data-handling declarations, and the privacy-policy link. Defaults: `country=us`, `lang=en`. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

Response behavior

- `disclosure` is the developer's data-use statement; `collects_data` reflects whether it declares collecting or using data; `data_collected` lists the data categories it declares handling (empty when it collects nothing); `declarations` is the list of standard data-handling declarations the store shows; `privacy_policy` is the developer's privacy-policy link. - An unknown item id returns a typed not-found error (HTTP 404). A blocked or shape-changed upstream response is returned as a typed upstream error (HTTP 503). Example response (a data-collecting extension): ```json { "code": 200, "msg": "OK", "data": { "id": "kbfnbcaeplbcioakkpcpgfkobkghlhen", "name": "Grammarly: AI Writing Assistant", "collects_data": true, "data_collected": [ "Personally identifiable information", "Personal communications", "Location", "User activity", "Website content" ], "disclosure": "Grammarly … has disclosed the following information regarding the collection and usage of your data.", "declarations": [ "Not being sold to third parties, outside of the approved use cases", "Not being used or transferred for purposes that are unrelated to the item's core functionality", "Not being used or transferred to determine creditworthiness or for lending purposes" ], "privacy_policy": "https://www.grammarly.com/privacy-policy", "url": "https://chromewebstore.google.com/detail/kbfnbcaeplbcioakkpcpgfkobkghlhen" } } ``` An extension that collects nothing returns `collects_data: false` and an empty `data_collected`, with a "will not collect or use your data" disclosure.

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related