Docs / WPMU DEV Privacy & Security / Cookie Declaration

4. Cookie Declaration

Written by Patrick Cohen & Mohamed Khafaja | Last updated: October 2, 2025

This document outlines the cookies that may be used by our website, as well as cookies that may be deployed by plugins you may have active on your site(s).

4.2 WPMU DEV Plugins

Copy chapter anchor to clipboard

You may be required to alert your site’s visitors and users to the use of the cookies in your Privacy Policy or Cookie area of your website. The following WPMU DEV plugins may add Cookies to your site(s) when active.

WPMU DEV Dashboard

The following cookies are used by the WPMU DEV Dashboard plugin when the Analytics feature is active. See this section in our WPMU DEV Dashboard document for details on how to allow your users to reject these cookies.
_pk_ses and _pk_id

Defender

The following cookies are used by the Defender plugin when specified features are active.

display_strong_password_warning
Used to display a warning message on the Reset Password page.

display_reset_password_warning
Used for the Password Reset feature.

wpdef_last_activity
Used for the Session Protection feature.

wpdef_lockout_{IP}
Used to create a Lockout cookie to avoid caching on the locked page, where {IP} is the IP address in this format (e.g., 127_0_0_1).

display_pwned_password_warning
Used for the Pwned Passwords feature.

wordpress_logged_in_{COOKIEHASH}
Default WordPress cookie used to store the session key for two-factor authentication, where {COOKIEHASH} is a default WP constant.

wp-resetpass-{COOKIEHASH}
Default WordPress cookie used to reset the user password when either of the above features are enabled, where {COOKIEHASH} is a default WP constant.

wpmudev_is_staff
This cookie allows WPMU DEV staff to bypass Defender firewall rules when they access your site via support access, and it logs the staff visit in firewall logs.

Hustle

The following cookies are used by the Hustle plugin when specified features are active.

provider_migration_notice_{providerName}
Used for displaying provider data migration notice.

hustle_module_show_count-{moduleType}-{moduleId}
Used for tracking the number of module instances.

inc_optin_popup_long_hidden-{moduleId}
Used for backward compatibility with older plugin versions. Responsible for hiding “popup” module.

inc_optin_slide_in_long_hidden-{moduleId}
Used for backward compatibility with older plugin versions. Responsible for hiding “slide in” module.

inc_optin_embedded_long_hidden-{moduleId}
Used for backward compatibility with older plugin versions. Responsible for hiding “embedded” module.

inc_optin_never_see_again-{moduleType}-{moduleId}
Flag for hiding module after clicking “Never see this again” link.

hustle-hide-module
Used for backward compatibility with older plugin versions. Hide module after close.

hustle-hide-module-{moduleId}_success
Flag for hiding module after subscribing.

hustle-hide-module-{moduleId}_cta_success
Flag for hiding module after CTA conversion.

hustle-hide-module-{moduleId}cta2_success
Flag for hiding module after CTA2 conversion.

hustle-hide-module{pageId}
Flag for hiding module on page.

Beehive

While Beehive itself does not add any cookies to your site, Google Analytics does once that is enabled in the plugin.

For a complete list of cookies added by Google Analytics, see their help document here.

If you still have questions or need assistance after reading this document, please don’t hesitate to contact our support superheroes using the available options under the Support tab in your Hub or via the Support tab in your WPMU DEV Dashboard.

Link to getting support