No. The activation token (JWT) is encrypted with OS‑level secure storage. The raw license key is never persisted after activation; only the signed token is kept.
All UI text is fully localizable; the activation flow adapts to right‑to‑left languages without breaking the layout. | Integration | API Endpoint | Data Flow | |-------------|--------------|-----------| | License Portal | POST /v1/licenses | Create, edit, revoke licenses. | | Activation Service | POST /v1/activate | Validate key, return JWT. | | Renewal Service | POST /v1/renew | Exchange expiring token for fresh token. | | Analytics | GET /v1/metrics | Pull activation counts, churn, geography. | | Third‑Party Resellers | POST /v1/bulk-keys | Bulk download of pre‑generated keys. | | Support Tool | GET /v1/license/key | Verify status for support agents. | system mechanic license key
Compromised keys can be revoked instantly from the admin portal. The next time the client contacts the activation service it will receive a revocation response and will block further usage, prompting the user to obtain a replacement key. All UI text is fully localizable; the activation
Trial keys have a built‑in expiration timestamp (usually 7‑14 days) and a limited feature set. Once the trial expires, the app automatically disables premium modules and displays a “Upgrade Now” banner. | | Renewal Service | POST /v1/renew |