Hay all, So i am having trouble with some legal aspects of social network aggregation, in particular advertising.. We are building an aggregated plug and play user/login system and attaching it to many different OS scripts for use as the aggregated social network login for said scripts site.. The way i see it is the data portability aspect, if we allow for example a user to login using facebook then his/her account will be added to our database following the 3rd (or acting) sites database as below.. Facebook connect data > Offsite database > site with aggregated login module. Because by using the data gained by FB connect on our database we can provide much more targeted advertising to the website that has opted to use both our advertising and login module. The second suggestion we had was to have the module self reliant on the acting websites facebook application details.. Eg.. Facebook connect data > Acting website database > Offsite database (us) For this we would only have up to date data as long as the acting website data is up to date, also this would provide alot of double up data (or updated data as the user repeatedly logs in) from any different website.. I know that was alot to take in.. But i really need to know the best legal position to be in to continue coding such a website. Cheers Alex