Various licensing requests, which are sent to the licensing server to acquire and activate a license, de-activate and relinquish, get licensing status, etc. for the system being licensed.

License activation and re-activation requests contain the following information:

• Request Version: so we can support software changes, over time
• the Re/License Info:
• Info Version: so we can support software changes, over time
• Purchased Product Name: the license's product identifier
• Purchased Product Version: the license's product version identifier
• Purchased License Kind: the kind of license
• Purchased License Serial: the license's serial number
• Requesting Product Name: the licensed product's identifier
• Requesting Product Version: the licensed product's version identifier
• Requesting Week Number: the week the request was made
• System Info: see detail below
• Checksum: a checksum to (doubly) ensure the validity of the transmitted data

The unlicensing request, which is required by the licensing server to request that a license be relinquished for a system, contains the following information:

• Unlicense Version: so we can support software changes, over time
• License: the License previously generated and received from the licensing server (this is encrypted)
• Requesting Week Number: the week the request was made
• System Info: see detail below
• Checksum: a checksum to (doubly) ensure the validity of the transmitted data

The unlicensing confirmation, which is required by the licensing server to de-activate and relinquish a license for a system, contains the following information:

• Confirmation Version: so we can support software changes, over time
• License: the License previously generated and received from the licensing server (this is encrypted)
• Confirmation ID: the Unlicense Confirmation identifier
• Requesting Week Number: the week the request was made
• System Info: see detail below
• Unlicense Date: the date of the unlicensing
• Checksum: a checksum to (doubly) ensure the validity of the transmitted data

The System Info is information that is used by the licensing server to help associate license activations with licensed systems, including as they change over time — it's a dynamic and adaptive patentable technology:

• Info Version: so we can support software changes, over time
• Requesting MAC Addresses: certain ethernet MAC address(es)
• Requesting System's Serial Numbers and/or UUIDs: the system serial number and/or an operating system and/or hardware UUID (where available)
• Requesting System's Kind: the system kind (where available)
• Requesting System's Model: the system model information (where available)
• Multiple other attributes on any given system: these are all pieces of information about the system that are available via standard operating-system supplied interfaces

Note that:

• no information related to Users or (other) applications is required, desired or captured
• ethernet MAC addresses are (by standards, are supposed to be but are not always) unique for every ethernet interface ever made and is something that's sent as a part of network packets, so it's always externally visible
• serial numbers and UUIDs are, by definition, supposed to be unique but are not always
• all System Info we capture is available via normal operating-system interfaces
• only specific employees at Derman Enterprises and the licensed application Vendor can view information that's captured and, by law, we're prevented from using this information for any purposes other than to support licensing (for more information, see our Privacy Policy page)
• you can use network packet-capture software to verify the nature of information being communicated — e.g., on OS X, issue the Terminal command:
  sudo tcpdump -pxX -vv -s 0 host www.derman.com