Privacy & research ethics
Clear limits, data minimization, role-scoped access, and disclosure-safe reporting for an instrument still in development.
The national survey is closed and collects no participant responses.
The public questionnaire preview keeps temporary answers only in the current browser tab and discards them. It does not create a research submission. Do not enter identifying or sensitive real-world details.
The core survey does not request names, military identification numbers, Social Security numbers, DoD ID numbers, unit names, exact duty locations, or identifying allegations. Open questions instruct respondents not to supply names, classified information, identifying details, suicide methods, or graphic descriptions.
The survey is not described as anonymous. Any future protocol must explain the actual technical architecture, confidentiality safeguards, and their limits. No advertising trackers or third-party analytics are added to the survey experience, and unnecessary IP-address retention is avoided by design.
Final consent must explain the research purpose, voluntary participation, potential risks, expected completion time, data handling, confidentiality limits, research contact, withdrawal procedures, and applicable approvals. Withdrawal limits after de-identification or aggregation must be stated accurately.
No administrator role automatically receives unrestricted access to individual survey responses. The current implementation exposes no staff or public function for reading submissions or responses. Future access requires an approved protocol, least-privilege permissions, and auditable controls.
Individual responses are never publicly displayed. Public reporting requires an approved, disclosure-safe aggregate export. The database suppresses public access to aggregates with a sample size below ten and does not automatically publish unreviewed responses.
Before launch, the responsible institution must document retention periods, deletion procedures, storage protections, backup handling, and withdrawal limits. No survey response retention period is claimed while participation remains closed.
University applications contain institutional contact and project information. They are stored privately, reviewed only by authorized partnership roles, and retained for follow-up administration. They are not published as partnerships or endorsements.
Role-scoped staff access, server-side validation, private database policies, and audit records are implemented. A qualified security and privacy review is still required before production survey launch; technical controls alone are not research approval.
