Bright Data Security and Use Review

Overview

Treat legal purpose, public-data scope, account roles, zone isolation, and application controls as one authorization chain. Provider access does not replace the customer's duty to restrict targets, fields, retention, and downstream use.

Prerequisites

• An integration inventory and named business and data owner
• The Bright Data acceptable-use and account-role documentation
• Secret-manager, egress, retention, and incident-response controls

Instructions

Step 1: Approve purpose and targets

Read the use case and Grep manifests for authenticated pages, personal or sensitive fields, messaging, purchases, account creation, or other prohibited activity. Refuse nonpublic information behind login.

Step 2: Minimize identity