implementing measures that would prevent one device from accidentally (or intentionally) being activated to another account without support intervention and the deletion of all prior account provisions to that device.
I think this is good idea but I will caution you about some issues I have experienced working for a cable operator who "locked" cable modems in a similar fashion and has ended up with multiple issues where someone legitimately purchased a modem on ebay or other public sites only to have it refused to be provisioned because it was still mapped to another account.
as I understand your previous thread, you are mapping the mac address to the account. This is going to bite you for in three ways in the future.
first, if your customer moves his SD card to another rPi, then the MAC address will change
same is true if they in the future use a wireless interface rather than the built in ETH interface
last, if someone decides to sell their rPi and it inadvertently gets picked up to run your software...well, you get the idea.
I would suggest you would be better off placing a user serial number in a config file so that it is mapped to the software and the user rather than using the hardware as your auth mechanism
it will save you, and your customers much grief in the future.
I appreciate your advice
luckily, our support team is prepared to assist any users experiencing those issues. We expect such things to happen as ownership transfers or users switch devices. We may revisit this in the future.