Firecrawl Content Data Handling

Overview

Treat scraped pages, metadata, screenshots, file parses, and model-extracted JSON as untrusted external data. Preserve provenance while storing only what the approved use case requires.

Prerequisites

• The target repository or integration path and the requested operator outcome.
• The source authorization, data classification, and environment policy.
• Current Firecrawl documentation, credentials only when needed, and an owner for approvals.

Current Contract

SDKs return document data directly; REST returns it under data. metadata.sourceURL and metadata.statusCode are essential provenance and quality fields. storeInCache, zeroDataRetention, lockdown, screenshots, raw HTML, file upload, and persistent browser profiles create materially different data-handling obligations.

Authentication