4 ms·
“You grant Snapchat a world-wide, perpetual, royalty-free, sublicensable, and transferable license to host, store, use, display, reproduce, modify, adapt, edit,
by simonw 11y ago
“You grant Snapchat a world-wide, perpetual, royalty-free, sublicensable, and transferable license to host, store, use, display, reproduce, modify, adapt, edit, publish, create derivative works from, publicly perform, broadcast, distribute, syndicate, promote, exhibit, and publicly display that content in any form and in any and all media or distribution methods”
This exact language shows up in almost every ToS, and every six months or so a dumb news story blows up because someone who isn't a lawyer reads it and gets angry.
I'm not a lawyer either, but I'm going to try to translate it anyway:
"You grant Snapchat a world-wide, perpetual, royalty-free, sublicensable, and transferable license" - you agree that when you upload something to Snapchat you can't turn round later and claim they owe you money for doing so.
"to host, store, use, display, reproduce" = to store the data that you upload and show it back to you (or to other people, presumably based on the semantics of how sharing works within the application)
"modify, adapt, edit, publish, create derivative works from" = create thumbnails. Provide you with an editing interface. Update records in a database relating to the content you uploaded. Build features akin to retweeting on Twitter or resharing or tools that let you add mustaches to your photos or whatever.
"publicly perform, broadcast, distribute, syndicate, promote, exhibit and publicly display that content" = show your content to other people (again, based on the semantics of how those features work in the app).
"in any form and in any and all media or distribution methods" = again, thumbnails, format conversions etc. If someone invents a new media or distribution method, Snapchat should be allowed to build it into their applications without getting you to re-approve the ToS.
I think the fundamental problem here is that ToS need to be written to be as generic as possible. If Snapchat wrote a ToS that legally bound them to the exact way that their app works today, they would have to get a lawyer involved with literally every feature change they make (or feature experiment they run) in the future.
- visakanv 11y agoThis is great, and maybe every ToS should have a plain English version next to it? Shopify does this wonderfully: https://www.shopify.com/legal/terms https://www.shopify.com/legal/terms
- reustle 11y agoThis is what https://tosdr.org https://tosdr.org is trying to do
- gcb0 11y agobut it still can have the other meaning. one does not exclude the other
- noddingham 11y ago"they would have to get a lawyer involved with literally every feature change they make (or feature experiment they run) in the future." Sorry, but I don't see that as a bad thing. Impractical and costly? Maybe. People are on the hook for what they sign up for, so as long as they keep letting this stuff go, they shouldn't be surprised when it goes bad for them.
- celticninja 11y agoGreat, so they have the best of intentions but what happens when they go broke and their data is sold off, the new owners have no obligation to the old users they just own all the pictures and could do whatever they want with it. Additionally who is to say that they don't decide down the line that using user pics for profit is fine and something they want to do. How often do we saw laws enacted for what appears to be good reason and then used for other purposes. Why do we think a for profit company would be better at this sort of thing than a government?
- thrownaway2424 11y agoThe very next sentence which the article doesn't bother mentioning limits the scope of Snapchat's rights under this worldwide perpetual blah blah grant.
- Silhouette 11y agoThis exact language shows up in almost every ToS But almost every TOS is not written for a service whose primary marketing feature is privacy and in particular the transient nature of the communications it sends. The kind of generalised boilerplate you talk about makes sense, at least up to a point, for hosting services or social networks, places like Pinterest or YouTube or Facebook. Even then they are often written more broadly than they need to be to provide the service with reasonable legal security, and this is something that should be challenged IMHO. But for a service like SnapChat, this seems wildly inappropriate and, in particular, unexpected.
- forgottenpass 11y agoI think the fundamental problem here is that ToS need to be written to be as generic as possible. If Snapchat wrote a ToS that legally bound them to the exact way that their app works today, they would have to get a lawyer involved with literally every feature change they make (or feature experiment they run) in the future. The very reason most people use snapchat in the first place is that they expect a very limited featureset with tight controls. It rightly should be a cause for concern that they're making way for expanding the scope of the service.