What are Operation Siam’s safeguarding and data rules?

Operation Siam’s public standard is to collect less, explain purpose, separate public information from case information, restrict access, and provide a route for correction or complaint.

Core principles

Defined purpose

Know why information is needed, who will use it, and what decision or service it supports before collecting it.

Minimum necessary data

Do not collect a complete case file when a category, safe contact method, or limited fact will answer the immediate question.

Meaningful notice

Explain foreseeable use, access, sharing, retention, and risk in language the person can understand.

Restricted access

Separate public publishing, routine support, safeguarding review, finance, and sensitive case material according to role and need.

Accuracy and correction

Mark uncertainty, attribute external claims, record review dates, and provide a way to correct an error.

Do no harm

Decline publication or sharing when exposure is unnecessary, disproportionate, unsafe, or inconsistent with consent.

Public-information boundaries

  • No names, recognizable faces, exact locations, case numbers, or family links merely to demonstrate impact.
  • No partner name or logo without an appropriate written basis and authorization for the specific use.
  • No public allegation presented as a verified finding; identify the source and procedural status.
  • No publication of a child’s story or image without a specialized best-interests and safeguarding review.
  • No coercive consent tied to assistance, contribution, publicity, or access.

Reporting a concern

An initial report should identify the concern category—such as safeguarding, privacy, financial conduct, discrimination, retaliation, fraud, or inaccurate public information—and a safe response method. Do not attach sensitive evidence until a restricted channel and authorized reviewer are confirmed.

Before retaining information

  1. Confirm the legal and operational purpose.
  2. Remove fields that are not necessary.
  3. Set access and sharing limits.
  4. Set a review or deletion point.
  5. Document any exception and the person responsible for approving it.

Sources and further reading

  1. ICRC — Handbook on data protection in humanitarian action — Humanitarian data-protection principles and operational guidance.
  2. UNHCR Thailand — Complaints and reporting fraud — Official complaint and fraud-reporting context.

External links are provided for verification and further reading. A citation does not imply endorsement, partnership, or control by the cited institution.

Corrections: If this page is incomplete or inaccurate, contact info@deganation.org with the article title and the source supporting the correction. Do not email identity documents or sensitive case records.

  • 0 Users Found This Useful
  • complaints, consent, data protection, privacy, safeguarding
Was this answer helpful?

Powered by WHMCompleteSolution