Defaults for CB Privacy have not been implemented. CB Privacy is not currently our top priority, we will get to the feature when time permits. You're welcome to edit and suggest implementations to further speed development of said feature as the plugin is open source.

I've already implemented defaults; patch is available on forge. Patch does not guarantee the exact implementation as adjustments may be made. So if patch is applied and a new release is made you should then install that new release. With patch applied admins will be able to set a default privacy for a field that has not yet had privacy applied (e.g. at registration or first time profile edit).

If you need information to be private then simply set it not to display on profile; I fail to see how this is even remotely an issue. We are aware several governments have privacy laws and CB more then complies with them based off how the admin has configured their site. For instance if Email must be private in your country then simply set it to not show on profile; it will never display.

As in terms of CB Privacy it gives the user absolute control over the privacy of their information. We certainly can not speak for 3rd party developers integrations however as if they pull this data directly from database it will clearly ignore privacy restraints. If however they use API to retrieve a field then it will respect those privacy settings.

CB Privacy isn't our top priority. While important it is just a small part of what CB is. This does not mean we don't upgrade or maintain it. We simply work on it when we can and not above say fixing critical bugs or security issues. We plan to have much more controls of course with release of CB 2.0, which will hopefully have privacy controls built in making the necessity of CB Privacy obsolete.

At any rate CB is free and completely open source. This means you are free to edit it in any way you want and implement anything you want; if there's something you need that CB lacks then simply implement it or develop as a plugin (best approach). Rarely do users propose fixes or features as patchs to fix an issue; they simply wait for us to do it. With over 30+ projects and 3 team members (expanding this is not exactly simple either.. we do not have corporate funds for a huge team.. subscribers is our only income.. with CB being free not many feel need to subscribe) you could understand our time is thin; we really encourage developers to dig in and help.. it would be greatly appreciated!