Interesting to see this stuff. I really enjoyed cracking this back in the day, just for friends, but took a different approach of using sector editors to read the code on the disk to find where the checks wer done to see if the protections were present and replacing it with NOPs ($EA), or changing BNEs to BEQs. What was more interesting was how the code that did the check was also moved about the disk, I remember seeing for a particular piece of code it did a B-E (Block Execute) on Track 5 Sector 5. I could plainly see the protection check on that spot on the disk. My young self was very excited about working it out. The puzzle of copy protection was more fun than playing the actual games. Very frequently the directory tracks (18?? I think) were overwritten but it was obvious looking over the disk to see the headers for various programs and the load start address so it was easy to rebuild. Golden times. I've coded since then, and only recently have stopped as AI has finally got better than me!!
IP address inspection has been getting a large amount of attention recently. It is considered a privacy violation, yet it is required to determine location, so devs know which privacy laws apply.
GDPR only applies in Europe, and CCPA only applies in California. How is one meant to determine which set of laws applies inside a piece of software without being able to determine location?
A waste of time (don't bother) answer is : Just apply maximum privacy everywhere and you won't have to worry about it... The response is always going to be - Many free tools you use are funded by advertising etc and advertising depends on being able to know where someone is, at least to the country level. Cutting off location and therefore revenue is not going to give people the software they want.
Other facts that usually matter - only 1-2% of people want to pay for private software. Everyone else wants the free option. Source : my apps.