=== Revenue Guard ===
Contributors: revenueguard
Tags: monitoring, woocommerce, forms, email, webhook
Requires at least: 6.4
Requires PHP: 8.0
Stable tag: 0.4.0-beta
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Revenue Guard monitors operational signals that can silently cost a WordPress business leads and revenue.

== Description ==

Revenue Guard beta connects WordPress to the Revenue Guard monitoring service. Purchase through Freemius Hosted Checkout, then use your license key to connect. Licensing is validated by the service; no Freemius WordPress SDK or customer dashboard is included.

The plugin can monitor:
* WordPress/PHPMailer mail send attempt success/failure (not confirmed inbox delivery).
* Contact Form 7, Gravity Forms, WPForms, and Elementor Pro form submissions.
* WooCommerce orders, completed payments, failed orders, and refunds.
* Failed outbound WordPress HTTP requests using host and a locally keyed path fingerprint; no raw path, query string or request body.
* Periodic plugin heartbeat events.

Privacy by default: Revenue Guard is designed not to send form field values, customer names, customer email addresses, payment card data, or outbound request bodies.

The plugin contacts the Revenue Guard service only after an administrator explicitly connects an account and consents to operational telemetry.

Service: Revenue Guard (private beta).
Privacy Policy, Terms of Service and Data Processing Agreement: pending publication by the beta operator. Review those documents before enabling monitoring.

== Installation ==

1. Upload and activate Revenue Guard.
2. Open Revenue Guard in wp-admin.
3. Paste the license key from your Freemius purchase information and accept monitoring consent.
4. Click Connect Revenue Guard and confirm Protected, Connected and Active.
5. Click Send test event. Wait for Test successful to confirm service communication. This does not confirm inbox delivery or correct checkout/webhook configuration.

== Upgrade notice ==

0.2.0 adds an idempotent queue migration and strict local event validation. Old credentials without a saved connection URL are blocked until an explicit Reset as new site. This confirmed reset clears copied credentials/queue and creates a new UUID/privacy salt; revoke the old cloud identity separately if appropriate. Changed home URLs or API destinations never silently reuse a production identity.

Normal Disconnect revokes the cloud token before clearing the local connection. Force local disconnect is a separate confirmed recovery action that does not guarantee remote revocation. A local diagnostics export excludes credentials and event payloads.

The documented service address is https://api.revenueguard.com/v1. Its availability and the beta operator's legal links must be verified before inviting customers. A beta operator can configure REVENUE_GUARD_API_BASE before the first connection. Changing it on an already connected site intentionally triggers identity protection. The installation does not require Composer. WordPress 6.4+, PHP 8.0+; multisite network activation is not supported.

== Changelog ==

= 0.4.0-beta =
* Guided connection, subscription pause, site limit and temporary error screens.
* A correlated test event confirms communication only after server acceptance.
* Safe diagnostics stay separate from setup; billing pause preserves the queue.
* Installable runtime-only package; Hosted Checkout with server-side licensing.

= 0.2.0 =
* Exact local schemas, HMAC privacy, clone detection, versioned queue migration.
* Bounded backoff, poison isolation, dead letters, safe diagnostics and remote revocation.


= 0.1.0 =
* Initial MVP scaffold.
