Manage YAAA accounts, license keys, and activated devices without exposing licensing secrets in client-side code.
The portal uses server-rendered forms, CSRF protection, secure session cookies, prepared database statements, and generic authentication errors. Production deployments must provide private environment secrets before real licenses are issued.
Customers can bind a license to a local device fingerprint, see active device counts, and deactivate retired devices. Raw license keys are never stored; server code stores keyed hashes only.
For procurement, enterprise review, and lost-device recovery, contact support. Do not send license keys or private workflow files in plain support messages unless a secure channel has been arranged.
