Device identity and recovery
ActivationClient keeps a private state directory. You do not collect CPU, disk or MAC values. The SDK creates installation credentials and detects supported device protection internally.
| Situation | Action and guarantee |
|---|---|
| Restart/update | Preserve the same state directory; do not create another registration. |
| Container recreation | Mount a dedicated private volume; never distribute shared installation credentials. |
| Lost local state on the same protected device | Create a new request. A verified matching hardware anchor allows recovery. |
| New software ID or different device | Request an exact-target transfer and await vendor review. |
| Offline file deleted or machine formatted | Deletion alone does not prove old backups stopped. Use reviewed transfer when recovery is unavailable. |
Current file-based clock tracking is not protected against full state rollback. Software credentials can be copied; a clonable virtual security device does not provide the same assurance as physical hardware. Do not call these mechanisms tamper-proof.