Humanitarian Data Protection Adviser — Crisis Response Networks

The mandate

The board must decide how much beneficiary information a redesigned crisis-response network should collect and exchange when agencies, donors, host authorities and local partners have different purposes and protection thresholds. Current proposals join registration, cash assistance, case management and movement analytics through a common identity layer. The standing question is whether operational coordination benefits justify risks of exclusion, retaliation, forced disclosure or future reuse after a conflict changes hands.

The adviser contributes four days each month, joins the monthly Geneva protection forum and attends the scheduled Amman and Nairobi field reviews. A quarterly private session with the committee tests one high-consequence data decision without programme sponsors present. During a declared crisis escalation, the chair may request a written view within forty-eight hours, provided it concerns an established advisory question rather than day-to-day clearance.

The appointment runs for twelve months with no automatic renewal. If deployment is delayed by access or security restrictions, the committee may re-sequence one field review within the existing term; unused days do not roll into operational support. At month ten, the board decides whether management has internalised the decision framework and closes any residual question through a recorded owner rather than extending the adviser by default.

The adviser has no line authority and assumes no executive responsibility. Country directors decide operations, protection leaders own harm analysis and the Data Protection Officer retains statutory interpretation; no programme, processing, security, contracting, field-command or legal-opinion authority transfers. The adviser may challenge purpose, necessity, sharing conditions and reversibility, but cannot approve a dataset, instruct a partner, negotiate government access or suspend assistance to an affected population.

Potential conflicts include humanitarian agencies, institutional donors, digital-identity platforms, cash-transfer providers, analytics vendors, host governments and protection consultancies. Board roles, funded research, active bids, retainers and material advocacy positions relevant to the network must be declared. A direct engagement with a bidder or receiving authority during the term requires committee approval and may result in recusal from the affected question.

Why the board wants this voice

Beneficiary information can enable faster assistance while also becoming a durable map of vulnerability, affiliation and movement. Consent language alone cannot resolve dependency, power imbalance or the danger of future access by a hostile actor. Independent counsel gives directors a disciplined way to test necessity and reversibility before infrastructure choices harden across multiple agencies.

What you will own

• Challenge whether each proposed data element is necessary for assistance, protection, accountability or an explicitly bounded secondary purpose.
• Frame plausible harms from conflict shifts, compulsory access, partner compromise, identity error, exclusion and linkage across programme datasets.
• Test sharing designs for role separation, revocation, local-partner equity, retention, emergency access and evidence of actual use.
• Examine digital-identity choices through accessibility, duplicate resolution, contested identity, family relationships and safe alternatives for undocumented people.
• Advise on analytics boundaries where movement prediction, vulnerability scoring or fraud detection could change eligibility or physical safety.
• Review field evidence with affected communities and frontline teams, separating institutional convenience from genuine humanitarian necessity.
• Leave the board a decision ledger, unresolved ethical tensions, escalation triggers and indicators of disproportionate collection or coercive reuse.

Candidate qualifications

• Advised executive or governing bodies on data responsibility within humanitarian, refugee, public-health or conflict-affected operations.
• Can evidence a programme design materially narrowed after testing future misuse, exclusion or compelled-disclosure scenarios.
• Understands protection practice, data minimisation, digital identity, responsible analytics and the limits of consent under dependency.
• Has worked with local partners and affected communities without treating headquarters policy as sufficient field evidence.
• Navigated donor reporting, host-government demands and inter-agency coordination while preserving principled limits on information sharing.
• Maintained independence where commercial technology interests, advocacy positions and urgent operational narratives competed for influence.

Non-negotiables

• Will attend the Geneva, Amman and Nairobi sessions subject to agreed humanitarian security protocols.
• Holds no undisclosed role with a proposed identity, cash, analytics or information-sharing provider.
• Accepts no authority to approve processing, direct field teams, interpret law or suspend humanitarian assistance.
• Brings high-consequence field judgment, not only corporate privacy policy or regulatory compliance credentials.

1. 49 words maximum. Which beneficiary-data use did you oppose despite a credible operational benefit, and why?
2. 49 words maximum. How would you test whether a shared identity field could endanger someone after control of territory changes?
3. 49 words maximum. Which current donor, agency or technology relationship requires disclosure for this mandate?