Privacy dashboard

The Privacy dashboard offers a centralized view of your database’s PII protection status. This dashboard is available under the PII tab in the Table view tab and is designed to help you effortlessly monitor and manage sensitive data across all tables in your workspace.

The dashboard categorizes each column into one of three privacy statuses below.

Unprotected PII columns

These columns have been identified as containing sensitive PII data but have not yet been protected. They require further action to ensure compliance, such as assigning a generator (e.g., mocker) to de-identify or synthesize the data.

Confidence scores

Here you also can review PII scan confidence scores to help evaluate the likelihood that a column contains sensitive information. These scores are displayed next to the mockers thus showing the confidence of a mocker for that column.

Confidence threshold slider

The confidence threshold slider enables you to fine-tune the sensitivity of PII detection to align with your privacy policies. When you set a specific threshold value, the dashboard will display only the columns whose PII confidence scores meet or exceed this threshold. This makes it easier to quickly apply a suitable generator to protect high-confidence PII columns directly from the interface.

This is especially useful when working with large databases. By setting a threshold value, only columns with a score equal to or greater than that value will be displayed, thus helping you prioritize which columns require protection.

If you click on Show columns below PII scan acceptance threshold, you will also see columns that fall below your defined confidence level, allowing for manual review of lower-confidence results as needed.

Protected PII columns

These columns are already protected using Syntho’s de-identification generators. Examples include columns with mock data for birthplace, driving license and maiden names, or id column which will be hashed.

Non-PII columns

These are columns the system has classified as not containing PII. While no action is required for these, it’s good practice to periodically review them, especially when the data or schema evolves.