Home/Sensitive data handling
sensitive data handling

The hub does not receive raw cases.

This page is the contract. Raw worker chats, case files, IDs, contact details, and private documents stay on the worker device or trusted NGO hardware unless an authorized user creates a sanitized submission. Sensitive PII is anonymized by the local Gemma 4 workflow before anything is submitted; the server runs a second PII detector before storage or display.

CategoryStays localMay cross hubEnforcement
Worker case contentAlwaysNeverLocal Gemma 4 anonymization must happen before submission; server schemas reject raw case fields.
Worker names · IDs · contactsAlwaysNeverServer-side PII detector rejects identifier-shaped strings before storage.
Anonymized pattern_id (e.g. fee_request)Originates locallyYes. opt-inPer-turn opt-in. K-anon ≥ 30 floor or rejected.
Corridor / sector bucketsOriginates locallyYes. anonymized onlyAnonymized buckets only; no time-of-day precision.
Public-source URLsYes (intended)Reviewed by curators before publication.
Pack version + pull-timeYes (audit)For reproducibility of the audit log.
Outbound emails / reportsNever auto-sentNo automated outbound channel exists. Human signs every artifact.
Hard rule 01

No raw case intake.

The hub has no endpoint that accepts worker case content. None will be added.

Hard rule 02

No auto-reporting.

DueCare drafts; the user or trusted caseworker decides. The hub does not send messages on anyone's behalf.

Hard rule 03

No legal counsel.

DueCare is not a law firm, an emergency response service, or an official complaint authority. It cites public sources and routes to verified contacts.

Hard rule 04

Second server-side PII pass.

The server rejects raw-PII submissions before storage and redacts detector-class PII in admin/debug views.