Licensing portal online

05 / Trust

Security and data.

The licensing portal is a commercial system with a deliberately narrow data footprint. This page describes the boundary and the controls around the signing path.

Trust anchor

Production binaries compile the vendor Ed25519 public key and key ID into the release. A token signed by an unknown key is rejected. Environment-configured public keys are a development or migration path, not the production default.

A8M1.<base64url payload>.<base64url ed25519 signature>

The signature covers the literal A8M1.<payload> bytes. The payload carries version, license ID, key ID, plan, edition, seats, features, deployment, issue/expiry and optional limits.

Key custody

  • Private signing keys never enter the product, a release archive or a customer deployment.
  • Production should use an isolated signer backed by KMS/HSM or a restricted vendor command.
  • Key IDs and a rotation ring let old tokens remain valid while new issuance moves to a new key.
  • Development file keys are for local tests only and must not issue customer licenses.

What the portal stores

DataWhy
Organization, contact, deployment and customer recordsDeliver the license, identify the estate and support the account.
Subscription, invoice, tax and payment identifiersBill and renew the contract. Card data stays with Stripe.
License claims, issue/reissue/revoke events and auditProve what was issued and who changed it.
Usage counts and enabled-feature countsSeat utilization, overage and support. No message content.

Not stored: mail, contacts, subjects, message bodies, attachments, mailbox contents or end-user passwords.

Retention

Sign-in links are single-use and expire in 15 minutes. Webhook and email delivery records are kept for operational troubleshooting. Invoices and tax records follow statutory retention. Usage reports can be pruned on a documented schedule; aggregate seat counts and license history remain for renewal and audit. A customer deletion request removes contact and deployment records that are not required for tax, fraud prevention or an active contract.

Revocation

Revocation blocks a reissue or a future download and adds the license ID to an Ed25519-signed revocation list at /api/v1/revocations. An offline token already installed on a customer server remains valid until its signed expiry unless the deployment is revocation-aware and refreshes that list. A revocation-aware deployment verifies envelope.signature over the decoded envelope.payload, rejects a list whose key ID is unknown, keeps the last verified copy on failure, and never treats an unverified list as authoritative. The product is explicit about this instead of claiming a remote kill switch.

Operational controls

  • TLS termination with HSTS, strict content security policy and no framing.
  • Customer sessions are signed, HttpOnly, SameSite=Lax cookies; operator sessions are separate, SameSite=Strict and scoped to the console host.
  • CSRF protection on forms and rate limits on sign-in, trial, checkout, claim and usage endpoints.
  • Stripe webhooks are signature-verified and idempotent.
  • Operator console is intended for a separate hostname or VPN-restricted route, with audit attribution.
Subprocessors.

Stripe processes payments. The deployment host, email provider and database provider are selected by the operator. A current subprocessor and data-location list is available on request from licensing@alt8mail.com.

NextFAQ