6 ms·
Umm has anyone read the lisc. for this application? https://keybase.io/docs/terms https://keybase.io/docs/terms When providing Keybase or the Service with con
by Meph504 10y ago
Umm has anyone read the lisc. for this application?
https://keybase.io/docs/terms https://keybase.io/docs/terms
When providing Keybase or the Service with content, such as your name, username, photos, social media names, data or files, or causing content to be posted, stored or transmitted using or through the Service (“Your Content”), including but not limited to the Registration Data and any other personal identification information that you provide, you hereby grant to us a non-exclusive, worldwide, perpetual, irrevocable, royalty-free, transferable (in whole or in part), fully-paid and sublicensable right, subject to the Privacy Policy, to use, reproduce, modify, transmit, display and distribute Your Content in any media known now or developed in the future, in connection with our provision of the Service. Further, to the fullest extent permitted under applicable law, you waive your moral rights and promise not to assert such rights or any other intellectual property or publicity rights against us, our sublicensees, or our assignees.
That's a bridge too far, and someone needs to dial this back.
- bduerst 10y agoIsn't that boilerplate legalese for a service that lets you upload, edit, and share media?
- Meph504 10y agothere are key additional phrases that subtly make it different, like the fact, that this is transferable. And though not uncommon, using the term "provision of service" leaves the door wide open to your contents usage, because the lisc. is non-revocable, and perpetual. If say, in 3 years from now as a provision of their service they offer analytics, or direct marketing. they can use any of your content for that. I get this is probably just a wide net they are casting to not box themselves in, but it's something that is super restrictive to the user. And being as they also have a section require arbitration, and barring class action suits. If they are acquired by, or decided become a bad actor, then you are pretty much SOL.
- deleted 10y ago[deleted]
- dangoor 10y agoNote the "in connection with our provision of the Service". This largely looks to me like a standard set of terms that they require in order to not get sued for shuffling around your content just to provide the service you're signing up for. While the rest of the paragraph looks standard to me, I'm not completely sure about that last sentence. Is that what you're wondering about?
- adambrenecki 10y ago> in connection with our provision of the Service. This is pretty much boilerplate legalese that's generally intended to mean "you can't upload a file to your public folder, then sue us for copyright infringement because that file is in a public folder". Lawyers seem like to cover their clients' asses as much as possible, but for a service like this that's designed for privacy-conscious people it'd do them well to step back and think about how the license comes across to privacy-conscious laypeople. From what I've seen of Keybase, from back when they were just an alternative to the PGP Web of Trust to now, I don't think they're genuinely planning anything nefarious (but they'd still do well to have a ToS that reflects that).
- nihonde 10y agoWhat you're describing is "for the sole purpose of proving the service to you". The "in connection with" language is much broader. Whether the license is intended to give them more leeway or not is a different question.
- donovanm 10y agoDoes this mean that you are giving them the right to use any data transmitted through the service? Including your own personal messages?
- whodknee 10y agoNo, from what I can tell it is them asking not to be sued to for providing the service they signed up for. That is, looking at your social media profiles to verify your identity across profiles. Even if it did mean that, it would be of 0 use to them because they are fully end-to-end encrypted
- deleted 10y ago[deleted]