You 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-di

You 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.