LogoLogo
Go to Syntho.AI
English
English
  • Welcome to Syntho
  • Overview
    • Get started
      • Syntho bootcamp
        • 1. What is Syntho?
        • 2. Introduction data anonymization
        • 3. Connectors & workspace creation
        • 4. PII scan
        • 5. Generators
          • Mockers
          • Maskers
          • AI synthesize
          • Calculated columns
          • Free text de-identification
        • 6. Referential integrity & foreign keys
        • 7. Workspace synchronization & validation
        • 8. Workspace & user management
        • 9. Large workloads​
        • 10. Data pre-processing
        • 11. Continuous Success
      • Prerequisites
      • Sample datasets
      • Introduction to data generators
    • Frequently asked questions
  • Setup Workspaces
    • View workspaces
    • Create a workspace
      • Connect to a database
        • PostgreSQL
        • MySQL / MariaDB
        • Oracle
        • Microsoft SQL Server
        • DB2
        • Databricks
          • Importing Data into Databricks
        • Hive
        • SAP Sybase
        • Azure Data Lake Storage (ADLS)
        • Amazon Simple Storage Service (S3)
      • Workspace modes
    • Edit a workspace
    • Duplicate a workspace
    • Transfer workspace ownership
    • Share a workspace
    • Delete a workspace
    • Workspace default settings
  • Configure a Data Generation Job
    • Configure table settings
    • Configure column settings
      • AI synthesize
        • Sequence model
          • Prepare your sequence data
        • QA report
        • Additional privacy controls
        • Cross-table relationships limitations
      • Mockers
        • Text
          • Supported languages
        • Numeric (integer)
        • Numeric (decimal)
        • Datetime
        • Other
      • Mask
        • Text
        • Numeric (integer)
        • Numeric (decimal)
        • Datetime
        • UUID
      • Duplicate
      • Exclude
      • Consistent mapping
      • Calculated columns
      • Key generators
        • Differences between key generators
      • JSON de-identification
    • Manage personally identifiable information (PII)
      • Privacy dashboard
      • Discover and de-identify PII columns
        • Identify PII columns manually
        • Automatic PII discovery with PII scanner
      • Remove columns from PII list
      • Automatic PII discovery and de-identification in free text columns
      • Supported PII & PHI entities
    • Manage foreign keys
      • Foreign key inheritance
      • Add virtual foreign keys
        • Add virtual foreign keys
        • Use foreign key scanner
        • Import foreign keys via JSON
        • Export foreign keys via JSON
      • Delete foreign keys
    • Validate and Synchronize workspace
    • View and adjust generation settings
  • Deploy Syntho
    • Introduction
      • Syntho architecture
      • Requirements
        • Requirements for Docker deployments
        • Requirements for Kubernetes deployments
      • Access Docker images
        • Online
        • Offline
    • Deploy Syntho using Docker
      • Preparations
      • Deploy using Docker Compose
      • Run the application
      • Manually saving logs
      • Updating the application
    • Deploy Syntho using Kubernetes
      • Preparations
      • Deploy Ray using Helm
        • Upgrading Ray CRDs
        • Troubleshooting
      • Deploy Syntho using Helm
      • Validate the deployment
      • Troubleshooting
      • Saving logs
      • Upgrading the applications
    • Manage users and access
      • Single Sign-On (SSO) in Azure
      • Manage admin users
      • Manage non-admin users
    • Logs and monitoring
      • Does Syntho collect any data?
      • Temporary data storage by application
  • Syntho API
    • Syntho REST API
Powered by GitBook
On this page
  • Unprotected PII columns
  • Protected PII columns
  • Non-PII columns

Was this helpful?

  1. Configure a Data Generation Job
  2. Manage personally identifiable information (PII)

Privacy dashboard

PreviousManage personally identifiable information (PII)NextDiscover and de-identify PII columns

Last updated 14 days ago

Was this helpful?

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.

Unprotected PII columns
PII scan acceptance threshold
Protected PII columns
Non-PII columns