How do you handle sensitive data (like passwords, PII, or internal admin panels) in session replays to ensure privacy and security, especially when used for internal feedback?
By "internal feedback" do you mean feedback when a user is logged into an account?
We allow you to do fine-grained censoring of any DOM element by adding class="do-not-track". So if there's a field, or an entire page, that you do not want captured, you can easily mask all of it.
Passwords fields are always censored, and there's no way to disable that.
We also have limited session lengths (up to 30 days), unless a user leaves feedback or a member of the team explicitly saves a moment.
How do you handle sensitive data (like passwords, PII, or internal admin panels) in session replays to ensure privacy and security, especially when used for internal feedback?
By "internal feedback" do you mean feedback when a user is logged into an account?
We allow you to do fine-grained censoring of any DOM element by adding class="do-not-track". So if there's a field, or an entire page, that you do not want captured, you can easily mask all of it.
Passwords fields are always censored, and there's no way to disable that.
We also have limited session lengths (up to 30 days), unless a user leaves feedback or a member of the team explicitly saves a moment.
You can learn more here: https://moment.help.guide/v1/user-manual/time-travel/privacy