Have fixed the CB Privacy issue in latest build. It was due to __minval and __maxval not triggering the check for the fields privacy as it was looking for exact name. As for your second issue it's more of a usability problem. The user should be selecting "Between 30 and 31" not "Between 30 and 30" since you're selecting a range. I however have noted in the bug ticket to change this to treat "Between 30 and 30" like "Between 30 and 31" so it'll give expected results.