Jump to content

Recommended Posts

Posted (edited)

Face book integration requires that the privacy policy includes the following :

 

 

1. Privacy policy needs to explain what data you are collecting from users

2. Privacy policy needs to have  a clear explanation of what purposes the app is using that data.

3 .Privacy Policy  should have clear explanation of how the data is deleted

 

What  to include to cover the above in the policy in relation to  facebook login app ?

 

Edited by Marafa
Posted

That is only a question you can answer. What info do you ask from your members outside of just a user name, email and password?  

The email is used to validate a user and ensure access to the account is only to to user linked to that email. Anything else you need to justify why you’re asking for it.  (Such as DOB if you verify age etc). 

Again a default privacy policy is included but because IPB can’t enforce how data is deleted they can’t answer that for you. 

Posted

Walk through your registration process?  What do you ask from your user?  Do you ask them to complete a profile after registration?  That’s the info you collect. 

And how is it deleted?  IPB does not delete info automatically. That’s done by you. What’s YOUR policy if someone wants to remove their account?  Do you allow accounts to be deleted?  Do you anonymize posts made or delete them if the account is removed?  

These questions are about your site’s policy and procedures. It can’t be dictated by software. If you don’t have these policies documented, this would be a good time to do so.  

Posted (edited)

You might consider reading some of the privacy policies from some of the Enterprise customers using this software to see how they address the data they collect. They should be able to allow you to figure out what things you should address in your site's privacy policy which should put you in a better position of being approved by Facebook.  

You will also have to audit every app and plugin you install to determine if it collects any personally identifiable data points and include them as well.  

If you delete a user there is a possibility that an app or plugin they used might not delete or anyomize the data it collected during use.  This may impact on whether or not you choose to use it or not. 

 

 

 

Edited by Chris Anderson
Posted (edited)

Privacy laws will likely evolve over the coming years so it's best to keep abreast of their requirements as well. 

Payment processors may also review your site guidelines and privacy policy and if it doesn't meet their internal requirements you might have your account placed on hold or closed.

One privacy policy trend is to include a brief set of explanations for each section highlighting the overall gist of it. 

You need to ensure you address you and your customer's interests and all the legal and payment processor requirements you may be bound to in both a simplistic and legally binding manner which often times requires lots and lots of words as way of explanation and to minimize legal exposure. 

Doing your privacy policy entirely on your own provides about a dollars worth of protection.  If your exposure is greater than that then you should seek out someone with privacy expertise to assist you in creating a comprehensive site guidelines and privacy policy.  

Edited by Chris Anderson
Posted

If you go through what others have suggested above, that will indeed get you a decent privacy policy. As was mentioned by Chris, often taking a look at what others have done can be extremely helpful too

  • 3 weeks later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...