Currently, the Data Privacy Opt-Out functionality removes the HCP from visibility anyone without the Opt-Out HCP DVP permission, and downstream, overwrite the name of the record along with Veeva maintained fields with blank / Opt-out values. However, current fields are not masked via this process and would be helpful to have the option to or include custom fields by default. An example is a custom email field might still be visibile in the downstream CRM system even after opt-out since it is not automatically masked through the target subscription.