I’d like to avoid collecting certain sensitive browser attributes that may trigger sensitivity for device fingerprinting. For example:
It’s possible to write a plugin (in v3 of the tracker) to remove it before it hits the collector, but this will still be after the data has been requested from the browser. I think if you want to exclude parts of the payload entirely it’ll likely need to be integrated in the tracker directly - this is a nice idea for a feature though (particularly in light of privacy sandbox / budgets).
However, I recently noticed a slight issue with this approach which I’m looking to fix in the v3.2.0 release next week. You can currently only delete core payload values, like those described above. Any of the properties like vp (viewport size) or ds (document size) that are calculated for each event are not yet in the payload when the beforeTrack plugin function is fired.
As Mike suggests though, this might still trigger anything in the browser that is looking for something which reads these values. I can open an issue to make it easier to configure which values are captured by the tracker.
I’m using the browser tracker, but I think the same conclusion applies. I’m equally concerned about the appearance of data collection (e.g. reading browser attributes) as actual data collection (sending the event payload), so I may just see if I can (monkey) patch it out for now.
As an aside, I’m less concerned about vp/ds since these have clear use cases; it’s more things like cd and cookie which aren’t typically consumed except in libraries like FingerprintJS Demo.