Changelog 3: Privacy Panel

We shipped the Privacy Panel. Replays are private by default and we follow industry standard for security practices since day one.
profile photo
Jason Laster
Image without caption
We take privacy and security seriously. This is why replays are private by default and we have had industry standard security practices since day one.
But security does not answer the question, “is this replay safe to share publicly”? This is why we’re shipping the Privacy Panel.
The Privacy Panel shines a light on how third party services are using data. For instance, the Privacy Panel above lets you see that CNN includes Adult Swim and Replay's time travel debugger lets you see what cookies it's reading!
We’d love to hear from you. What would you like to see in a Privacy Panel?

Additional Updates

Smart links: Our comments editor now supports formatting GitHub and Replay links.
LogRocket: Opting out of LogRocket will now be stored as an account-level user setting.
Upload panel: We redesigned the Upload panel so that it would be easier to see privacy information and edit sharing settings.

Case Study

Carta is currently showing our valuation as `NaN` which is JavaScript speak for not a number. Checkout out the Loom to see where the bug came from and how we found it.
Related posts
post image
Today we’re excited to share our new Elements Panel. The next time you open a replay and inspect an element you’ll feel the difference.
post image
We’re excited to share an experimental version of Redux DevTools today. If you open a Chrome replay, you’ll see the Redux tab in the bottom right.
post image
Today we’re shipping a big little detail, the processing badge. The next time you open the Test Suite dashboard you’ll see which replays have been processed. And when you open a replay that’s not been processed, you’ll see that we...
Powered by Notaku