November 15, 2013 - JFBConnect v5.2.1 Released - Autotune fixes and other minor updates - Read the full changelog
November 8, 2013 - JFBConnect v5.2.0 released - Twitter Authentication and more.
Hi, hoping you can help
I've been looking into the legalities of using this component (which looks amazing by the way) on a clients website that I'm currently developing. However, my understanding of the legalities of ownership of data, and it's declaration, are rather confusing.
The way I understand it, is that Facebook still own all the data that this component will import across to the Joomla site. Email address, contact photo, everything. Obviously any connection of data from another source needs to be legally outlined correctly first.
So far I've written this:
FACEBOOK CONNECT REGISTRATION: Acting in agreement with the terms and conditions as set out by Facebook (http://www.facebook.com/legal/terms), any content, data or information provided through Facebook will remain under ownership of Facebook. In using the Facebook Connect service on the Site, you agree to allow THE SITE access to details and information held by Facebook.
Anyway, because of the fact I'm not a solicitor/lawyer, I'm looking to see if anyone can point me in the direct of correct (legally sound) examples of text used within a site's Terms & Conditions document when addressing this issue.
Thanks in advance, I'm very much looking forward to using this component!
Sorry for the delayed response. This isn't a question we've been asked before
First off, the Facebook platform policies are on the following page, which are different than the main Facebook terms:
Specifically, you'd be interested in the "II. Storing and Using Data You Receive From Us" section. If you read through it, there's no where that the data is stated to belong to Facebook. Per Facebook's privacy policies, that data actually belongs to the user, but is stored on Facebook.
The authentication popup dialog when a user clicks the Login With Facebook button actually has a link to Facebook's terms and shows the user what data is going to be imported. So, by doing that, the user is explicitly agreeing to Facebook's terms and allowing your application access to the user's own data stored on Facebook.
While it's definitely a good idea to have extra terms and policies laid out on your site, I don't know if you need an additional term for importing data. Facebook does have a method when setting up your Facebook application where you can include a link to your own privacy and terms URLs. Those URLs will be shown during the authentication process in addition to the link to Facebook's terms.
Hope that all explains, though I'm certainly not a lawyer either.