Governance

PII Audit

Find sensitive data before it spreads.

Classify schema columns for PII and check whether queries or dbt models expose sensitive fields.

Catch privacy risk while the model is still being built.

The problem it solves

Sensitive data often enters analytics through ordinary columns: email, phone, IP address, name, address, or customer identifiers. Teams need to catch exposure early.

What it does

Classifies columns that may contain personally identifiable information.
Checks whether SQL or dbt models expose sensitive fields.
Reports categories and confidence.
Supports privacy and governance workflows.

When to use it

BEFORE

productionizing a model that touches customer data

WHEN

auditing a schema for sensitive columns

WHEN

checking whether a query exposes PII

DURING

GDPR, CCPA, HIPAA, or internal governance reviews

How it works

The skill scans column names, types, and query lineage to find columns likely to contain PII and flag where they're being used.

Tools used

altimate_core_classify_pii

Classify potential PII columns through Altimate Core.

altimate_core_query_pii

Check whether a query exposes potential PII.

schema_detect_pii

Scan warehouse metadata for columns that may contain personally identifiable information.

schema_inspect

Inspect a table's columns, types, nullability, and constraints.

Related skills

← All skills & tools