Skip to main content

User FAQ

What user data does TrustedLogin collect?​

The only user data TrustedLogin stores is the website URL. The website URL is stored unencrypted in our database.

Other than that, we do not collect any user data.

When a support user logs into the website, we store the user's WordPress ID on the Vendor's website.

What data is in the troubleshooting report shared with Vendors?​

If you check the "Include the Site Health information" checkbox, the data generated by the WordPress Site Health tool is shared with the Vendor. Learn more about the shared information.

By default, Site Health information does not include any personally-identifiable information. However, if you have installed a plugin that adds personally-identifiable information to the Site Health information, that information will be shared with the Vendor.

Some things to note about the troubleshooting report:

  • The data is never received by TrustedLogin
  • The Vendor defines where this information is sent
  • TrustedLogin does not control the website that receives the debugging data

What happens if I don't want to use TrustedLogin on my website?​

To disable TrustedLogin globally, define a TRUSTEDLOGIN_DISABLE constant in the site's wp-config.php file. That will prevent all code that uses TrustedLogin from loading TrustedLogin.

To prevent a single TrustedLogin installation, you will need to know the namespace. Once you have the namespace, define a TRUSTEDLOGIN_DISABLE_{NAMESPACE} constant in the site's wp-config.php file. The namespace must be in all caps.

Is TrustedLogin WordPress.org compliant?​

Yes. TrustedLogin requires user action to provide logins. This is in compliance with WordPress.org.

When distributing TrustedLogin on WordPress.org, all files (logo, CSS, and JS files) must be local (using plugin_dir_url() or similar) to comply with WordPress.org rules.