newWebber

LogiShield Security was built to be the only WordPress login security plugin you will ever need.
Easily improve your site’s security with this WordPress login security plugin by implementing essential defense features like Two-Factor Authentication (2FA), Limit Login Attempts, Temporary Logins, and Custom Login URLs.
<h3>Core Login Security Features of LogiShield Security</h3>
LogiShield Security is not just a basic plugin. It’s a multi-layered WordPress login security plugin with a custom login URL to give maximum protection. Below is a deep dive into the powerful features included in this secure WP login tool, explaining exactly what they do and why your website’s security depends on them.
<h4>1. Two-Factor Authentication (2FA)</h4>
As an ultimate WordPress 2FA plugin, LogiShield ensures that a stolen password is no longer enough to compromise your website. It adds an extra layer to your security. 2FA by LogiShield protects your admin login from brute force attacks, password leaks, automated password guessing, and data breaches.
2FA-enabled WordPress login requires both your password and a phone-generated OTP code. Use Google Authenticator, Authy, or Microsoft Authenticator to generate the 2FA code, then have a sound sleep at night!
LogiShield is a fully TOTP-compatible OTP login system. So, setting up the 2FA code is a piece of cake now.
See what our 2FA features include:
<ul>
<li>Passwordless login with passkey support</li>
<li>Free two-factor authentication (2FA) for all users</li>
<li>Remember trusted devices</li>
<li>Recover locked out of authentication accounts with allow next user login</li>
<li>Support multiple 2FA generators. </li>
<li>Enable 2FA with Authenticator app (TOTP) </li>
<li>Generate 2FA code over email (cooking)</li>
<li>Developer API integration for WhatsApp, OTP Token, etc. (cooking)</li>
<li>Password reset with 2FA (cooking)</li>
<li>Universal 2FA app support</li>
<li>Backup codes (16 digits) for recovery access</li>
<li>Wizard-driven setup</li>
<li>One-click WooCommerce integration</li>
</ul>
Passwords are fundamentally flawed. They can be guessed, phished, brute force attacked, or leaked in third-party data breaches. If an attacker acquires your admin password, a standard setup lets them walk right in. Here comes the WordPress 2FA plugin. If enabled, the attacker is stopped dead in their tracks because they cannot access your mobile device instantly to retrieve the 6-digit time-limited code.
LogiShield Security 2FA plugin provides individual user-based two-factor authentication, allowing your editors, authors, and admins to manage their own WordPress site security seamlessly. Thus ensuring brute force protection.
Documentation
<h4>2. Custom Login URL</h4>
A cornerstone feature of any effective WordPress login security plugin is the ability to mask your entry points, AKA the login URL. This feature lets you easily change WordPress login URL parameters. Instead of your login page living at
X “yoursite.com/wp-admin” or “yoursite.com/wp-login.php”,
Set a custom login URL WordPress slug, such as:
✓”yoursite.com/my-secret-portal”.
Hide your WP-Admin page access and rename the WordPress login page locations using this simple custom login URL feature:
<ul>
<li>Rename your WordPress login URL to anything</li>
<li>No core file changes or rewrite rules</li>
<li>Hides wp-admin and wp-login.php completely</li>
<li>Deactivate to restore original access instantly</li>
</ul>
Why Custom Login URL is a must-have plugin: LogiShield is a must-have plugin for security because automated hacking bots are very much active on the WordPress ecosystem. They scour the internet looking for websites and automatically append <code>/wp-admin</code> to the domain.
If the page loads, they begin their attack. Use the LogiShield WordPress login security plugin to change your admin URL, and those automated scripts simply hit a 404 Not Found error!
This acts as an immediate unauthorized access prevention measure and a highly effective bot protection strategy. It also works as brute force attacks prevention. The Custom Login URL feature ensures your front door is hidden from the public eye.
Documentation
<h4>3. Limit Login Attempts</h4>
By default, WordPress lets users try an unlimited number of login attempts. Trying to log in endlessly makes it easier for hackers to guess passwords. Limit Login Attempts by LogiShield blocks such brute force attacks by limiting login attempts.
LogiShield shines as a WordPress login security plugin by actively neutralizing active attacks through advanced request limiting.
This plugin lets you limit login attempts across your entire WordPress site. Configure a specific threshold (e.g., 3 failed attempts) to temporarily or permanently block suspicious IPs or invalid usernames. It creates a robust login firewall.
Core features of LogiShield Limit Login Attempts:
<ul>
<li>Stops brute force attacks by limiting login attempts</li>
<li>Works on standard logins, XMLRPC, WooCommerce, and custom pages</li>
<li>Improves security and site performance</li>
<li>Customized lockout timing</li>
<li>Set the remaining time for retry</li>
<li>Email Notifications of Lockout</li>
<li>Logs of denied attempts and lockouts</li>
<li>Logs of Successful Logins</li>
</ul>
Why you need the Limit Login Attempts feature: The limit login attempts feature is needed because in dictionary or brute-force attacks, hackers use automated software to rapidly guess thousands of password combinations per minute. Without a WordPress login security plugin, WordPress allows infinite login guesses.
This not only puts your credentials at risk but severely drains your server resources, potentially crashing your site.
By implementing WordPress brute force protection through the LogiShield security plugin, you lock out invalid login attempts instantly. It is a critical WP admin security step to prevent dictionary attacks from overwhelming your database.
Documentation
<h4>4. Temporary Login Access</h4>
Temporary login access feature redefines how you manage guest access and third-party collaborations.
This feature allows you to generate secure, self-expiring links that grant direct access to your dashboard for a limited time. This means you can create a WordPress guest login without requiring a password.
You can share temporary WordPress access with a specific user role, and set it to expire after a few hours, days, or after a single use.
Features we offer for Temporary Login URL:
<ul>
<li>Unlimited logins: Create as many temporary logins as you need</li>
<li>Passwordless login setup: Users log in with a simple link</li>
<li>Set a custom expiry: Choose when access automatically ends</li>
<li>Flexible time options: 1 day, 1 week, 1 month, or custom date</li>
<li>Redirect after login: Send users to a specific page</li>
<li>Track last login: See when each user last accessed your site using the temp link</li>
<li>Login count: View how many times a link was used</li>
<li>Detailed activity logs: Monitor exactly what each user did after login</li>
<li>Limit link usage: Control how many times a link can be accessed</li>
<li>Instant alerts: Get notified each time a temporary login is used</li>
</ul>
Why you need the Temp login link feature: Site owners frequently need to grant temporary admin access to WordPress credentials to freelance developers, support technicians, or guest writers. The traditional method involves creating an admin account and a password, which is a massive security risk. People often forget to delete these accounts, leaving ghost admin profiles vulnerable to attack.
This WordPress login security plugin eliminates that risk entirely, along with any possibility of brute force attacks. Because no password is created, no password can be stolen. Once the time limit expires, this WordPress login security plugin automatically destroys the access link, maintaining pristine login page protection.
Documentation
<h3>Why You Need a Dedicated WordPress Login Security Plugin</h3>
Every single day, thousands of websites fall victim to brute-force attacks and credential stuffing. The default WordPress configuration is user-friendly, but it leaves your front door wide open. When you install our LogiShield WordPress login security plugin, you instantly close those vulnerabilities.
Many site owners assume their hosting provider handles security, but server-level security cannot protect your admin dashboard from compromised passwords. This is why a dedicated WordPress login security plugin is strictly necessary.
By using a WordPress login security plugin, you can control your authentication flow, ensuring only authorized users can access your backend. This also ensures brute force attack prevention.
We believe that security should have the least possible impact on website performance, user experience, and maintainability. Therefore, this WordPress login security plugin is:
<ul>
<li>Lightweight: Every feature in this WordPress login security plugin is developed with a modular approach. Disabled features won’t load any redundant code, keeping your site fast.</li>
<li>Easy to use: This WordPress login security plugin offers a 1-minute configuration and a short, seamless onboarding process. You don’t need to be a cybersecurity expert to use this WordPress login security plugin effectively.</li>
</ul>
Hence, whether you are running a small personal blog, a bustling e-commerce store, or a massive corporate portal, ensuring a robust firewall and WP login security is no longer optional; it’s a necessity.
<h3>Privacy Policy</h3>
At newWebber, we believe that a WordPress login security plugin should protect your data, not harvest it. We are strictly committed to user privacy and full GDPR, CCPA, and CPRA compliance.
LogiShield Security does not collect, harvest, transmit, or store personal data beyond what is strictly and functionally required for authentication security on your local server.
When you use this WordPress login security plugin, all security logs (such as the IP addresses recorded to limit login attempts) are stored locally on your own WordPress database. We do not have access to your site’s data.
Furthermore, this WordPress login security plugin does not track user behavior, set tracking cookies, or send telemetry or analytics data back to our servers or any third-party marketing agencies.
The IP blocklists and allowlists are managed locally by your server. You retain absolute data sovereignty while utilizing this WordPress login security plugin.
If a user requests the deletion of their personal data from your WordPress site, standard WordPress data erasure tools will seamlessly purge any localized security logs associated with that user generated by this WordPress login security plugin.
<h3>External Services</h3>
To function as a top-tier WordPress login security plugin, LogiShield Security relies on your local server architecture for almost all operations. There is only one specific instance in which an external service is used to enhance the user experience during setup.
This WordPress login security plugin uses the external QR Server API strictly to generate the visual QR codes during the two-factor authentication WordPress setup process.
<ul>
<li>Service: QR Server API</li>
<li>Purpose: To instantly generate readable QR codes for your mobile authenticator app during the TOTP setup.</li>
<li>Data sent: Only the cryptographic TOTP setup URL is transmitted to generate the image. Absolutely no personally identifiable information (PII), usernames, passwords, or site data is sent.</li>
<li>When: This API is only triggered momentarily during the specific moment a user configures 2FA in their user profile. It does not run in the background.</li>
<li>Terms of Service: https://qr-server.com/terms/</li>
<li>Privacy Policy: https://qr-server.com/privacy/</li>
</ul>

LogiShield Security – Login Security, 2FA, Limit Login, Brute Force Protection, Firewall

LogiSheild Security with 2FA, limit login, custom login URL, and temp login is your go-to login security plugin for WordPress.

wpformation

Twelve security modules. One lightweight plugin. Zero compromise.
Login Armor is a complete WordPress security stack built for agencies, freelancers and pros who deliver audit-ready sites. No premium tier, no bundled marketing dashboard, no telemetry. Every module runs locally, ships with safe defaults, and stays out of your way.
Stop juggling Wordfence’s bloat, Solid Security’s upsells, and Limit Login Attempts’ gaps — Login Armor delivers twelve independent modules in about one megabyte.
<h4>New in 2.4.0</h4>
<ul>
<li>Request Firewall — an optional, 8G-inspired PHP filter that blocks malicious requests (SQL injection, code execution, traversal, XSS, disallowed HTTP methods) before WordPress finishes loading, on Apache, Nginx and LiteSpeed alike. Off by default, it starts in monitor mode and never filters logged-in administrators; every block is logged, aggregated to one incident per IP per hour.</li>
<li>Guided onboarding — a first-run wizard offers a one-click “safe baseline” that turns on the no-risk essentials, so a beginner is protected in seconds. The same “Apply safe baseline” button stays available any time.</li>
</ul>
<h4>Why Login Armor</h4>
<ul>
<li>No upsells, ever. No “premium” tier, no greyed-out “Pro” buttons. Every feature is GPL.</li>
<li>No external services to sign up for. No API keys, no remote dashboards, no telemetry. The only outbound calls are opt-in: Have I Been Pwned (breach/password checks), Slack/Discord/webhook (notifications), the keyless ipwho.is API (geolocation), and your own WordPress 7 AI connector.</li>
<li>Built to be invisible. Sub-megabyte ZIP, lazy-loaded modules, indexed queries — under 2 ms on a normal login flow.</li>
<li>Multisite-aware, PHP 8.1-native, production-grade defaults. Network-activate a fleet, configure per-site, manage from a complete WP-CLI suite; zero-config gets you 80 percent of the protection.</li>
</ul>
<h4>Twelve independent modules</h4>
<ol>
<li>Hide Login — Replace wp-login.php with a custom slug; the old URL returns a 404, and a branded pre-activation modal lets you pick or generate the slug and emails it to you so you can’t lock yourself out. Compatible with multisite, reverse proxies and password-recovery flows.</li>
<li>Brute Force Protection — Cascading lockouts escalating to a 24-hour ban, with subnet blocking and trusted X-Forwarded-For; lostpassword, register, XML-RPC and the REST users endpoint are all gated when an IP is locked, and every lockout surfaces as an incident.</li>
<li>Hardening — Fifteen one-click toggles across surface reduction, credential hardening, request filtering and account monitoring: disable XML-RPC/pingbacks, the file editor, version exposure, application passwords and author enumeration; block reserved usernames (Unicode-confusable detection); add a login honeypot; get alerted on new administrators.</li>
<li>Two-Factor Authentication — TOTP, one-time codes by email and printable backup codes, with trusted devices for thirty days, per-role enforcement, a configurable grace period and an email recovery flow when the authenticator is lost.</li>
<li>Detection and Incidents — A real-time engine groups raw events into six attack patterns, each with a drill-down (timeline, source IPs, target users, severity, UA fingerprint) and one-click actions (reset password, block subnet, mark resolved).</li>
<li>Activity Log — A compliance-ready, tamper-evident (hash-chained) audit trail of admin actions across seven logger domains, with filtering, CSV export, configurable retention and optional signed webhook forwarding to a SIEM.</li>
<li>Login Page Security Headers — Content-Security-Policy, X-Frame-Options, Permissions-Policy, Referrer-Policy and X-Content-Type-Options on wp-login.php and the lockout page, in two presets with an optional CSP report-uri; baseline headers can optionally extend site-wide.</li>
<li>Breach Check — Detect logins using a breached password via privacy-preserving k-anonymity against Have I Been Pwned (only a 5-character SHA-1 prefix leaves the server); optional XposedOrNot email lookup, fail-soft so an outage never blocks login.</li>
<li>Password Policy — Enforce strong, unique passwords at registration, profile update and reset: minimum length and character classes, forbid the username inside the password, optionally reject breached passwords, with optional non-locking expiration nudges.</li>
<li>Session Management — Idle-timeout logout measured on real page loads, a maximum session lifetime regardless of “remember me”, an optional single-active-device restriction, and a one-click “sign out all other devices”.</li>
<li>IP Geolocation — Show the attacker’s country on the Incidents and Events tabs; lazy, cached thirty days, capped per page load, private ranges never sent. Keyless ipwho.is by default, swappable for an offline database via a filter.</li>
<li>Request Firewall — An optional, 8G-inspired PHP filter that blocks malicious query strings, paths, HTTP methods and (opt-in) user-agents/referrers before WordPress loads, on Apache/Nginx/LiteSpeed alike; off by default, starts in monitor mode, never filters admins, skips REST/cron/WP-CLI, with an IP/path allowlist (CIDR). Not scored.</li>
</ol>
<h4>AI Security Briefing (optional)</h4>
Built on the WordPress 7 native AI Client, one click turns your last thirty days of activity into a plain-language verdict, an IP picture and a short list of prioritised actions; “Explain with AI” does the same on a single incident. Minimised mode (anonymised signals) is the default and deep mode is an explicit opt-in. No API key is stored — it uses your own WordPress AI connector, so provider and cost stay yours. It always leads with a deterministic facts snapshot that works with or without AI.
<h4>Plus</h4>
<ul>
<li>Guided onboarding — a first-run wizard with a one-click safe baseline (Simple) or manual setup (Advanced); the “Apply safe baseline” button stays available, and upgrading sites never see the wizard.</li>
<li>Security score — a weighted 0-100 read of your posture with a one-click “next best action”; observability features (geolocation, notifications, the AI assistant) are deliberately not scored.</li>
<li>Conflict detection — warns when another login-security plugin (Wordfence, Solid Security, Sucuri, All-In-One Security, SecuPress and more) or a cache plugin (with Hide Login on) could clash.</li>
<li>Notifications — email, Slack, Discord or webhook with SSRF-safe URL validation, severity threshold and rate limiting.</li>
<li>WP-CLI suite and a dashboard widget (14-day sparkline, six headline metrics).</li>
</ul>
GPL forever. PHP 8.1+. WordPress 6.8+. Zero dependencies.
Douze modules de sécurité. Une seule extension légère. Zéro compromis.
Login Armor est une stack complète de sécurité WordPress conçue pour les agences, les freelances et les pros qui livrent des sites prêts à passer un audit. Pas de version premium, pas de tableau de bord marketing intégré, pas de télémétrie. Chaque module tourne en local, embarque des réglages par défaut sécurisés, et reste discret.
Fini de jongler entre la lourdeur de Wordfence, les fenêtres d’upsell de Solid Security et les angles morts de Limit Login Attempts — Login Armor regroupe douze modules indépendants en environ un méga-octet.
<h4>Nouveau en 2.4.0</h4>
<ul>
<li>Pare-feu de requêtes : un filtre PHP optionnel, inspiré du pare-feu 8G, qui bloque les requêtes malveillantes (injection SQL, exécution de code, traversée de répertoires, XSS, méthodes HTTP non autorisées) avant même que WordPress ait fini de charger, aussi bien sur Apache que Nginx ou LiteSpeed. Désactivé par défaut, il démarre en mode surveillance et ne filtre jamais les administrateurs connectés ; chaque blocage est journalisé, agrégé en un incident par IP et par heure.</li>
<li>Assistant de configuration : à la première activation, un assistant propose une « base sûre » en un clic qui active les essentiels sans risque — un débutant est protégé en quelques secondes. Le même bouton « Appliquer la base sûre » reste disponible à tout moment.</li>
</ul>
<h4>Pourquoi Login Armor</h4>
<ul>
<li>Aucun upsell, jamais. Pas de niveau « premium », pas de boutons « Pro » grisés. Tout est en GPL.</li>
<li>Aucun service externe à activer. Pas de clé API, pas de tableau distant, pas de télémétrie. Les seuls appels sortants sont opt-in : Have I Been Pwned (fuites/mots de passe), Slack/Discord/webhook (notifications), l’API sans clé ipwho.is (géolocalisation) et votre propre connecteur IA WordPress 7.</li>
<li>Conçu pour être invisible. ZIP de moins d’un méga, modules chargés à la demande, requêtes indexées — sous 2 ms sur un flux de connexion normal.</li>
<li>Compatible multisite, natif PHP 8.1, réglages prêts pour la production. Activation réseau d’une flotte, configuration par site, pilotage via une suite WP-CLI complète ; sans configuration, vous avez déjà 80 % de la protection.</li>
</ul>
<h4>Douze modules indépendants</h4>
<ol>
<li>Masquer la connexion : remplace wp-login.php par une URL personnalisée (l’ancienne renvoie une 404) ; une modale de pré-activation choisit ou génère le slug et vous l’envoie par e-mail pour éviter tout verrouillage. Compatible multisite, reverse proxies et récupération de mot de passe.</li>
<li>Protection contre la force brute : verrouillages en cascade montant à un bannissement de 24 h, blocage de sous-réseaux et support X-Forwarded-For ; lostpassword, register, XML-RPC et l’endpoint REST users sont bloqués pour une IP verrouillée, et chaque verrouillage devient un incident.</li>
<li>Renforcement : quinze bascules en un clic (réduction de surface, identifiants, filtrage des requêtes, surveillance des comptes) — désactiver XML-RPC/pingbacks, l’éditeur de fichiers, l’exposition de version, les mots de passe applicatifs et l’énumération d’auteurs ; bloquer les identifiants réservés (homoglyphes Unicode) ; ajouter un pot de miel ; être alerté à la création d’un administrateur.</li>
<li>Authentification à deux facteurs : TOTP, codes à usage unique par e-mail et codes de secours imprimables, avec appareils de confiance 30 jours, application par rôle, période de grâce configurable et récupération par e-mail en cas de perte.</li>
<li>Détection et incidents : un moteur en temps réel regroupe les événements en six patterns d’attaque, chacun avec une vue détaillée (chronologie, IP sources, comptes cibles, sévérité, empreinte UA) et des actions en un clic.</li>
<li>Journal d’activité : piste d’audit conforme et inviolable (chaîne de hachage) des actions admin sur sept domaines, avec filtrage, export CSV, rétention configurable et transfert webhook signé optionnel vers un SIEM.</li>
<li>En-têtes de sécurité : CSP, X-Frame-Options, Permissions-Policy, Referrer-Policy et X-Content-Type-Options sur wp-login.php et la page de verrouillage, en deux préréglages avec CSP report-uri optionnel ; les en-têtes de base peuvent s’étendre à tout le site.</li>
<li>Détection de fuites : repère les connexions avec un mot de passe fuité via k-anonymat sur Have I Been Pwned (seul un préfixe SHA-1 de 5 caractères sort) ; vérification e-mail XposedOrNot optionnelle, fail-soft.</li>
<li>Politique de mot de passe : impose des mots de passe forts à l’inscription, au profil et à la réinitialisation (longueur, classes de caractères, interdiction de l’identifiant, rejet optionnel des mots de passe fuités), avec expiration optionnelle qui ne verrouille jamais personne dehors.</li>
<li>Gestion des sessions : déconnexion sur inactivité mesurée sur les vrais chargements, durée de vie maximale indépendante de « se souvenir de moi », limitation optionnelle à un seul appareil actif, et « déconnecter tous les autres appareils » en un clic.</li>
<li>Géolocalisation IP : affiche le pays des IP attaquantes dans Incidents et Événements ; recherches paresseuses, cache 30 jours, plafonnées par page, plages privées jamais envoyées. ipwho.is sans clé par défaut, base hors ligne possible via un filtre.</li>
<li>Pare-feu de requêtes : filtre PHP optionnel inspiré du 8G qui bloque chaînes de requête, chemins, méthodes HTTP et (en option) user-agents/referrers malveillants avant le chargement de WordPress, sur Apache/Nginx/LiteSpeed ; désactivé par défaut, démarre en mode surveillance, ne filtre jamais les admins, ignore REST/cron/WP-CLI, allowlist IP/chemins (CIDR). Non noté.</li>
</ol>
<h4>Briefing de sécurité IA (optionnel)</h4>
Bâti sur le client IA natif de WordPress 7, un clic transforme vos trente derniers jours d’activité en un verdict en langage clair, un panorama des IP et une courte liste d’actions prioritaires ; « Expliquer avec l’IA » fait de même sur un incident. Le mode minimisé (signaux anonymisés) est par défaut, le mode approfondi est un opt-in explicite. Aucune clé API stockée : il utilise votre propre connecteur IA WordPress, le coût et le fournisseur restent les vôtres. Il s’ouvre toujours sur un instantané de faits déterministes, utile avec ou sans IA.
<h4>En plus</h4>
<ul>
<li>Assistant de configuration : un assistant à la première activation propose une base sûre en un clic (Simple) ou une voie manuelle (Avancée) ; le bouton « Appliquer la base sûre » reste disponible, et les sites en mise à jour ne le voient jamais.</li>
<li>Score de sécurité : lecture pondérée 0-100 de votre posture avec une action prioritaire en un clic ; les fonctions d’observabilité (géolocalisation, notifications, assistant IA) ne sont pas notées.</li>
<li>Détection de conflits : alerte quand une autre extension de sécurité axée connexion (Wordfence, Solid Security, Sucuri, All-In-One Security, SecuPress et d’autres) ou un plugin de cache (avec Hide Login actif) peut entrer en conflit.</li>
<li>Notifications : e-mail, Slack, Discord ou webhook, avec validation d’URL anti-SSRF, seuil de sévérité et rate limiting.</li>
<li>Suite WP-CLI et widget Tableau de bord (sparkline 14 jours, six métriques clés).</li>
</ul>
<h4>Conçu par</h4>
Login Armor est conçu et maintenu par Fabrice Ducarme de <a href="https://wpformation.com/login-armor/" rel="nofollow ugc">WPFormation</a>, expert WordPress français obsédé par les sites propres, rapides et prêts pour l’audit. On l’utilise sur chaque site qu’on livre.
<ul>
<li><a href="https://wpformation.com/login-armor/" rel="nofollow ugc">Présentation et fonctionnement de Login Armor</a></li>
<li><a href="https://wpformation.com/securite-wordpress/" rel="nofollow ugc">Guides de sécurité WordPress</a> sur WPFormation</li>
<li><a href="https://wpformation.com/outils/veille-securite/" rel="nofollow ugc">Veille des vulnérabilités WordPress</a> : l’outil de veille sécurité de WPFormation</li>
</ul>
GPL pour toujours. PHP 8.1+. WordPress 6.8+. Zéro dépendance.
<h3>External Services</h3>
<h4>AI Security Briefing (optional)</h4>
The AI Security Briefing and the “Explain with AI” incident analysis are powered by the WordPress 7 native AI Client (<code>wp_ai_client_prompt()</code>). When the administrator clicks the analysis button, LoginArmor asks WordPress to send a prompt to the AI connector that the administrator configured in their own WordPress (for example OpenAI, Anthropic or Google, depending on the connector). LoginArmor itself stores no API key and contacts no endpoint directly: the request, the provider and the cost are owned by the site’s own AI connector.
Data sent: a text prompt describing the security situation. In minimised mode (the default), only anonymised, non-identifying signals are included (counts, categories, severities, role buckets) – no IP address and no username in clear. In deep mode (an explicit, off-by-default opt-in), the prompt additionally includes real IP addresses and event details so the analysis can name specific sources. No data is ever sent unless the administrator clicks the analysis button.
This feature is inactive unless WordPress 7 (or the AI Building Blocks feature plugin) is present with a configured, approved AI connector. The applicable terms and privacy policy are those of the AI provider the administrator chose for their connector; please refer to that provider’s documentation.
<h4>Webhook Notifications (optional)</h4>
When explicitly enabled and configured by the administrator in LoginArmor > Settings > Notifications, the plugin sends incident data to third-party services via webhooks.
Data sent: incident type, severity level, IP address, target username, event count, and site URL.
No data is sent unless the administrator actively enables and configures a notification channel.
<ul>
<li>Slack – <a href="https://slack.com/terms-of-service" rel="nofollow ugc">Terms of Service</a> | <a href="https://slack.com/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
<li>Discord – <a href="https://discord.com/terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://discord.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
<li>Custom Webhook URL – User-configured endpoint (administrator’s responsibility)</li>
</ul>
<h4>Gravatar (Automattic)</h4>
The Activity Log tab uses WordPress core’s <code>get_avatar()</code> function to display user avatars. WordPress may send a hashed email address to <a href="https://gravatar.com/" rel="nofollow ugc">Gravatar</a> servers to retrieve avatar images. This is controlled by Settings > Discussion > Avatars.
<ul>
<li>Gravatar – <a href="https://automattic.com/tos/" rel="nofollow ugc">Automattic Terms of Service</a> | <a href="https://automattic.com/privacy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Breach Check – Have I Been Pwned (optional)</h4>
When the administrator explicitly enables the Breach Check module (LoginArmor > Settings > Breach …

Login Armor

Twelve security modules + AI briefing: hide login, request firewall, brute force, 2FA, password policy, sessions, hardening, audit log. No upsells.

LogiShield Security – Login Security, 2FA, Limit Login, Brute Force Protection, Firewall vs Login Armor