Guard Dog
Guard Dog is a focused WordPress security plugin for the login door, authentication, sessions, and practical access workflows. With custom login URLs, two-factor authentication, passkeys, CAPTCHA providers, access control, and activity logging, Guard Dog helps site owners tighten the parts of WordPress that get bothered most. Key Features: Custom Login URLs – Hide your wp-admin and wp-login.php from attackers Two-Factor Authentication (2FA) – TOTP-based authentication with recovery codes Social Login (OAuth) – Sign in with Google, Microsoft, or Apple Passkeys – Use device-based biometric authentication like Face ID, Touch ID or Windows Hello Multiple CAPTCHA Providers – Support for Google reCAPTCHA v2/v3, hCaptcha, and Cloudflare Turnstile Login Attempt Limiting – Prevent brute-force attacks with intelligent lockout Access Control – IP-based whitelist/blacklist protection Activity Monitoring – Comprehensive logging of security events Temporary User Access – Create temporary WordPress users with time-limited, secure access Frontend Account Security – Shortcodes and blocks for login, passkeys, 2FA, and session controls Why Choose Guard Dog? Privacy-Focused – Multiple CAPTCHA options including privacy-first providers WordPress.org Compliant – Built following WordPress coding standards Site-Owned Controls – Protections run inside your WordPress site User-Friendly – Intuitive interface with helpful documentation Regular Updates – Actively maintained and updated Perfect For: Business websites requiring enhanced security WordPress sites handling sensitive data Multi-user sites with complex access requirements Anyone wanting practical login and account protection without a central SaaS dependency Frontend Shortcodes: [guard_dog_login_form] renders a public Guard Dog-managed login form [guard_dog_passkey_login] renders a standalone passkey sign-in button for custom login pages [guard_dog_two_factor] renders logged-in 2FA management [guard_dog_passkeys] renders logged-in passkey management [guard_dog_sessions] renders logged-in active-session management [guard_dog_account_security] renders the composite logged-in account security widget for 2FA, passkeys, and sessions [guard_dog_2fa] remains supported as the legacy alias for the account security widget Block-based themes can use the matching Guard Dog Login Form, Passkey Login, Two-Factor Auth, Passkeys, Sessions, and Account Security blocks. Additional Information Support: For support questions, please use the WordPress.org support forums. Privacy: Guard Dog respects user privacy and offers multiple privacy-focused options. Third-party services are only contacted when you enable features that need them, such as CAPTCHA, email delivery, social login, IP reputation, or geolocation. Security: Guard Dog follows WordPress security best practices. User input is sanitized and output is escaped throughout the plugin. Third-Party Services Guard Dog integrates with the following third-party services to provide CAPTCHA protection. These services are optional and only used when CAPTCHA features are enabled. Google reCAPTCHA (v2 and v3) What it is: Google’s CAPTCHA service that helps protect websites from spam and abuse. What it’s used for: – Verifying that login, registration, and password reset attempts are made by humans – Preventing automated bot attacks on your WordPress forms What data is sent and when: – User interaction data (mouse movements, time spent on page) when CAPTCHA is solved – IP address of the user – Site domain for verification – CAPTCHA response token Privacy and Terms: – Google reCAPTCHA Privacy Policy – Google reCAPTCHA Terms of Service – Google reCAPTCHA Data Usage Cloudflare Turnstile What it is: Cloudflare’s privacy-first CAPTCHA alternative that doesn’t require user interaction. What it’s used for: – Invisible verification of human users during login, registration, and password reset – Privacy-focused protection without tracking or cookies What data is sent and when: – Non-interactive browser signals when forms are submitted – IP address for verification – Site domain for validation Privacy and Terms: – Cloudflare Privacy Policy – Cloudflare Terms of Service – Turnstile Documentation hCaptcha What it is: A privacy-focused CAPTCHA service that doesn’t track users across websites. What it’s used for: – Human verification during login, registration, and password reset forms – Privacy-conscious alternative to Google reCAPTCHA What data is sent and when: – User interaction with CAPTCHA challenge – IP address for verification – Site domain for validation Privacy and Terms: – hCaptcha Privacy Policy – hCaptcha Terms of Service – hCaptcha Data Processing Google OAuth (Social Login) What it is: Google’s OAuth 2.0 service that allows users to sign in using their Google account. What it’s used for: – Authenticating WordPress users via their Google account – Retrieving basic profile information (name, email) to link or create accounts What data is sent and when: – User is redirected to Google’s authorization server when clicking “Sign in with Google” – An authorization code is exchanged for an access token on your server – Basic profile information (name, email, Google user ID) is retrieved from Google’s API – No ongoing data sharing – data is only retrieved during the login process Privacy and Terms: – Google OAuth Privacy Policy – Google OAuth Terms of Service – Google API Services User Data Policy Microsoft Azure AD (Social Login) What it is: Microsoft’s OAuth 2.0 service via Azure Active Directory that allows users to sign in using their Microsoft account. What it’s used for: – Authenticating WordPress users via their personal Microsoft account or organizational (work/school) account – Retrieving basic profile information (name, email) to link or create accounts What data is sent and when: – User is redirected to Microsoft’s authorization server when clicking “Sign in with Microsoft” – An authorization code is exchanged for an access token and ID token (JWT) on your server – Basic profile information (name, email, Azure object ID) is extracted from the ID token – No ongoing data sharing – data is only retrieved during the login process Privacy and Terms: – Microsoft Privacy Statement – Microsoft Services Agreement – Microsoft Identity Platform Documentation Apple Sign In (Social Login) What it is: Apple’s OAuth 2.0 / OpenID Connect service that allows users to sign in using their Apple ID. What it’s used for: – Authenticating WordPress users via their Apple ID – Retrieving basic profile information (name, email) to link or create accounts What data is sent and when: – User is redirected to Apple’s authorization server when clicking “Sign in with Apple” – An authorization code is exchanged for an access token and ID token (JWT) on your server – Basic profile information (email, user ID) is extracted from the ID token – User’s name is only provided on first authorization; subsequent logins return only the user ID – Apple may provide a private relay email address instead of the user’s real email – No ongoing data sharing – data is only retrieved during the login process Privacy and Terms: – Apple Privacy Policy – Sign in with Apple Guidelines – Apple Developer Program License Agreement TOTP (Time-based One-Time Password) Standard What it is: An open standard (RFC 6238) for generating time-based one-time passwords used in two-factor authentication. What it’s used for: – Generating secure, time-limited authentication codes for 2FA – Providing backup authentication when primary 2FA methods are unavailable – Enabling compatibility with popular authenticator apps (Google Authenticator, Authy, Microsoft Authenticator, etc.) What data is sent and when: – No external data transmission – TOTP codes are generated locally using the TOTP algorithm – Secret key generation – A unique secret key is generated locally when 2FA is enabled for a user – QR code generation – QR codes are generated locally for easy setup with authenticator apps – Code verification – Generated codes are verified locally against the stored secret key Privacy and Terms: – RFC 6238 – TOTP Standard – Google Authenticator Privacy Policy (if using Google Authenticator app) – Authy Privacy Policy (if using Authy app) – Microsoft Authenticator Privacy Policy (if using Microsoft Authenticator app) Data Handling Summary When CAPTCHA is disabled: No data is sent to any third-party services. When CAPTCHA is enabled: Only the specific provider you choose receives verification data. Data is not shared between providers or stored by Guard Dog beyond the verification process. When 2FA is disabled: No external data transmission occurs. When 2FA is enabled: – All TOTP operations (code generation, verification) happen locally on your server – No data is transmitted to external services for 2FA functionality – Authenticator apps only receive the initial setup QR code or secret key – Recovery codes are generated locally and stored securely When Social Login is disabled: No data is sent to any OAuth provider. When Social Login is enabled: – Data is only sent to the configured providers (Google, Microsoft, Apple) during the login process – Only basic profile information (name, email, user ID) is retrieved – Social account links are stored locally in your WordPress database – Users can unlink their social accounts from their profile at any time User control: Users can choose which CAPTCHA provider to use, or disable CAPTCHA entirely. 2FA can be enabled/disabled per user, and users can choose their preferred authenticator app. Social login can be enabled/disabled by administrators, and users can manage their linked social accounts. All security features are optional and configurable.
Top keywords
- data27×1.91%
- login27×1.91%
- google23×1.63%
- user20×1.42%
- privacy18×1.28%
- captcha16×1.13%
- guard16×1.13%
- dog15×1.06%
- guard dog15×1.06%
- microsoft14×0.99%
- wordpress14×0.99%
- id13×0.92%
Simpler Checkout
The Simpler Checkout button lets your customers complete their purchases in seconds. Customers using Simpler for the first time will fill in a simple form once. For all the next purchases, they can complete their orders with one click, regardless of device or browser, and without a password. Simpler checkout is designed based on conversion best practices, reducing friction and increasing sales. 1.4.11 Fix(compat): Apply custom order numbers to emails and Simpler 1.4.10 Feat(compat): Custom Order Numbers for WooCommerce 1.4.9 Feat: Accept regulatory_code (e.g. DNI) on order submission Feat: Billing address handling 1.4.8 Fix: persist voucher meta on order creation for v3.3 1.4.7 Fix: Set woocommerce taxes when creating order shipping line item manually 1.4.6 Fix(sequra): Save payment type meta on order creation; fix empty payment gateway ID fallback; sync shipment status 1.4.5 Compat: BOPO Bundle Builder Premium Compat: WooCommerce Order Attribution 10.x 1.4.4 Compat: BOPO Bundle Builder 1.4.3 Feat(compat): TranslatePress – Multilingual 1.4.2 Fix(compat): BOX NOW Delivery 3.2.1 1.4.1 Fix: Cart request URL 1.4.0 Breaking: Drop support for PHP versions <7.4 Fix: SLM phone field, collect package rates before calculating quotes Fix(submit): Add shipping item only if not exists Fix(hook): Pass shipping method on COD hook 1.3.5 Feat: use /v1/cart-requests to create carts for takeover 1.3.4 Fix: compatibility with woocommerce 10.4+ 1.3.3 Fix(takeover): use determine_locale with extra filter for language resolution 1.3.2 Feat: handle grouped products Fix: normalize option keys in product feed Fix: handle stock status in product feed Compat: Skroutz Lockers 1.3.1 Fix: normalize product feed and product details request responses 1.3.0 Feat: introduce product feed route 1.2.7 Fix(coupons): Check if coupon already exists in session cart before applying it 1.2.6 Fix(compat): Set order status to complete for digital vouchers from WooCommerce PDF Vouchers 1.2.5 Fix: Pass shipping as order item for WC 10.3.0 1.2.4 Fix: Should render button for WooCommerce PDF Vouchers 1.2.3 Feat: Default support for woo attribution to true Fix: Support extra keys for order attribution meta Compat: WooCommerce PDF Vouchers 1.2.2 Fix: Payment method title 1.2.1 Feat: Clean output buffers before writing api json responses 1.2.0 Feat: Check verification token before auto-login on order success 1.1.13 Compat: EU VAT Compliance Premium 1.1.12 Fix(compat): WC Pickup Store 1.1.11 Fix(multi-currency): Full support of multi-currency Feat(settings): Disable force login 1.1.10 Chore: strict time frame 1.1.9 Compat: WPML Multicurrency Compat: Pre-Orders for WooCommerce 1.1.8 Fix: Bank transfer email on order submit (default status: on-hold) Fix: Order notes 1.1.7 Compat: PW WooCommerce Gift Cards 1.1.6 Compat: Gift Wrapping for WooCommerce Feat: Link stub payment gateway settings screen to plugin settings for configuration Fix: WooCommerce order attribution hooks race condition Fix: Ignore shipping address when quote is for virtual cart Fix(COD): include restrictions 1.1.5 Fix/Compat: WC Smart COD / availability to set 0 fees 1.1.4 Fix/Compat: WC Smart COD / include tax 1.1.3 Feat: Bank transfer payment method Fix/Compat: WC Smart COD 1.1.2 Compat: WPC Product Bundles for WooCommerce Compat: WPC Frequently Bought Together for WooCommerce 1.1.1 Compat: Asana WooCommerce Dynamic Pricing and Discounts 1.1.0 Feat(hook): custom cod cost hook 1.0.9 Fix(takeover-checkout): prevent redirection if cart has no products Compat: BoxNow ‘Pay on the Go’ payment method as COD 1.0.8 Feat: takeover checkout (Replace native checkout with Simpler) 1.0.7 Compat: WC Smart COD 1.0.6 Fix: increase http timeout for integration status call Compat: Rightpress Dynamic Discounts 1.0.5 fix(payment): enable payment gateway and hide it from checkout 1.0.4 Compat: BOGO 1.0.3 Feat: handle bundle discounted products 1.0.2 Feat: simplerwc_customer_properties filter Compat: WC Pickup Store 1.0.1 Hotfix: default to production environment when no explicit setting 1.0.0 Feat: new simplerwc_order_created action on successful submission Feat: run woocommerce_checkout_order_created action on successful submission Feat: remove sandbox option as Simpler production environment now supports Test Stores 0.7.11 Compat: WordPress 6.5 0.7.10 Feat: Experimental support for WooCommerce Order Attribution Tracking 0.7.9 Compat: Pay for Payment for WooCommerce 0.7.8 Fix: omit coupon from button payload if empty 0.7.7 Feat: introduce simplerwc_should_render_product_button and simplerwc_should_render_cart_button filters for granular control of rendering logic Feat: introduce simplerwc_button_get_product_attibutes and simplerwc_get_cart_item_data filters for managing cart item attributes Compat: iThemeland Free Gifts 0.7.6 Fix: COD filters invocation 0.7.5 Feat: Parse company invoicing details in order request Fix: do not set payment method title when payment method is not simpler 0.7.4 Feat: Support COD payment method Compat: Smart COD plugin support 0.7.3 Compat: BoxNow v2 plugin support 0.7.2 Feat: Allow switching to sandbox environment from single distributable 0.7.1 Fix: Correct auth cookie argument in login before order confirmation redirect 0.7.0 Feat: Login user before redirecting to order confirmation 0.6.2 Feat: Add Minicart placement setting Fix: remove excessive free gifts returned in products response when FGF plugin is active 0.6.1 Compat: BoxNow support 0.6.0 Compat: WooCommerce Local Pickup Plus support Fix: Apply coupons before collecting shipping rates to account for free shipping coupons Fix: Set chosen shipping method on retrieved package keys instead of defaulting to 0 0.5.8 Fix: WooCommerce Product Bundles correct quantity payload when bundle is in cart 0.5.7 Fix: Free Gifts for Woocommerce support for cart checkout with gift 0.5.6 Free Gifts for Woocommerce support 0.5.5 Support Product Bundles created with WooCommerce Product Bundles plugin 0.5.4 Calculate discounted tax when simpler discount present Fix : check data validity when invoking simplerwc_should_render_button function 0.5.3 Optionally include customer email during quotation to handle coupon usage limits Fix : Refactor submission flow to ensure shipping tax calculation works as intended 0.5.2 Fix: Cost reporting in order confirmation email Remove deprecated order submission functionality Remove deprecated Offers tab from Settings 0.5.1 Hotfix: Include customer name & phone in order shipping address 0.5.0 Support custom fees during cart fees calculation Breakdown products cost during quotation Excluded specific user roles from viewing the button Fix: Price rounding Fix: Include tax in coupons 0.4.0 Breaking : Drop support for legacy SDK Add configuration option to hide the product page button if cart contains at least one item Include amount in refund request to account for partial refunds Introduce programmatic filter to modify shipping rates during quotation Fix : Include tax amount in shipping costs during quotation Fix : Respect prices when input excluding tax 0.3.3 Introduce products route to speed up product details retrieval Introduce /v2/order route to include cart calculation hooks in order submission flow 0.3.2 Fix critical issue preventing the plugin from running on PHP 7.2 Render translated asset texts based on store locale 0.3.1 Add product attributes to simpler integration for variable products. 0.3.0 Extract browser assets to external file, hosted at https://cdn.simpler.so. This behavior can be toggled off by the “use legacy SDK” checkbox in the plugin settings, but is not encouraged. Use a Web Component to render the simpler-checkout button Add separate option to control if checkout button gets rendered in the cart view Accepted cards notice is now controlled by a single option for all positions to enhance consistency