Skip to content
Privacy Policy

Data flows should be explicit.

Summary: RevGuard is designed around local-first storefront diagnostics and data minimization. This policy describes the current website, browser-extension and local-workflow data flows; it is not a blanket legal-compliance certification.

1. Marketing website

This static marketing site does not intentionally collect form submissions, run first-party analytics, or load advertising trackers. If you choose an external checkout or email link, the destination service processes that interaction under its own terms and privacy policy.

2. Browser extension diagnostics

The extension analyzes the publicly rendered DOM of the active storefront tab to produce technical evidence. Storefront content is not automatically uploaded to a RevGuard-operated cloud service as part of the standard local audit flow.

3. License validation

When a license is activated or validated, the extension sends the license key and required activation metadata to Lemon Squeezy's licensing service. Local license state may be cached in browser extension storage. RevGuard does not receive raw payment-card data from Lemon Squeezy.

4. Optional AI features

If you explicitly invoke a supported BYOK AI feature, the relevant context is sent to the configured AI provider using the API key you supplied. The current extension is designed to keep the BYOK key session-scoped rather than persistently stored. The selected provider's terms and privacy policy apply to those requests.

5. Local settings and reports

Extension preferences, report data and licensed configuration may be stored in browser extension storage. Licensed store-domain bindings may also sync through Chrome Sync if enabled. You can clear local report and AI-copy data through browser extension storage controls; deactivate your license before removing the extension. A separately supplied local operator workflow may store configuration, approval state, suppression records and reports on the machine where it runs.

6. Data minimization

Do not use RevGuard to collect payment-card details, private admin credentials, or unrelated non-public customer information. RevGuard is intended for public storefront diagnostics and explicitly authorized technical work.

7. Privacy requests

For privacy questions or requests concerning data controlled by RevGuard, contact audit@revguardpro.com. Data processed by third-party services may also need to be addressed directly with those providers.

8. Policy changes

We may update this policy when product data flows materially change. The public policy should be updated before a materially different data-processing feature is released.