Hi @johndobson1,
Thanks for letting us know. Happy to provide some context as to why you’re experiencing this.
At this point in time it’s indeed not possible to convert an existing contact property into a sensitive data property. This is because of the way we designed these new properties. However, it’s likely we develop this functionality in the future.
1. Theoretically you could create a custom sensitive property and use it to store email addresses. However, I’m doubt you’d be able to have this new property act as a replacement for the default email address field. So I don’t think this will work. The reason why we’re preventing you from doing so, is because our email functionality (just like our other channels) aren’t end-to-end encrypted. Very few email providers are sadly.
2. More ore less same answer as above, our comms channels like SMS and Email don’t support sensitive data.
Thanks,