use-case-triage

A DPIA is mandatory when GDPR assessment triggers are met, such as large-scale behavioral tracking, whereas a PIA is required for broader privacy risks. Triage classifies your activity into PROCEED, PIA REQUIRED, DPIA MANDATORY, or STOP by evaluating regulatory triggers and policy conflicts.

Run a privacy triage by describing the new feature, data types, purposes, data subjects, and any vendor involvement. The workflow evaluates house triggers, mandatory assessment criteria, and privacy policy commitments to classify the activity and route it to PIA generation if needed.

Check for purpose limitation, data retention limits, selling/sharing rules, new data categories, and consent coverage gaps. Triage detects these privacy policy conflicts early to prevent launch blocks and identifies whether the proposed activity should proceed or stop.

Yes, privacy triage works for vendor relationships and behavioral data use. It evaluates the proposed processing activity against applicable regulatory footprints and privacy commitments, then returns a structured classification with reasoning and explicit handoffs if an assessment is required.

You can skip a PIA only if triage returns PROCEED after evaluating house triggers and regulatory criteria. If mandatory assessment triggers or privacy policy conflicts are detected, the workflow routes you to PIA or DPIA generation before the activity can safely launch.

A STOP classification means the processing activity violates privacy policy commitments or mandatory regulatory triggers. Triage provides structured reasoning and conflict identification, such as purpose limitation or consent gaps, preventing the activity from proceeding until the issues are resolved.