Fans contact EVEN support at [email protected], and requests are honored under the controller and processor structure of the campaign.
What your team has to do
Your team has nothing operational to do in most cases. Privacy requests land with EVEN rather than with the label or management, and EVEN handles the response. That matters during a release week, when a data request arriving in a manager's inbox is the last thing anyone has time for.
Deletion requests
A fan can email [email protected] from the email or phone number on their account and have their account or data removed. Verification runs off the account details rather than requiring the fan to prove identity separately.
How opt-outs propagate
When a fan opts out, the consent chain carries that through the integrations, so the opt-out is honored in your CRM and downstream systems rather than only inside EVEN. This is the part that most often breaks when data is exported as raw files instead of synced, which is why partner access flows through platform controls.
Set per campaign
The controller and processor structure, the privacy policy, and the opt-in language are all configured per campaign before launch, naming the actual parties. Each release also carries its own Terms of Service and Privacy Policy.
If a request reaches you first
Point the fan at [email protected], or raise it in your shared thread with your EVEN team and it will be picked up.