Wed May 06, 2026 5:45 am
Hello,
Thank you for your continued feedback. We fully understand your concerns regarding data security and compliance, and we sincerely apologize for the anxiety this has caused. We value your business and want to provide complete transparency to address these issues.
Here are the answers to your specific questions:
1. Payload Data Structure and Privacy
We understand your need to know exactly what is being transmitted. Here is the explanation of the process:
How it works: When the client is online, it sends requests to our license verification service. The service differentiates clients by these information and creates a unique machine ID, which serves as the foundation for license verification.
Privacy Guarantee: We do not record, store, or track the actual address of your machines. The ID generated is random and cannot be reverse-engineered to reveal hardware information. This mechanism is solely to ensure the license is not abused beyond its scope.
2. Validation Logic for "Unlimited" Licenses
Regarding your question on why checks occur even with an "unlimited number of deployment locations" license:
While the client application is programmed to trigger a request by default (as part of the standard library code), our server is configured to recognize your specific license type.
Once recognized, our service performs no validation checks for your license. The request is essentially a "handshake" that is ignored on our end, ensuring your unlimited rights are respected without interference.
We hope this clarifies the situation. Our goal is to protect the software's integrity while fully respecting your privacy and operational requirements.
Please let us know if you need any further technical details.
Sincerely,
Amy
E-iceblue support team