That's probably the double output issue. I've sent you an email with test builds for CB Privacy and CB Conditional to the email address attached to your JP account. Please give those a try (be sure both are installed) and let me know if issue resolves.

So the issue is not resolved with the two builds I've sent? Will attempt to replicate your results here locally.

How are you conditioning or privacy controlling the username field? Are you conditioning AND privacy controlling the username field at the same time?

Ah, substituting it in as a value. Ok, thank you. Will investigate further to see what's causing your issue.

Is the username field on the tab being conditioned?

Edit: I am unable to confirm the issue still. Substituting in the username for a tab conditional value appears to be working fine. Also note you should be using [cb:userdata field="username" user="#me" /] as you need to compare against the raw value instead of HTML formatted (userdata instead of userfield)

Edit: Ok, I could confirm your issue. This only happens when you substitute in a field to condition a tab that the field is on. If you use userdata instead of userfield then there's no issue. Will see if I can implement a fix for userfield usage though.

Ok, was able to fix the issue and prevent all future looping problems as well. Will be releasing 4.0.1 today for both CB Privacy and CB Conditional.