4 ms·
How do you feel about a 30 page TOS and privacy policy being necessary to use said app? Something of that length tells me that the company likely wants to get a
by telchar 7y ago
How do you feel about a 30 page TOS and privacy policy being necessary to use said app? Something of that length tells me that the company likely wants to get a lot of data from me. Reading it is hardly necessary with the way these are typically written to be as friendly to whatever the company wants to do as possible.
This is why I have never used the Bluetooth features on my QC35s. They're mostly dumb headphones to me since I won't accept their user agreement. This seems counterproductive for the company, unless they simply don't care about user privacy and expect users to roll over.
- mmjaa 7y agoThis is why I never work in a technical capacity where I am being 'managed' by lawyers and other non-technically competent means of business org. I truly do believe, as do you, that the TOS and Warranty world is another desperate subject from where the execs/lawyers/owners of the company desire to eek every penny. There are many other realms where the TOS is simply: use the thing, have fun with it, if you want to tell us about yourself, press this button/fill in this card. For sure, consumers 'never read the TOS', because - hopefully - the device is now set up, everything works, it is time to rock .. For sure, tech can be used against the user. But it can also work for the user, too.
- telchar 7y agoI think the shame of it is that 95% of most TOS's are as you said, essentially harmless or nearly harmless boilerplate. My concern is more about privacy policies which could in many cases be very short if user privacy is being respected. In either case, if I'm presented with pages upon pages of small font #888888 text, I defensively assume these is something nefarious hidden there (e.g. "we don't share any of your data with anyone except our 3rd party affiliates, marketing partners, your nosy relatives, people who claim to be law enforcement, anyone who wants to connect to our open s3 buckets, etc.") I would hope there could at least be standardized agreements developed so that I could decide which I'm okay with or not and have enough companies using them to make it worth the effort to read once. I'm thinking of various flavors of FOSS or CC licenses as an idea template.