I have a business requirement where I need to take the current user, and based on certain user properties, filter out User profile properties such as fax/phone etc if the current user does not meet certain business rules. Basically this solution has it's own extremely complex user profile privacy requirements.
The logic for this is surfaced via the user profile service, getting this is not the issue - the issue is where in the search pipeline can I implement this business logic so the properties are empty when they hit the display template render process?
I've looked at extending the search results web part, but as things are done client side I don't think I can implement here - my next step is to look at a Post security trimmer, but believe this filters out whole results not just properties.
SP2013, On premises, highly customised.
Any one faced a similar problem?