ARWANZAI POLICY

Licensing

ArwanzAI licensing controls the scope of service access without turning payment metadata into automatic execution authority.

Version 0.9.0-web-policyUpdated 26/09/2026Automatic execution: NEVER

1. Core licence attributes

Customer/organization identity.
Plan and deployment mode.
Seats and user scope.
Analysis allowance.
Capability entitlements.
Issue and expiry dates.
Licence status and revocation state.

2. Signed licences

Production licences are intended to be signed and verified so that the customer and service can establish the permitted scope without exposing the signing private key.

3. Status

The working state model includes ACTIVE, EXPIRING SOON, EXPIRED and REVOKED. Expiry or revocation does not silently create a new entitlement.

4. Analysis allowance

The current Golden Freeze implementation treats analysis allowance as a licence-term entitlement rather than an automatic monthly reset. Any future reset model would require an explicit product/configuration change.

5. Deployment

Licences may distinguish SaaS and customer-managed/offline deployment where contractually offered.

6. Renewal and replacement

Renewal creates a new approved commercial/licence transition; replacement or revocation is recorded separately so the licence history remains auditable.

7. Customer responsibility

Customers must keep their licensed seats and usage within the agreed scope and must not share licence material in a way that bypasses entitlement controls.

8. Commercial dependency

Pricing, payment method, taxes and final invoice rules are governed separately by the accepted commercial documents. Payment does not by itself grant entitlement.