Attestation
Before a project's first run, someone in your organisation confirms that you may record that hostname: you own the app, a client authorised you, or it is an internal tool. The attestation is stored with who made it and when, and a run against an unattested host is refused before any browser opens. The wizard asks for it when a project is created; the app shows a dialog when a run is refused; create_project takes it as attestation_type.
Attestations are per organisation and per hostname. localhost and IP addresses are not accepted as targets.
Allowed hosts
Each recording runs in a fresh, isolated environment whose network can reach your app's hostname, the hosts named in the guides, and the project's allowed hosts: the API subdomain, the CDN, the auth provider, anything the frontend calls. Everything else is unreachable, which is why a page that loads its data from an unlisted host shows up empty in the video. Set them on the project or with create_project / update_project (allow_hosts).
What we keep
The video, the run report and the run's log stay in your account under your retention setting. Credentials are stored encrypted and typed only inside the browser. The recording environment is destroyed after the run. When a run fails on our side you may send us its evidence with Send failure report; you can withdraw it, and our copy is deleted.
The full rules are in the acceptable use policy.