Actually, I find that calling it censorship resistance is incredibly honest.
You're absolutely right that there's a complete inability to protect anyone's personal information that someone puts out there at the blockchain level - but that's clearly a different level of "protecting registrants' personal information" than keeping such information for all website names in centralized databases that governments can access with a piece of rubber stamped paper. The two aren't conflatable the way OP mentions it.
As an example - elonmusksssnis012345167 and other such names containing personal information could be blocked by the browsers or other legally liable, centralized points of access that people use to access Handshake names. My example isn't mutually exclusive with having a decentralized, distributed base layer (root zone) for names. If such (legally needed) censorship abilities were built in at the root zone, we'd see it abused as it is in the current system. That's the censorship resistance feature.
tldr; Legal censorship can and should happen at another layer.
You're absolutely right that there's a complete inability to protect anyone's personal information that someone puts out there at the blockchain level - but that's clearly a different level of "protecting registrants' personal information" than keeping such information for all website names in centralized databases that governments can access with a piece of rubber stamped paper. The two aren't conflatable the way OP mentions it.
As an example - elonmusksssnis012345167 and other such names containing personal information could be blocked by the browsers or other legally liable, centralized points of access that people use to access Handshake names. My example isn't mutually exclusive with having a decentralized, distributed base layer (root zone) for names. If such (legally needed) censorship abilities were built in at the root zone, we'd see it abused as it is in the current system. That's the censorship resistance feature.
tldr; Legal censorship can and should happen at another layer.