Social login data paths

Where WordPress social login plugins send visitor data

A Continue with Google, Facebook, or X button can load a login script from that provider when the page opens, even if the visitor never clicks it. Other setups keep the buttons on your site and send the visitor to the provider only after a click. Outside scripts used in comment forms can contact providers on pages showing those forms, even when visitors do not sign in. Requests to the provider include an IP address and browser information. This table describes the setups below; your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group social login plugins

We compare the social login setups named below. A plugin that keeps Continue with Google, Facebook, or X buttons on your site and sends the visitor to that provider only after a click is different from a plugin that loads an outside login or comments script when the page opens. Google sign-in, Facebook comments, and X sign-in are separate outside services. Outside scripts used in comment forms can contact providers on pages showing those forms, even when visitors do not sign in. We have not tested consent timing or how long login-provider logs are kept.

Social login plugins

No paid placement. Buttons hosted on your site first, then outside login scripts, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented service domainsHow long data is keptBefore consentLinksSource
Nextend Social Login

This row covers Nextend Social Login when Continue with Google, Facebook, or X buttons are shown. The buttons are hosted on your site. Clicking one sends the visitor to that provider to sign in. A Google or Facebook login script is not documented as loading for every visitor before that click. Adding the buttons to comments is a different placement, not a different script host. Consent timing is not tested here.

Buttons hosted on your siteNo outside login script documented on page load for this setup. Clicking a provider still sends the visitor there. Other page requests are not covered.Not assessedNot tested
  • None
Log in with Google

This row covers Log in with Google when One Tap is set to load on the whole site. The page loads a Google sign-in script from accounts.google.com for every visitor, including people who never sign in. Login-page-only One Tap is a different setup and is not this row. Consent timing is not tested here.

Outside login script on page loadaccounts.google.comNot assessedNot tested
  • None
Social Login (OneAll)

With a OneAll subdomain configured, the plugin loads an outside login script on front-end pages, even where login buttons are not shown. Consent timing is not tested here.

Outside login script on page loadconfigured subdomain of api.oneall.comNot assessedNot tested
  • None
Social Login, Social Sharing by miniOrange

This row covers Social Login, Social Sharing by miniOrange when Facebook comments are enabled on posts. The page loads a Facebook comments script from connect.facebook.net, so every post with comments can contact Facebook even if the visitor never logs in. Login buttons without Facebook comments are a different setup and are not this row. Consent timing is not tested here.

Outside login script on page loadconnect.facebook.netNot assessedNot tested
  • None
Super Socializer

This row covers Super Socializer when Facebook login or Facebook comments are enabled. The page loads a Facebook script from connect.facebook.net. Outside scripts used in comment forms can contact providers on pages showing those forms, even when visitors do not sign in. The WordPress.org listing is closed. Consent timing is not tested here.

Outside login script on page loadconnect.facebook.netNot assessedNot tested
  • None
WordPress Social Login

We have not reviewed this plugin's social login data path yet.

Not reviewedDocumentation not reviewed yet.Not assessedNot tested
  • None

What this table does and does not prove

This table describes the named social login setups. It does not show what loads on your site. Where no outside login script is documented on page load, that applies only to the setup described. Clicking Continue with Google, Facebook, or X still sends the visitor to that provider. Other page requests are not covered. Outside scripts used in comment forms can contact providers on pages showing those forms, even when visitors do not sign in. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long login-provider logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.

Documentation snapshot: Oct 1, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-social-login-plugin-privacy