Documentation
Install, activate and configure HiveProtect: a screen-by-screen guide, in the order you will meet them, with the exact labels used in the plugin.
Getting started
HiveProtect installs like any other WordPress plugin, in a few minutes. The 15-day trial starts on activation, with every feature included and no credit card.
| System requirements | Requirement |
|---|---|
| WordPress | 5.3 or later |
| PHP | 7.4 or later |
| WooCommerce | Optional |
| Web server | Apache or LiteSpeed for the .htaccess protections and the HTTP headers; any other server for everything else |
| Outgoing connections | HTTPS to hiveprotect.ai, required for the license, updates and HiveShield |
| Other requirements | The WordPress scheduler (WP-Cron) in working order and the common PHP extensions (openssl, mbstring, curl, zip) |
Download the plugin ZIP file from your customer area.
In WordPress, go to Plugins > Add New.
Click Upload Plugin.
Select the ZIP file you downloaded.
Click Install Now, then Activate.
On activation, HiveProtect opens the HiveProtect.ai > License screen and starts your 15-day trial. If you have already purchased a license, paste your key into the “Enter your license key:” field, then click Validate.
The plugin screens
Everything is managed from the HiveProtect.ai menu in the WordPress admin.
| Screen | What it does |
|---|---|
| Dashboard | The anti-spam counters, the status of a few settings and the latest message analyses. |
| Settings | The anti-spam filters, the AI provider, geographic filtering, alert emails and the interface language. |
| Detailed logs | The log of form and comment submissions, with the reason for each decision. |
| False positives | The rules that allow an email address or a text excerpt, so that they skip the AI analysis. |
| Blocked IPs | List, add and remove blocked or allowed addresses. |
| Forms Creator | Create forms whose submissions go straight to Prospect Hub. |
| Secure Login | Two-factor authentication and the custom login address for administrators. |
| Login Logs | The log of logins and the lockout after repeated failures. |
| WAF Security | The web application firewall, the HiveShield collective defense and the server protections: ten screens, detailed below. |
| Analytics | Statistics on visits, orders and bots, stored in your own database: three screens, detailed below. |
| License | Enter your key, start the trial, see the license status, install an update. |
Forms and comments
HiveProtect protects your forms and comments against spam with several complementary filters, without your visitors having to do anything. The traps and the behavioral detection are free; AI analysis and geographic filtering require a license. These protections are configured in HiveProtect.ai > Settings, and their results are read in the logs.
Supported form plugins
HiveProtect automatically recognizes the form plugins installed on your site and protects all of their forms against spam: there is nothing to connect and nothing to configure form by form. Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Formidable Forms, Fluent Forms, Forminator, Elementor Forms (with Elementor Pro), Beaver Builder and WordPress comments are supported; WPBakery and Oxygen are recognized as well.
- A plugin that is not on this list has no integration. The web application firewall, with a license, nevertheless examines form submissions from any source.
- Your own submissions are checked like those of visitors: a logged-in administrator is not exempt. To test without risking a block, add your address to the whitelist on the Blocked IPs screen.
- Attached files are not analyzed: only the values entered are.
Settings
The Settings screen brings together the anti-spam settings. Each message goes through several filters; depending on which one stops it, the log shows the “Detection reason”:
- Honeypot System: invisible trap fields that only bots fill in.
- Behavioral Detection: the way the form is filled in, measured by a script that runs in the visitor's browser, with the form plugins that support it. The “Block if JavaScript is disabled” option adds a requirement.
- Geographic filtering (license): refuses form submissions based on the visitor's country, as a “Blacklist” or a “Whitelist”, by country or by continent. It never affects how your pages are displayed.
- Artificial intelligence analysis (license): you use your own Claude (Anthropic) or OpenAI key. The content of the message fields is sent directly from your site to the provider you chose, using your key. Test the API checks the saved key; the “Site context” field describes your business to help the analysis; the “Detection Threshold” sets its strictness on WordPress comments, Formidable Forms, Ninja Forms, Fluent Forms, Elementor Forms, WPForms and Forminator.
- Comment protection: also checks WordPress comments, with the traps, geographic filtering and AI analysis, but without behavioral detection.
- Mass attack protection: an address that is already blocked and keeps trying is refused across the whole site (“403 mode”); you set the alert threshold and the response mode (HTTP 403 error, custom message or redirect). If the server already refuses the address, its own 403 page is displayed.
The “Block spam submissions” setting lets you observe without refusing with Contact Form 7 and Gravity Forms: once unchecked, messages are recorded but no longer blocked. With WPForms, Ninja Forms, Elementor Forms, Fluent Forms, Formidable Forms, Forminator and comments, detected spam is always refused.
The interface Language is chosen from nine buttons and applies immediately: “Auto” follows your site's language, and falls back to English when it is not supported. The “Keep data when uninstalling” checkbox decides what happens to the data when you delete the plugin (see the License, updates and uninstallation section).
If the AI analysis does not respond, the message is not analyzed by the AI, the other filters stay active, and an “Anti-spam protection out of service” banner warns you in the admin.
Alert emails and diagnostics
The Notification email receives the anti-spam alerts: the automatic blocking of an address, the reminder when a blocked address keeps trying and a weekly report. These three messages cannot be turned off from the screen, and the field must not be left empty.
Test the email first runs a diagnostic of your domain's DNS records (SPF, DKIM, DMARC, MX and reverse DNS): it displays a score out of 100 and a few tips, then sends a test message to the notification address. That message only proves that WordPress was able to send an email; the diagnostic does not measure actual inbox delivery. The “Email security” box at the bottom of the screen keeps the latest report; Refresh reads it again without repeating the DNS queries.
The diagnostic only looks for a DKIM key under common names: a key published under an unusual name is not detected.
Detailed logs
The log of form and comment submissions. Filter on “Spam” to see the refused messages. Each line shows the “Detection reason” (geographic filtering, honeypot system, IP block, behavioral detection or artificial intelligence) and the “Complete form content:” as submitted. The search covers the name, email, phone number, IP address and message, on the displayed page.
Not spam appears on spam entries, except those refused by a trap, by geographic filtering or because the address was already blocked. It takes two clicks: a panel offers to allow the email address and/or the first 100 characters of the message, and the entry changes to “Legitimate”. Matching future submissions no longer go through the AI analysis; the address itself is not unblocked (see Blocked IPs).
Show sets the number of entries per page (from 10 to 200), and an entry's trash button deletes it. This screen has no export.
Clear all logs empties the anti-spam log and resets the counters on the dashboard and in the admin bar.
False positives
This screen lists what you have allowed. Click Add a rule and choose the type: an “Email” address or a “Content pattern” (a text excerpt), with a “Value” and an optional reason. The “Allowed emails” and “Content patterns” tabs let you Delete a rule. The tiles at the top count the corrections made with Not spam and show how they have evolved over six months.
Blocked IPs
The Blocked IPs screen manages the addresses refused for forms and comments: those HiveProtect blocks by itself after repeated spam, those you block by hand (a single address, or an entire range in CIDR notation, IPv4 and IPv6) and those that mass attack protection refuses across the whole site (“403 mode”). Blocking an address or a range closes its forms and comments, not the site; only 403 mode closes the site to an address.
- Block manually accepts an address or a range (
10.0.0.0/8); the screen warns you if it is already blocked, whitelisted or included in a range. - IPs under monitoring: addresses detected for spam but not yet blocked, with the Block now, 403 mode and Add (to the whitelist) buttons, per address or for all at once.
- Unblock form submissions and Lift 403 mode only lift their own type of block. Unblock all, at the head of the column, unblocks every address on the site, including those banned by the firewall or by their DNS name.
- Whitelist: enter an IPv4 address or range, then click Add; if it is blocked, the screen offers to unblock it before adding it. Remove and Remove all lift it. A whitelisted address escapes the anti-spam, the firewall and the login lockout, but not a HiveShield refusal.
- Further down: the Blocked CIDR ranges, the Blocking system impact (the number of submissions blocked without an AI call and the estimated credit savings) and the Manual action history (who, when, from which address).
Forms Creator
Forms Creator builds forms whose every submission goes from the visitor's browser straight to Prospect Hub, the CRM associated with HiveProtect: each submission becomes a contact in your CRM, protected by Prospect Hub's anti-spam chain. The screen is free. If you already use a form plugin (Contact Form 7, WPForms, Gravity Forms…), keep it: HiveProtect protects it separately.
- Before you start: you need a Prospect Hub account (free), an API key whose public key (
pk_…) you paste in, and your site's domain name in the “Allowed domains” of that key. Test connection checks the domain, not the key. - Create a form: choose one of the 12 templates (Contact, Quote request, Callback request, Plumber, Electrician, Building tradesperson, Real estate, Restaurant, Auto repair shop, Health and wellness, Training, After-sales service), then drag fields from the palette, with the mouse or your finger; a click adds the field at the bottom. A form holds up to 29 fields, three per row.
- Field settings: label, help text, type, technical name, “Required” checkbox and width (full width, half, one third or two thirds).
- Texts and after submission: the button text, the success message or a redirect to a page of your site, and the text of the GDPR consent checkbox. This checkbox is always added and required: only its text can be changed.
- Where to display it: with the shortcode
[hiveprotect_form id="form_…"], with the “HiveProtect Form” block, with an Elementor widget or a WPBakery element, or automatically before or after the content of the pages you choose. For other page builders, use the shortcode or the block. - The list shows each form's template, number of fields, key, shortcode and the pages where it is displayed. Preview, Duplicate and Delete (with confirmation) are available; deleting a form leaves its shortcode in the pages.
- On every change, HiveProtect clears the cache of the affected pages for the main caching plugins.
Securing the login
Two-factor authentication protects administrator accounts. It is one of the licensed features; the login log is free.
Secure Login (two-factor authentication)
The Secure Login screen turns on two-factor authentication for administrator accounts, with a compatible app: Google Authenticator, Microsoft Authenticator or Authy. WooCommerce customers, editors and other roles log in normally, without two-factor authentication. Each administrator sets up their own two-factor authentication: the screen does not let you manage another account's.
- The large 2FA Authentication switch turns the module on for the site. Each time it is turned on or off, HiveProtect sends an information email to the admin address.
- Configure 2FA now: choose a random key (recommended) or your own key, reusable across several sites; scan the QR code or enter the key by hand; Download codes (TXT) saves the 10 backup codes created at that moment, to be kept safe; enter a 6-digit code, then click Validate Configuration and Activate 2FA.
- Once 2FA is active, the screen shows the remaining backup codes and the Regenerate Backup Codes buttons (the old ones stop working), Send Recovery Link and Disable 2FA, which asks for the current code from the app.
- Advanced Options: the custom login address (“Custom login URL:”), the validity period of the recovery link (5 minutes, 15 minutes or 1 hour) and the “Verify IP address during recovery” checkbox, which ties the link to the address that requested it.
- Authentication Order: “Classic 2FA” (username and password, then code) or “Without 2FA (secure URL only)”, where the custom login address replaces the code.
- If Wordfence Login Security has already set up two-factor authentication for an account, a “2FA conflict” banner tells you; HiveProtect never changes another plugin's configuration.
Choose the custom login address carefully: it is recognized as soon as a site address contains it, and a word already used by one of your pages, such as “contact”, would hijack it.
Login Logs
The log of logins to your site: every login, logout and failure, with the address, account and time. It is always on, for all accounts. Filters by event and by period, search and the choice of the number of rows help you find your way; CSV export exports one event type over a period, and Clear empties the log.
- Lockout after repeated failures: a switch, then Save. A locked address has its logins refused, even with the right password, until the refusal expires on its own. A second, optional lockout targets unknown usernames. The “Currently refused:” table lists the addresses concerned, which you release with a click on Unblock or Unblock all. The lockout applies to the login page and to WooCommerce's customer form.
- Bans: optionally, the lockout can also ban the address (403 response) with automatic lifting; the “Banned (403) by the lockout:” and “Recent bans and lifts:” tables keep a record, and Ban adds an address by hand.
- Login Email Notifications: check the events to report (administrator login, logout, user login, grouped attempts) and enter the “Recipient email:”; the setting is only saved when you click Save.
The username entered during a failure is kept as is in the log: a password typed by mistake in the “username” field stays visible there.
The web application firewall
The firewall examines every request and refuses or bans attacks before they reach your site. It is one of the licensed features, except the Abuse & Reports screen, which is free. It is configured in WAF Security, whose tab bar gives access to all the screens that follow.
Status banner and switch
At the top of each WAF Security screen, the banner reads “WAF protection active” or “WAF protection disabled”. The OFF / ON switch turns protection off or on immediately, without confirmation. The firewall requires a valid license.
The Clear logs button, visible when protection is active, empties the firewall log after confirmation. Clearing is permanent and does not unblock any address.
The switch affects neither the addresses already written to the .htaccess file, nor HiveShield.
Dashboard
The Dashboard brings together seven number cards (total threats, blocked addresses, critical, high and medium threats, addresses under monitoring, allowed DNS names), the table of blocked addresses and the log of detected threats.
- IPs blocked by the WAF: address and DNS name, location, reason, score and block date. Unblock and Unblock all ask for confirmation. Unblocking does not whitelist the address: it can be banned again at its next threat.
- Security logs: one line per detection, with the level (critical, high, medium or low depending on the score), the description, the requested address, the detected pattern, the User-Agent, the referrer and the GET and POST parameters.
- Search and exports: search only filters the displayed page; the Show selector offers 25 to 1,000 rows; Export Page, Export All and Custom Export produce a CSV file that opens in Excel.
The log and the table of blocked addresses refresh on their own while the page is open; the number cards are recalculated on reload.
Rules & configuration
- Blocking thresholds: three sliders (critical, high, medium) set the number of attempts an address can make before being banned.
- Detection rules: more than 200 rules grouped into about thirty families. Each family has a switch and most rules have their own checkbox; a rule that is turned off is off for the whole site.
- IP whitelist: enter an IPv4 address or CIDR range (
192.168.1.0/24), then click Add; Remove deletes the entry. A whitelisted address escapes the firewall analysis, the anti-spam and the login lockout, but not a HiveShield refusal. - Advanced security options: block empty reverse DNS names, block empty User-Agent headers, verify bot authenticity, block Tor exit nodes, hide the oEmbed and REST endpoints, enable Performance Mode.
Performance Mode (early firewall)
The Performance Mode (MU-Plugin) switch installs a file in wp-content/mu-plugins/. It refuses the most obvious threats very early in the request, before the plugins and the theme: automated tools, sensitive files, probes, request bursts and missing plugins. Each of these families has its own switch.
- The
mu-pluginsfolder must be writable, otherwise the switch is grayed out. - The anti-burst protection and the counting of missing plugins require a persistent object cache (Redis or Memcached).
- A plugin update does not rewrite this file: if the screen reports that it dates from a previous version, click Regenerate the early firewall.
- Deactivating the plugin deletes this file: turn the switch back on after reactivating.
Banned DNS Reverse and Allowed DNS Reverse
These two screens manage lists of patterns compared with visitors' host names (reverse DNS), with * wildcards.
- Banned DNS Reverse: an address whose name matches a pattern is refused, then banned. Recognized search engine bots are never affected. Enter a pattern and a reason, then click Add. The ready-made examples only fill in the fields: you then need to click Add, one pattern at a time. Deleting a pattern does not unban addresses that are already banned.
- Allowed DNS Reverse: an address whose name matches a pattern and is confirmed by forward resolution is exempt from the firewall analysis. This exemption extends neither to banned patterns nor to HiveShield.
- Each list can be exported and imported as a text file (one
motif|raisonline).
Bots and search engines
The bots of the main search engines (Google, Bing, Yandex, DuckDuckGo, Baidu, Yahoo, Apple) are recognized by the host name of their address, confirmed by forward resolution. A fake bot is refused and its address banned. The DNS Reverse verification checkbox controls this recognition.
- Artificial intelligence bots: thirteen providers, blocked by default, with one switch per provider (Collection allowed or Collection blocked). The list is closed: an AI bot that is not on it is not recognized.
- Social network bots: six networks, allowed or blocked one by one, to keep or drop the previews of your pages.
- SEO and monitoring bots: one switch per tool, including Semrush, Ahrefs, Majestic, Moz, Pingdom, GTmetrix and OnCrawl.
Abuse & Reports
For each address that has attacked your site or sent spam, the screen shows its host's “abuse” contact, found automatically for IPv4 addresses when a contact exists, as well as the country's CERT.
- Test sends the report to yourself; Send reports the address to the host in one click, without confirmation; Send selection does it in bulk, after confirmation.
- The email template can be edited (sender name and address, copies, twelve variables); save it before a real send. The X-ARF attachment is optional.
- The send history keeps the date, the address, the recipient, the copies, the reason and the status. “Success” means that your site's mail system accepted the message.
No sending is automatic: every report goes out with a click.
404 & Redirects
The screen lists the missing pages seen by your visitors: requested address, referrer, IP address with its location and date, with six counters. It refreshes on its own, offers 25 to 200 rows per page and is emptied with Clear logs (permanent). Logs are kept for 30 days at most.
No distinction is made between a broken link and a bot looking for a vulnerability: the referrer, the address and the time let you work it out.
Server hardening
FreeThese three WAF Security screens protect your server without depending on the license.
.htaccess
HiveProtect writes four blocks into the .htaccess file, each with its own switch: XML-RPC closed, Server hardening, Backups and exports out of reach and PHP configuration files protected. They apply on an Apache or LiteSpeed server, if the file is writable and if no other security plugin already manages the file.
- Before each write, HiveProtect keeps a full copy of the file (the last three) and checks that the site responds; if the server returns a 500 error, the copy is put back immediately.
- Apply now writes the enabled rules, Remove our blocks removes them and turns off their switches, Restore puts back one of the three copies (the whole file is rolled back).
- The screen's verdict (“Server hardened”, “Partial protection”, “No blocks added”, “No effect”) counts the blocks present in the file: it does not prove that the server applies the rules.
- If a rule disappears from the file, HiveProtect writes it back when an administrator opens an admin page, at most once an hour.
HTTP Headers
The screen sets fifteen security, cross-origin sharing (CORS), cache and performance headers, each with its own switch. They are written to the .htaccess file: only Apache and LiteSpeed send them.
- Regenerate .htaccess rewrites the block; it is the only action that displays a write error, because a setting is saved even if the file could not be modified.
- Test the headers rereads your configuration: it does not show what the visitor actually receives. For that, use the browser's developer tools (F12 > Network).
- The security level is a configuration score, calculated from the switches that are turned on.
Protection Badge
The “Protected by HiveProtect.ai” badge is displayed at the bottom of public pages. The Footer Badge switch turns it on; you choose among four styles (full, compact, plain text, integrated into the footer), the position (left, middle or right) and, for the full style, the color. Your choices are saved immediately.
The badge is a link to hiveprotect.ai: on click, we receive your site's domain and the page address. Turning it off does not remove the meta tags that identify the plugin.
HiveShield and Cloudflare
HiveShield is the collective defense: when one site on the network blocks an attacker, the others refuse it before it tries them.
HiveShield
Your site reports to hiveprotect.ai the addresses it has banned for attacks, receives the network's list and refuses visitors whose address appears on it. HiveShield is included with the license, trial included, and active by default.
- Enable HiveShield turns participation off or on. The list arrives at your site's next synchronization: choose the frequency (15 minutes, 30 minutes or 1 hour), or click Sync now.
- The network list shows, for each address, the attack type, the number of sites that reported it and its expiry; addresses expire automatically.
- Latest HiveShield blocks summarizes your site's refusals (today, 7 days, 30 days), with the detail per address.
- The CRON diagnostics show whether scheduled tasks are running. Reschedule the CRON task recreates the task, but does not repair a stopped cron.
- Firewall bans are shared automatically: for each address, HiveShield transmits the address, the attack type, the severity, the page targeted on your site and the time. Your settings (filtered countries, refused bots) are not transmitted. The refused visitor sees an error page in English.
Cloudflare
HiveProtect finds the visitor's real address behind Cloudflare and can relay the addresses banned by the firewall to the IP access rules of your Cloudflare account. The Rules & configuration screen displays the detection (“Cloudflare configured correctly” or “incomplete configuration”).
- Create a Cloudflare API token with the permissions shown on the screen, paste it with the Zone ID (Load zones lists your domains), then click Save configuration and Test API connection.
- Cloudflare synchronization turns on the relay; the default destination chooses the zone or the account.
- The cache table lists the IP access rules of the zone and the account, including those you created elsewhere. Add IP/CIDR accepts IPv4 ranges.
Dashboard and statistics
Three places to follow what HiveProtect does on your site: the anti-spam Dashboard, the WordPress admin bar and the Analytics screens. The dashboard does not need a license; the Analytics statistics do.
Dashboard
The first screen in the menu summarizes anti-spam activity: the “Spam detected”, “Legitimate” and “Total analyses” counters, then, depending on what you have enabled, the “Honeypot System”, “Geographic filtering”, “Behavioral Detection”, “WordPress comment protection” and “Mass attack protection” blocks. It has no settings: everything is configured in Settings.
- System status: the detected form plugins, the AI API status, blocking, the threshold and a few protections. “Detected” means that the plugin is present, not that a test submission succeeded.
- Tokens and costs: with an AI key, the number of tokens consumed and an estimate of the cost, based on the prices built into the plugin.
- Recent analyses: the last 50, filterable as “All”, “Spam” and “Legitimate”, with the reason, the score, the visitor's address and the complete form content. The Not spam button adds the email address or an excerpt of the content to the rules on the False positives screen.
The counters only count what the anti-spam analyzed, not the attacks stopped by the firewall, which has its own Dashboard in WAF Security; “Blocked IPs” only counts form blocks. The screen is cached for up to 24 hours: a plugin installed a moment ago or an address that was just unblocked may take a while to show up.
WordPress admin bar
Administrators see a HiveProtect.ai (S:x|L:y|T:z) shortcut in the WordPress toolbar: S for spam, L for legitimate messages and T for the total of analyses, like the first three dashboard counters. Its menu opens the WAF Security, Analytics and Login Logs screens directly. It only appears for accounts that manage the site's options, and only if the toolbar is displayed in their profile.
These counters reset to zero with the Clear all logs button on the Detailed logs screen.
Visitor Analytics
See who visits your site: the figures come from tables in your WordPress database, and no statistics are sent to HiveProtect. The Visitor tracking switch starts and stops collection.
- Online now and trends: visitors from the last five minutes with their cities and pages, the visits curve, the breakdown by device, the traffic origin (direct, search engines, social networks, referring sites) and visits by hour.
- Rankings: the 50 most visited pages, countries, cities, browsers, screen resolutions and referring sites; a click on a number details the matching visits.
- UTM campaigns: the table of tracked campaigns and a campaign link generator, which keeps the list of your campaigns with a notes area.
- Recent Visits: one line per visit, with the pages viewed, the duration, the location and the “Human” or “Bot” label depending on whether the tracking script ran; the search covers the whole database.
- Filters and periods: device, search engine, visitor type and period, including a custom period. Interaction tracking is optional: it also records clicks and mouse movements.
- Exports and clearing: three CSV exports (the displayed page, everything, or a selection of columns); Clear cache recalculates the statistics without deleting anything; Delete all erases all visits, including the order copies on the E-commerce screen.
Bot Analytics
Bot Analytics tracks visits by authentic bots: a bot is only counted if the host name of its address (reverse DNS) does belong to its domain and resolves back to the same address. The Bot tracking switch starts and stops collection.
- Four tiles (visits, distinct bots, today's visits, most active bot), the Top 10 bots, the latest visits with the address, location and host name, the pages most visited by bots and their UTM campaigns, which read the parameters of the addresses requested by bots and therefore do not measure your own campaigns.
- Filters by bot type, by bot and by period (up to two years), three CSV exports, the Log storage limit (beyond it, the oldest entries are deleted), Clear cache and Delete all.
E-commerce Analytics
This screen is intended for WooCommerce stores: without WooCommerce, it only shows a “WooCommerce required” box and an Install WooCommerce button. HiveProtect copies orders into its database, and all the statistics read this copy.
- Import: “All orders”, “Last 30 days” or “Custom Period”, in batches with a progress bar. After that, an order enters the copy when its status changes to “processing” or “completed”; only its status is updated afterward. Clear Analytics orders deletes the copies, never WooCommerce's orders.
- Indicators over 30 days, a quarter, a year or everything: total revenue, orders, average order value, conversion, unique and returning customers, average customer lifetime value, growth; revenue and orders curve, revenue sources, conversion funnel, Top 20 products and customers (without name or email), countries, categories, days, hours and the list of orders.
- Carts and follow-ups: the screen tracks carts and lets you send a customizable follow-up email by hand (subject, introduction, button text, signature, color palette, preview and test send), whose opens, clicks and conversions are tracked.
- Clear cache and Repair empty orders fix an old or incomplete display.
Data retention and erasure
A WordPress scheduled task cleans the logs once a day, in small batches. The durations are fixed and cannot be set in the interface:
| Data | Retention period |
|---|---|
| Visits, bot visits and order copies (Analytics) | 90 days at most |
| Anti-spam log, login log, action log | One year |
| Other security logs | 60 days |
| 404 errors and geolocation cache | 30 days |
| Temporary blocks | Removed when they expire; a permanent block stays until you lift it |
| Carts, follow-ups, report history, files flagged as modified | No automatic cleanup |
To erase sooner, each Analytics screen has its Delete all button, and the Detailed logs screen has Clear all logs. There is no deletion by address or by visitor, and the plugin cannot erase the identifiers stored in visitors' browsers.
License, updates and uninstallation
The HiveProtect.ai > License screen brings together everything related to your subscription.
- Validate activates your key; Refresh license rereads its status; Remove license erases the key from your site.
- Free trial starts the 15-day trial if the plugin was not installed with WordPress's Activate button.
- Install updates the plugin; Check file integrity compares its files with those on the official server.
- Before you delete the plugin, the “Keep data when uninstalling” checkbox in HiveProtect.ai > Settings decides what stays.
Error messages, special cases (moving, change of address, failed update) and clean uninstallation are detailed in the Help Center.
A question about a setting?
The FAQ answers the most frequent questions, and the help center guides you through troubleshooting step by step.
Ready to protect your site?
Try HiveProtect free for 15 days, with all features included.