Verification & Licensing Policy

1. Verification Frameworks

To secure our services and confirm subscription integrity, the Extension uses a dual verification model:

1.1 License Key Authentication

Upon successfully completing a Premium subscription purchase via PayPal, your account is provisioned with a unique cryptographic license token. This token must be authenticated by the Extension instance via secure API calls to our licensing endpoint. This process confirms the purchase status and ensures your subscription remains active.

1.2 Active Production & Target Domain Tracking

The licensing matrix handles authorization based on target properties:

• Local Development Scopes: Standard developer testing environments (e.g., localhost, 127.0.0.1) are broadly exempted from seat limits, enabling extensive offline iteration.
• Staging & Production Environments: Premium licenses can be actively bound to a designated number of staging URLs or live production platforms per seat license. This restriction helps protect against unauthorized token sharing.

2. Misuse Red Flags and Suspension Actions

Our tracking systems continuously monitor for unusual verification behaviors. The following activities may trigger safety alerts:

• Concurrent, high-frequency premium authentication requests originating from widely separated geographic areas using a single license token.
• Systematic modification of client-side configuration variables to bypass verification limits.

If suspicious behavior is detected, we reserve the right to temporarily suspend the license token while an audit is performed. We will reach out to the registered account owner via email to resolve the issue or verify the activity before any permanent termination action is applied.