Privacy.

Before promising confidentiality, map eligibility information, participation records, and selections. The privacy guide explains why limiting a public report is different from preventing administrators from linking a member with a choice. Use the service-selection questions to investigate the actual implementation, including exports, replacement invitations, support access, and the limitations of any stated separation. Do not treat an unfamiliar security label as a complete answer.

Privacy also intersects with accessibility and result reporting. Assistance should explain the task without unnecessarily collecting private selections, while a review package should retain appropriate evidence without duplicating sensitive content everywhere. Read the relevant articles together before deciding what to put in the invitation’s privacy explanation. The goal is a statement members can understand and the organizer can substantiate across the full workflow, not a broad promise copied from another service.