Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OneAll Social Network Integration Blocked #811

Open
SchlesserClaude opened this issue Apr 19, 2016 · 6 comments
Open

OneAll Social Network Integration Blocked #811

SchlesserClaude opened this issue Apr 19, 2016 · 6 comments
Labels
broken site DNT policy EFF's Do Not Track policy: www.eff.org/dnt-policy login cookies A sub-category of "broken site" issues; might be common enough for us to try to work around entirely

Comments

@SchlesserClaude
Copy link

SchlesserClaude commented Apr 19, 2016

Hello,

I'm writing on behalf on OneAll:
http://www.oneall.com

Also on Github here:
https://github.com/oneall

We simplify the integration of 30+ social networks and our services are used by more than 300,000 websites worldwide, including small blogs, growing startups and large corporate enterprises.

We also offer a Social Login service, which allows users to login and register with one click on a website/app using their accounts from 30+ social networks.

Several users reported us that Privacy Badger blocks us.

The problem is that by blocking OneAll (especially the API running under *.api.oneall.com), the users that are using Privacy Badger can no longer login with their social network accounts on any websites that are using our services for social login. So these users are basically locked out of their accounts.

This blocking impacts our service and it locks out the users of their accounts on hundreds of thousands of websites.

We do not track users and we have a very strict privacy policy:
http://www.oneall.com/company/data-protection/

How should we proceed?

@DJQuadRocks
Copy link

I can vouch for OneAll. I've been using them for years.

@cooperq
Copy link
Contributor

cooperq commented May 2, 2016

Hi @SchlesserClaude,
Here is some information about how privacy badger works which should help you understand why you are getting blocked an what you can do to fix this issue.
How Privacy Badger decides what to block:
https://privacybadger.org/#Does-Privacy-Badger-contain-a-list-of-blocked-sites
How to get unblocked:
https://privacybadger.org/#-I-am-an-online-advertising-tracking-company.--How-do-I-stop-Privacy-Badger-from-blocking-me

Can you also please send me some example sites where oneall is being used, so I can test it myself?

@SchlesserClaude
Copy link
Author

@cooperq Thank you very much for your answer.

Here a link to our demo:
http://www.oneall.com/services/social-login/

Here we use it for our own login:
https://app.oneall.com/signin/

Here an example customer:
https://www.freshdirect.com/index.jsp

Thank you for your help!

@SchlesserClaude
Copy link
Author

@cooperq Did you have a look at it?

@ghostwords ghostwords added the DNT policy EFF's Do Not Track policy: www.eff.org/dnt-policy label Apr 18, 2017
@ghostwords
Copy link
Member

Hi @SchlesserClaude, would OneAll be able to adopt the EFF Do Not Track policy? If your company can and will abide by the policy's requirements, posting the policy on your domains will tell Privacy Badger to allow loading of resources from those domains. Let me know if you have any questions.

@ghostwords ghostwords added the login cookies A sub-category of "broken site" issues; might be common enough for us to try to work around entirely label Apr 28, 2018
@ghostwords
Copy link
Member

This seems related to #137.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
broken site DNT policy EFF's Do Not Track policy: www.eff.org/dnt-policy login cookies A sub-category of "broken site" issues; might be common enough for us to try to work around entirely
Projects
None yet
Development

No branches or pull requests

4 participants