3 ms·
Good to see "Privacy: Option to disable full session recordings" is in your roadmap, but I think what a lot of users want is the ability to have full recordings
by hn_throwaway_99 6y ago
Good to see "Privacy: Option to disable full session recordings" is in your roadmap, but I think what a lot of users want is the ability to have full recordings, but have the text on the page "blocked out" and not sent to the server so you don't accidentally scrape up things like credit card numbers or PII. For an example see https://help.fullstory.com/hc/en-us/articles/360044349073-FullStory-Private-by-Default https://help.fullstory.com/hc/en-us/articles/360044349073-Fu....
- XCSme 6y agoYou can already disable keyboard (form) input entirely or on specific fields by adding the "noRecord" class. https://docs.usertrack.net/api/client-side-api#4-disable-tracking-a-text-input-field https://docs.usertrack.net/api/client-side-api#4-disable-tra... Another thing to note is that userTrack uses a custom tracking method that doesn't actually store or send existing page content. This way it is A LOT more efficient and provides much better privacy. This also leads to some limitations in the way session recording and playback works, but for landing pages and static content it works as good as other methods. I have a more detailed explanation about how the session tracking works here: https://docs.usertrack.net/requirements-and-limitations/limitations https://docs.usertrack.net/requirements-and-limitations/limi... EDIT: That FullStory docs page is a really good example of the feature you mentioned. They provide more options than userTrack does for filtering out specific recording input but currently their tracking method also stores more personal data than the one userTrack uses.