Token & Billing Terms

Non-binding summary

Packages include feature capacity/limits. Tokens are optional platform credits for extra usage (translation, AI, audio, locations, campaigns). Tokens are not money. B2B purchases are generally non-refundable.

1. Package capacity and limits

Subscription packages define included feature capacity (locations, campaigns, journeys, employees, etc.), not a general prepaid token bank unless explicitly stated. Usage beyond included limits may require token purchase or plan upgrade.

2. Token nature

Tokens are optional digital platform credits. They are not money, e-money, legal tender, interest-bearing, or transferable unless Zlox authorises in writing. Tokens may be consumed for translation, AI content, audio transcription, extra locations, campaigns, journeys, or other enabled services.

3. Usage and deductions

Token usage is deducted according to a usage table shown in the dashboard before or at the time of use. Purchased translation hours and token balances are separate pools and are not interchangeable.

4. Expiry

Purchased tokens expire after 24 months unless stated otherwise at purchase. Promotional tokens may expire sooner. Subscription-included capacity resets per billing period unless roll-over is expressly stated.

5. Refunds and chargebacks

B2B token and subscription purchases are non-refundable except where mandatory law requires. Chargebacks may trigger suspension, token reversal, and collection.

6. VAT and invoices

Prices may be shown exclusive or inclusive of VAT as indicated at checkout. Valid billing profile data is required for compliant invoices.

7. Non-payment and suspension

Failed payments, overdue invoices, fraud, or abuse may result in feature suspension, including translation, AI, and token spending.

8. Merchant dashboard requirements

Zlox will show balance, deduction history, token lot source, expiry date, and invoice reference in the billing dashboard where technically available.

9. Change log

  • v2.0.0 (2026-07-27): Updated for package limits, separate translation hours, and usage-table deductions.

Implementation Notes (non-legal)

  • Require token billing acceptance before token checkout.
  • Display usage table and estimate before AI/translation actions.