What this capability changes
Connector states prevent unreviewed scrapers from entering production. Raw and normalised datasets keep separate retention rules.
Build source approval, privacy, suppression and human review into the product rather than adding them later. The design starts with a commercial question and preserves the trail back to the authoritative record, instead of forcing a team to trust a relevance label it cannot inspect.
How it works in the platform
Company outreach requires purpose limitation, source provenance, recipient rules, suppression and a human decision.
Source identity, observation time, transformations and user decisions remain separate fields. That distinction allows the product to update a notice without erasing what a user saw when a pursuit decision was made.
Production controls
The package includes a DPIA starter, data inventory, retention matrix and incident workflow for adaptation by qualified advisers.
Deployment begins with a source register, access roles, retention rules and measurable acceptance criteria. Features that depend on customer systems or third-party rights remain disabled until those dependencies are approved.