Customer Portal

Your relationship with the platform, under your control.

A privacy-first account boundary for future products, licences, subscriptions, downloads, and support—designed before customer data is introduced.

Identity is not entitlement

Signing in proves who you are. It does not grant product access.

The portal separates authentication from authorization. Product access will require an active, traceable entitlement from its owning programme. Workspace identity, email possession, or account creation alone can never create a licence.

01Foundation ready

Account

Identity, profile, privacy, and account controls.

02Future

Products

Future access to entitled products and verified downloads.

03Future

Licensing

Future licence state, devices, and entitlement history.

04Future

Support

Future private cases, secure updates, and resolution history.

05Future

Subscriptions

Future plans, renewal state, and service management.

06Future

Billing

Future invoices and payment administration through a compliant provider.

Security architecture

Minimum identity. Explicit authority. No accidental persistence.

The current foundation reads verified identity headers for the active request. It does not create a customer database, store profiles, infer membership, or retain activity.

  1. 01Authenticate
  2. 02Authorize
  3. 03Minimise
  4. 04Audit