Live data from Hacker News

Terms of Service update

google.com

1–10 of 43 posts

Re: Terms of Service update

#2
> So if you’re asked for your password, think twice and consider whether there might be safer and more secure ways to share the information.

Interesting, given the recent hullabaloo around people submitting their Gmail credentials to Linked In for contact-scraping.

From some of the technical measures Google outlines as 'unusual activity' it sounds like they might be closing that hole...

Re: Terms of Service update

#4

    We are updating the Google Terms of Service. The new Terms will go
    live on November 11, 2013 and you can read them here.

    Because many of you are allergic to legalese, here’s a plain English
    summary for your convenience.
Why not just write your TOS in plain English, then? Also, if a company supplies both a "legalese" version and a "plain English" version that differ, which one takes precedent?

Re: Terms of Service update

#6
post #4

We are updating the Google Terms of Service. The new Terms will go live on November 11, 2013 and you can read them here. Because many of you are allergic to legalese, here’s a plain English summary for your convenience. Why not just write your TOS in plain English, then? Also, if a company supplies both a "legalese" version and a "plain English" version that differ, which one takes precedent?

The legalese.

(And I agree.)

Re: Terms of Service update

#7
post #4

We are updating the Google Terms of Service. The new Terms will go live on November 11, 2013 and you can read them here. Because many of you are allergic to legalese, here’s a plain English summary for your convenience. Why not just write your TOS in plain English, then? Also, if a company supplies both a "legalese" version and a "plain English" version that differ, which one takes precedent?

I believe the legalese version is the actual one and it offers protection in front a court.

As for the plain English, I think is because in law you have to be very explicit in order to do not leave any holes.

Re: Terms of Service update

#8
post #4

We are updating the Google Terms of Service. The new Terms will go live on November 11, 2013 and you can read them here. Because many of you are allergic to legalese, here’s a plain English summary for your convenience. Why not just write your TOS in plain English, then? Also, if a company supplies both a "legalese" version and a "plain English" version that differ, which one takes precedent?

Technically, the legalese version is written in plain English. ;)

But snark aside, I don't think this plain English version is all that enforceable since it doesn't mention at any point about being a contract that you're agreeing to. IANAL, but I think this is part of why the actual TOS isn't written in "normal English". All the stuff that makes it binding (or is supposed to, anyway) and prevents lawyers from twisting the words is what we call legalese.

I don't so much blame companies for this sorry state, but the legal system and the lawyers who inhabit it. Google and the like are just doing what they must to navigate in that environment.

Re: Terms of Service update

#9
post #4

We are updating the Google Terms of Service. The new Terms will go live on November 11, 2013 and you can read them here. Because many of you are allergic to legalese, here’s a plain English summary for your convenience. Why not just write your TOS in plain English, then? Also, if a company supplies both a "legalese" version and a "plain English" version that differ, which one takes precedent?

"Plain English" is the legal equivalent of pseudocode. (By similar reasoning, the courts are analogous to CPUs.)

The TOS isn't in plain English for the same reason that Android isn't written in pseudocode: the CPUs won't run it.

Also -- pseudocode ignores edge cases, boundary conditions, etc. to make it readable. Production code (and legal documents) can't escape these requirements.

Re: Terms of Service update

#10
post #5

Diff: https://www.google.com/policies/terms/archive/20120301-20131...

Thank you! Most interesting bit imo:

"If you have a Google Account, we may display your Profile name, Profile photo, and actions you take on Google or on third-party applications connected to your Google Account (such as +1’s, reviews you write and comments you post) in our Services, including displaying in ads and other commercial contexts. We will respect the choices you make to limit sharing or visibility settings in your Google Account. For example, you can choose your settings so your name and photo do not appear in an ad."

Now the question is where are the settings? I assume it will be allowed by default. Will my choice be respected in the long run?

Post reply on HN