4 ms·
I'm sure they had their "permission" on page 27 of the terms of service. This isn't news... My opinion is still that those terms of services are silly. If I ev
by lucb1e 9y ago
I'm sure they had their "permission" on page 27 of the terms of service. This isn't news...
My opinion is still that those terms of services are silly. If I ever do start my own business, one of the things on the checklist is to have a minimal, if any, terms of service, because nobody wants to waste time reading them, and 99% of what is in ToSes is in the law anyway. Except, of course, data collection beyond functional requirements. That would be a good thing to hide in long ToSes.
- deely 9y agoAnd, what happen if some big comp asks you to 'polish' a bit ToS, to make it more 'lawyer style', because otherwise they didn't spent additional $ 10m on you business?
- iovrthoughtthis 9y agoThis is the real bullshit. Other people's lawyers are the worst.
- richforrester 9y agoJust for the record; your lawyers are other people's other people's lawyers.
- dpwm 9y agoStatistically speaking, they're probably not the same "other people's lawyers." As in, you're probably small and they're probably big. Big firms acting for small clients generally doesn't work out so well for the small client.
- zaarn 9y agoPersonally, I'd say no because I value the trust of my users over corporate money.
- nasmorn 9y agoI got this objection once for a mere 100k. The most enterprisey client stalled negotiations for quite some time because we didn’t have long enough TOS. There was no issue with the content just length.
- lucb1e 9y agoWtf, this is a thing?
- emiliobumachar 9y agoI don't know... are they not written in blood, so to speak? For example, I assume all warranty disclaimers include "not even the implied warranty of merchantability or fitness for a particular purpose" because somewhere, in a legal dispute, "no warranty" was not enough.
- dpwm 9y agoAnd if the warranty-disclaimed item had been sold and depending on the nature of the sale, such term probably wouldn't hold up in many jurisdictions. Otherwise such a term can be carte blanche to fraud.
- underwater 9y agoIf you read the TechCrunch article you wouldn't have to guess where it was shown. There is a screenshot of the prompt that shows that the prompt and explanation "Continuously upload info about your contacts like phone numbers and nicknames, and your call and text history." Your solution of hiding this information in a minimal terms of service is strictly worse. My take away is that you can tell users exactly what you're doing and they'll still be outraged. So don't do creepy stuff.
- mehrdadn 9y agoI got my contacts uploaded at some point despite always making sure to reject their prompt. I'm sure people will claim it was just a "bug" or I must have just mistapped (which I have no reason to believe was the case, but how would I prove this), but either way, it's oddly convenient how it works out for them.
- underwater 9y agoThat is worrying. The iOS security model would have served you better; Facebook could never accidentally forget you’d said no.
- mehrdadn 9y ago> That is worrying. Indeed. :\ > The iOS security model would have served you better; Facebook could never accidentally forget you’d said no. Interesting, so you mean this is the case even if I uninstall and reinstall the app? What if I wipe the OS and reinstall (as "cleanly" as is possible)?
- josephg 9y agoIn the iOS security model there's no fixed grab-bag of permissions you accept when an app is installed. Instead the app must explicitly ask for access to each credential on an as-needed basis while the app is running. The request must happen when you request to use that particular feature. And the app is expected to continue working if you say no; just with the corresponding features disabled. So for example, on iOS whatsapp only requests camera access when you try to take a photo in the app. If you say no, facebook can't access the data. Facebook can't conveniently forget that you said no and access the data anyway - if you say no at the system prompt, the OS won't give the app access to that data in the first place. The system isn't perfect - it turns out my mum wasn't getting chat notifications on her iphone because she doesn't know what notifications are and she's been saying no to the prompts. But I find it somewhat refreshing to see beginner users erring on the side of saying no, rather than always saying yes to every random prompt the computer spits out. Fail-private is better than fail-public.
- pdkl95 9y ago> nobody wants to waste time reading them How about a law that requires the party presenting legal paperwork to show that the recipient could have read the document. Use an algorithmic method to estimate the reading time, take off ~33% to account for variance in reading ability, and declare that the minimum time that must be spent with the document. If you cannot show that e.g. someone clicked "I Agree" at lest 5 minutes (or whatever) after they received the ToS text, then the court will assume prima facie that the have not read the ToS and are not responsible for anything in it. The friction this would add to the checkout/signup process grows with the document size, creating an incentive to write short and simple ToS.
- verinus 9y agoNo thank you. How about present your TOS in a form that is understandable by the average user in a span of 2 minutes? Without being a lawyer...(and I doubt you have 2 minutes at all)
- simion314 9y agoThe OP point was that the app creator will be forced to consider how many lines of text will he put in the EULA, if adding such a law with a force timeout and your EULA means the user has to wait 10 minutes you have to think about removing some crap. Don't do creepy things should be a different law
- drawnwren 9y agoVarious ToSes already attempt this. Either by forcing you to scroll to the end, timing you, or by putting verification next to each paragraph. Still, no one reads them. The problem is putting a legal contract before a leisure app. I'd rather see legislation that requires the reading level and length of the ToS to match the reading level and attention span of the average user.
- seanp2k2 9y agoThe problem, as I’m sure you’re aware, is that the reading level and attention span in this case are minimal. People click through ToSes just as they click through installers. Even if the ToS was 5 words on the screen in 36pt bold font saying “WE COLLECT: Text, call, and contact data”, people would still not take the time to read or understand or care about what that actually means. They want to see cat / friend / baby photos, and will mash buttons until that happens, onboarding processes and tutorials be damned.