3 ms·

The kicker for this is whether the user is in control of the amount of masking going on or not. If the app maker is in control, and the user can do nothing but

by myu701 7y ago

The kicker for this is whether the user is in control of the amount of masking going on or not. If the app maker is in control, and the user can do nothing but use the app or not, then while the new defaults are better than nothing, I will continue to have all known FS domain names blocked on my devices / not use said apps at all. Can the user permanently set and forget a "I don't care if the devs want analytics, they aren't getting them from me" flag in the app? If yes, good. If yes by default, better. Can the user see what the analytics wants to unmask? If yes, good. Can they permanently make surgical tweaks to the unmasks to not unmask certain fields? If yes, better and impressive. Edit: the wireframing and reconstructing from xaml views is quite the technical innovation, better than screenshots indeed.

mmastrac 7y ago
We offer a small level of control via the FS.consent API that we have available across platforms (https://developer.fullstory.com/consent https://developer.fullstory.com/consent), but at this time the app maker is really in control. I'd love to have us give better controls to end-users -- we're still investigating ways for users to better control things like that on their own devices. The web makes this a bit easier with adchoices (ie: setting cross-domain cookies opting out) and the ability to more easily block domain patterns with browser plugins. We have an internal team that is dedicated purely to privacy innovation and I'll bring this up with them. > Edit: the wireframing and reconstructing from xaml views is quite the technical innovation, better than screenshots indeed. Thanks! This took us a _long_ time to get right, as you can imagine.
- Dustie 7y ago
  Seems simple enough: To turn on any analytics users should be redirected from the app to the webpage. Anyone that doesn't go there and turn it on should have it off no matter what the app developer does. But I'm guessing you don't really want to make it a user choice.

by myu701 7y ago

mmastrac 7y ago

We offer a small level of control via the FS.consent API that we have available across platforms (https://developer.fullstory.com/consent https://developer.fullstory.com/consent), but at this time the app maker is really in control. I'd love to have us give better controls to end-users -- we're still investigating ways for users to better control things like that on their own devices. The web makes this a bit easier with adchoices (ie: setting cross-domain cookies opting out) and the ability to more easily block domain patterns with browser plugins. We have an internal team that is dedicated purely to privacy innovation and I'll bring this up with them. > Edit: the wireframing and reconstructing from xaml views is quite the technical innovation, better than screenshots indeed. Thanks! This took us a _long_ time to get right, as you can imagine.

Dustie 7y ago
Seems simple enough: To turn on any analytics users should be redirected from the app to the webpage. Anyone that doesn't go there and turn it on should have it off no matter what the app developer does. But I'm guessing you don't really want to make it a user choice.