FreeFuture AI Secure Monitoring

By freefuture

0+ active installationsVersion 0.8.4

Local WordPress safeguards, clear activity alerts and optional AI guidance for people managing their own business website.

Description

FreeFuture AI Secure Monitoring shows what is protected, what needs attention and the next useful action. One administrator is enough. Local features are free, require no SicurezzaAI account or subscription, and do not expire when a service trial or subscription ends.

  • Guided setup checks the host, prepares private storage on compatible hosting and verifies the notification address.
  • Optional sign-in protection pauses repeated failures on the standard WordPress login.
  • Local monitoring highlights administrator changes, unusual sign-in activity and unusual volumes of email requests made through WordPress.
  • The native WordPress content export requires confirmation with the requesting administrator’s current password. Confirmation belongs to that request and login session, expires after 24 hours and permits one download.
  • Optional email alerts use the site’s own mail service. Delivery depends on the host and scheduled tasks.
  • Advanced connection controls can observe or restrict destinations used through the WordPress HTTP API.

The dashboard suggests checks; administrators decide what to do. It does not repair files, reverse account changes or stop all email automatically. Optional AI is a separate paid service; local controls work without it.

Coverage is limited to supported WordPress hooks. This is not a full-server firewall, malware scanner, mailbox backup or guarantee against attacks. Direct database access, direct SMTP/cURL/sockets and custom integrations may bypass these controls. Code with the plugin’s privileges can disable its hooks. Deactivation restores ordinary WordPress export and HTTP behaviour. Phone push notifications are not included.

Documentation and support

External services

Optional SicurezzaAI analysis, operated by Free Future LDA

AI is off by default. The administrator must connect a SicurezzaAI account and site, check the consent box and enable AI. Plugin activation alone does not start the service or subscription.

The service costs EUR 15/month for one linked site, including VAT where due. Eligible new accounts receive a 15-day trial with one initial AI analysis, once per account. Paid subscriptions include one analysis every seven days. External checkout requires a card; billing renews monthly unless cancelled. Signup accepts EU billing addresses. Review the terms before purchasing. No personal OpenAI account/key is needed. Payment is for the hosted service, not unlocking local functions.

After opt-in, the plugin contacts https://sicurezzaai.it/wp-json/guardian-store/v1/ai/ over HTTPS to connect the site, submit an analysis or retrieve its status. Connection requests carry the site URL, a one-use connection code and challenge. Later requests use a service credential and request identifier. FreeFuture makes a challenge request back to the site’s i-guardian/v1/ai-proof endpoint to verify control of the linked HTTPS site. These credentials and challenges are not forwarded as AI input.

The analysis summary contains bounded activity counts, time windows, configuration and coverage signals, and report-specific account aliases. It excludes raw logs, account names, visitor IP addresses, passwords, email contents and recipients. HTTPS still exposes connection information, including the server IP, to the receiving infrastructure. FreeFuture checks eligibility and sends the summary to OpenAI to produce explanations and suggested checks. No executable code is downloaded.

FreeFuture stores connection identifiers, credential hashes, status, usage and reports, but not submitted summaries in its AI ledger. Scheduled cleanup removes request/report records older than 90 days in batches; minimal eligibility/trial history and active connections remain. The local archive retains the latest report and summary until replaced or managed by its operator. Pausing stops future submissions; an accepted request may finish. Outages, service limits or delayed tasks may postpone reports without stopping local safeguards.

FreeFuture service terms | FreeFuture privacy notice

OpenAI, used by FreeFuture for opted-in reports

FreeFuture sends the minimized summary to https://api.openai.com/v1/responses. The plugin connects to FreeFuture; the provider key stays on FreeFuture’s server. Reports may be wrong and never execute repairs or change permissions.

FreeFuture requests no stored response. This is not zero retention: OpenAI’s default abuse-monitoring retention is up to 30 days, subject to its applicable exceptions and policies. Processing is not promised to remain in the EU. See OpenAI API data controls, the OpenAI Services Agreement and OpenAI privacy information. API content is governed by the API data controls and business agreement.

Example addresses and outbound controls

The https://api.example.com and https://api.example.com:8443 addresses in the connection-settings help text are illustrative placeholders, not third-party services, configured destinations or default permissions. The plugin does not send requests to these example addresses. The outbound-control feature observes or filters requests already initiated through the WordPress HTTP API by the site or its other plugins; it does not create requests to observed or allowed origins. FreeFuture and its OpenAI processor, described above, are the optional analysis service destinations.

Installation

  1. Check that the site uses single-site WordPress 5.9+, PHP 7.4+ and PDO SQLite with SQLite 3.7.17+. Web and scheduled-task PHP both need these dependencies. Keep software patched; minimum compatibility is not a security certification.
  2. Install and activate FreeFuture AI Secure Monitoring. For a supplied ZIP, use Plugins → Add New → Upload Plugin. Open FreeFuture AI Secure Monitoring → Guided setup. Local protection requires no service account or payment.
  3. Let the guide prepare the private archive. Automatic setup needs compatible Unix hosting, verifiable ownership and storage outside public roots. If unavailable, setup explains the issue and native exports stay paused; no public-directory fallback is used.
  4. Choose the alert address, send a test and confirm actual receipt. Enable email alerts using the separate action when offered.
  5. Start recommended protection. Keep the sign-in protection checkbox selected to enable it with local monitoring. Existing connection rules are preserved. Advanced settings remain optional.
  6. Only if you want hosted AI, obtain a connection code from your SicurezzaAI account, review the disclosure above and explicitly enable AI. This is separate from local setup.

Confirm exports with your own password, then return to the download tab. If setup fails, contact support; never send passwords, keys or an archive copy.

FAQ

What happens if I do not subscribe or stop paying?

Local monitoring, sign-in protection, export confirmation, alerts and connection controls remain usable. An expired entitlement stops new hosted AI reports, not the local plugin. Reinstalling does not reset the initial-analysis allowance.

Does protection wait for AI?

No. If enabled, 20 standard login failures from one verified source in five minutes trigger a 60-second pause. Existing sessions and password recovery remain available. Shared networks may share a pause; SSO, API/XML-RPC, custom logins and distributed sources are outside coverage. Ambiguous sources or unavailable storage preserve WordPress’s login result and show the gap.

Administrator-change cases appear locally without waiting for AI. Activity analysis/alerts use scheduled tasks and may run late. Email counts measure wp_mail requests, not deliveries or personal mailboxes. Missing observations and backlog are reported.

What do advanced connection controls cover?

They start off. Observation records destinations without blocking or trusting them. Explicit blocking uses an origin allowlist for WordPress HTTP API calls and disables redirects. Test integrations first. An allowed origin permits all paths, not approved data contents. Blocked calls are not queued. AI consent permits only the plugin’s AI requests through this control; other rules remain unchanged.

What stays on my server?

Private storage holds export request identifiers, decisions, activity metadata, cases and administrator inventories, not exported files. Login-source hashes are site-specific; attempted usernames and clear visitor IPs are not stored. Activity retention: events 7 days, counters 30 days, closed cases 90 days, with capacity limits. Open cases, inventories, approved comparison data and export audit records remain for the operator to manage. Connection aggregates expire after seven inactive days when cleanup runs. Cleanup and alerts depend on scheduled execution. The configured mail provider processes alert recipients and messages.

WordPress’s Privacy Policy Guide includes suggested wording. Personal-data tools export matching participation and identify retained security records for operator review. Backups follow the site’s retention policy.

What happens when I uninstall or update?

Uninstall removes schedules/settings but preserves private archives for recovery; scheduled cleanup stops. The operator manages retained records/backups. Back up before updates and preserve the archive location. Installations obtained from WordPress.org use WordPress updates; directly distributed installations use the account’s ZIP. No custom external updater is included. The GPLv2-or-later licence is included.

Changelog

0.8.4

  • Make action-specific nonce checks explicit after administrator and POST checks.
  • Validate and sanitize identifiers and decisions without accepting repaired values.
  • Validate login-source fields before resolution and canonicalize public archive roots early.

0.8.3

  • Sanitize and unslash notice inputs while rejecting altered feedback codes.
  • Let WordPress.org manage directory translations automatically; retain bundled Italian for direct installations.
  • Clarify that sample origins in the settings help text are examples, not external services.

0.8.2

  • Prepare directory metadata and document free local features and the optional hosted AI service.
  • Clarify external destinations, consent, data handling and service terms.
  • Reject malformed export confirmations without changing the submitted identifier or decision.
  • Preserve private-storage checks when WordPress escapes special characters in server paths.

0.8.1

  • Add a direct email-alert activation button after the notification address is verified, without changing consent automatically.