Test Replay automatically redacts sensitive values from captured network logs before that data reaches Cypress Cloud.
If your team turned Test Replay off in the past because of what your network logs held, this is the change that may let you turn it back on. You keep full CI debugging, and the values you didn't want stored are removed on your machine before Test Replay data is uploaded.
Redaction is on by default, and you can turn it off for one project at a time in project settings.
What gets redacted
Redaction covers authorization and credential-like values most likely to be sensitive. Each redacted value appears as (redacted) in the network log.
Everything else stays. Request timing, status codes, and the structure around each request are captured the way they always were, so you keep enough context to debug a failing request without the values themselves.
The full list of redacted values lives in the Test Replay redaction docs.
Who can see Test Replay data
Test Replay data, including the network log, is visible to everyone with access to your project. In a private project, only people invited to your organization with the required team roles can see them. In a public project, any Cloud user can see the runs and the Test Replay data.
Redaction narrows what sits in that Test Replay data. If you are interested in managing access to Test Replay itself, review your project access controls.
What we're still working on
We built redaction from customer feedback. If you see a value that should be redacted and isn't, raise it with your account team.
For the full redacted-value list, where redaction runs, and how to turn it off, see the Test Replay redaction docs.