MindForge Guard License Hub

Terms, privacy, refunds, and boundaries

PricingLicense Hub

Terms

  • Commercial access covers checkout, signed license delivery, License Hub account access, and bounded account visibility.
  • The local Guard CLI remains the runtime governance surface and uses the locally installed signed license file.
  • License Hub does not provide execution authority, policy takeover, or hosted control-plane behavior.

Privacy

  • License Hub may process purchase email, order state, billing state, account session, and license delivery metadata.
  • The billing provider continues to handle self-serve payment and billing events for checkout.
  • Operational email is used for login, delivery, account access, and support workflows.

Refunds

  • Refunds and cancellations are separate lifecycle actions and may update commercial license status differently.
  • A refund may cause the related commercial license to become inactive or revoked according to the billing lifecycle.
  • Billing questions should include the purchase email and available order context.

Product boundary

  • MindForge Guard remains recommendation-only, additive-only, non-executing, and local-first.
  • Audit output, verdict, and exit behavior are not changed by License Hub.
  • Permit and classify behavior are not changed by License Hub.