LicenseCenterSoftware License Service Center

Privacy

How customer and license data is handled.

This page explains what information the license service records and how it is used to process orders, activate products, provide support, and protect the service.Last updated June 23, 2026

Information we collect

We collect the information needed to deliver and operate licensed software.

  • Order email, contact name, company name, selected product, plan, price, currency, and payment status.
  • License key, activation status, product identifier, domain, server fingerprint when sent by the product, expiry date, and update eligibility.
  • Support ticket messages, attachments, reply links, technical details provided by the customer, and email delivery status.
  • Basic security records such as IP hash, user agent, rate-limit events, and audit logs used to detect abuse.

How we use information

Data is used only for the business functions expected from a software license service.

  • Create orders, deliver license keys, verify activation, and manage renewals.
  • Send order, license, support, expiry, payment, and security notifications.
  • Review suspicious activity, unauthorized reselling, repeated binding changes, and payment disputes.
  • Improve support quality by keeping a history of tickets and product context.

Payment and third-party providers

Card and wallet details are processed by the selected payment provider. The license center stores order references, webhook results, and confirmation status, not raw card numbers.

  • Automatic gateways may redirect the customer to the payment provider.
  • USDT and manual payment records may include transaction hashes or manual confirmation notes.
  • Provider logs are kept so failed or disputed orders can be investigated.

Security and retention

Access to private records is limited to authorized operators. Attachments and sensitive logs should be retained only as long as required for support, accounting, and license enforcement.

  • Private customer links use random tokens and expiration rules.
  • License and update APIs use rate limits and signed responses where applicable.
  • Customers can request correction or deletion where business, security, or legal retention rules allow it.