All Collections
Fixing issues
No privacy rules defined issue
No privacy rules defined issue

What is this issue and how to fix it?

Updated over a week ago

This issue is triggered when two conditions are met :

  1. Certain fields within this database may contain sensitive information.

  2. No privacy rules have been established to safeguard them.

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.


In order to fix this issue, please define some privacy rules for this data type.

If you consider this database as not sensitive, please update the field's sensitivity.

Did this answer your question?