Data involved in browser sessions
Remote Browser processes the information needed to create, run, observe, meter, and terminate browser sessions. Depending on how a team uses the product, this may include account details, API key metadata, session configuration, profile state, recordings, logs, and billing records.
- Treat CDP URLs and API keys as secrets.
- Avoid entering third-party credentials into profiles unless the account owner authorizes it.
- Use short recording retention where workflows include sensitive information.
Customer responsibility
Teams control what their agents browse, automate, submit, store in profiles, and capture in recordings. Customers should design workflows around consent, access control, data minimization, and deletion requirements for their own users and accounts.
- Create separate profiles for separate users or environments.
- Remove profiles that are no longer needed.
- Review agent prompts and scripts before running them against production accounts.
Questions and requests
For privacy questions, deletion requests, or a copy of current policy documents, use the Remote Browser console or contact the team through the support channel associated with your workspace.
- Use the console for account-specific support.
- Include your workspace identifier when requesting help.
- Do not send API keys or full CDP URLs in support messages.
