CB Privacy doesn't store privacy rules that it doesn't need to. That'd result in a lot of data bloat. Default privacy rules are not stored. You need to use the proper CB APIs when retrieving fields and when retrieving users you need to check their privacy using API.
This will be changed in a future release where I'll be normalizing the privacy rule storage so it can more accurately be queried against, but for now you have to check a users field access before rendering them. The easiest way to do this is to call getFields API and if the field doesn't output then don't display that user. The getFields API is documented below.
www.joomlapolis.com/documentation/279-community-builder/tutorials/18361-obtaining-field-values-through-getfields-api
Alternatively since you know the default privacy rule if they don't have one in the database then just perform whatever SQL you need to based off knowing they're set to a specific privacy rule.