4 ms·
I think transparency is always good, although one worry I do have is that forcing benign declarations (i.e. what amounts to disclosing that when you turn on X,
by g_p 4y ago
I think transparency is always good, although one worry I do have is that forcing benign declarations (i.e. what amounts to disclosing that when you turn on X, it does X), creates something similar to "alert fatigue".
People don't read privacy policies. A privacy preserving app that has to put a long-winded policy, despite not leeching your data, becomes even harder to distinguish from a cloud-based email app that scans all your emails, and holds your email usernames and passwords, and harvests contact-name pairings and sells email signature contact info and job titles to lead-harvesting data brokers.
I don't know if that's the best outcome for users, as it might make every policy look the same (long, complex, and wordy, with scary legal language they are forced to add by the platform gatekeeper).
- brewdad 4y ago>I think transparency is always good, although one worry I do have is that forcing benign declarations (i.e. what amounts to disclosing that when you turn on X, it does X), creates something similar to "alert fatigue". My favorite unnecessary warning label is the one on the bag of frozen shrimp I bought at Costco. There's a government mandated "Warning: Contains shellfish (shrimp)" Thanks.
- deleted 4y ago[deleted]
- jacksnipe 4y agoI don’t think this is about alerting users where data is going proactively; I think this is about having an accounting of where data is being sent, so that we can answer questions about data flows after the fact.