This issue is fired when two conditions are met:
A database contains at least one sensitive field
The "Everyone else" privacy rule for this database allows to "See all fields"
The fields are defined as sensitive whether by our prediction model or by yourself when you manually reviewed the field's sensitivity.
In order to get more accurate results, we recommend reviewing manually the field's sensitivity. You can find some help in this article.
Solution
In order to fix this issue, please uncheck the "View all fields" checkbox from the "Everyone else" privacy rule. If you think this is normal, you can ignore this issue.
This checkbox has to be unchecked.