01 · Data categories
Separate what is sent, returned, stored, and created downstream.
Inventory account and integration information, request fields, retrieved output, operational metadata, and derived records.
Name each category
Trust Center · Privacy & data handling
Trace representative inputs and output through the selected WebScrapingAPI product and into your systems. Name the purpose, data categories, access owners, retention, deletion, and downstream use at every handoff.
Data handling review frame
Separate account and integration information, request inputs, retrieved output, operational metadata, and downstream records. Assign a purpose and owner to each category.
01 · Data categories
Inventory account and integration information, request fields, retrieved output, operational metadata, and derived records.
Name each category
02 · Purpose and systems
Record why the data is needed, which product or application handles it, where it is delivered, and how the workflow continues.
Map every handoff
03 · Access
Name the customer owner for service credentials, integration permissions, destination access, periodic review, and removal.
Assign access owners
04 · Retention and deletion
Set the required period, deletion event, responsible owner, and treatment of downstream copies or derived records.
Specify the lifecycle
05 · Review source
Use current policies for general information, then identify product configuration, data-flow, customer-control, or commercial questions that need a workload-specific answer.
Link every answer
Selected service
Use the product model to identify what crosses the WebScrapingAPI boundary and which lifecycle decisions stay with the customer environment.
Account and connection information, target requests, customer-run collector, and the output it creates.
Authentication, request inputs, documented API processing, response and error states, and consuming application.
Source coverage, dataset fields, history, update cadence, format, transfer path, and destination.
Source scope, record schema, collection and quality tasks, cadence, delivery method, and destination.
Project-specific privacy review
Bring the selected service, representative inputs and output, intended purpose, connected systems, access groups, retention and deletion requirements, and commercial questions.
01
Follow a request, dataset, or managed delivery from input through WebScrapingAPI to the customer system and downstream consumers.
02
Name the owner for purpose, source scope, service access, destination access, retention, deletion, and downstream use.
03
Connect published answers to current policies and route remaining configuration, data-flow, or commercial requirements to an owner.
Current policies
Use the published destination for general policy information. Send product, configuration, data-flow, and commercial questions with the selected workload.
Read the current WebScrapingAPI privacy notice.
Review current GDPR information and available data-subject routes.
Review current information about cookies used on the website.
Read the current terms for access to WebScrapingAPI services.
Review the current agreement for the contracted service relationship.
Map the product boundary, connected systems, access model, customer controls, and required sources.
Connect business purpose to source scope, minimum record, cadence, and operating ownership.
Share the selected product, representative data map, customer systems, lifecycle requirements, and open questions.
Privacy evaluation
Send the selected service, data categories, connected systems, access owners, retention and deletion requirements, and open approval questions.