Privacy and Anonymity in Research Surveys

Privacy and anonymity should be considered before data collection begins. Academic research surveys often need to balance respondent trust, recruitment needs, link tracking, incentives, longitudinal follow-up, and analysis requirements.

1. Step 1: Review Block Builder. Identify any questions that directly collect names, emails, identifiers, precise locations, or sensitive demographics.

   Step 1: Review Block Builder

   Block Builder: Question Type

   Use the question type selector to switch between multiple choice, slider, grid, ranking, and more.

   Multiple Choice

   Required

   Page Break

   Question text

   Multi-select

   Options

   Add QuestionPull Questions

   Closing text

   Example only.

   Redirect (optional)

2. Step 2: Check the link strategy. Open Deploy and decide whether the study should use a public link or personal links with respondent-level tracking.

   Step 2: Check link strategy

   Block Builder

   Flow

   Preview

   Deploy

   Export

   Deploy

   Configure publishing, links, quotas, and theme from the Deploy tab.

3. Step 3: Preview consent language. Use Preview to confirm the consent block accurately explains confidentiality, anonymity, and data handling.

   Step 3: Preview consent language

   Block Builder

   Flow

   Preview

   Deploy

   Export

   Preview

   Walk through respondent-facing behavior in the same preview surface.

4. Step 4: Export a test response. Open Export and identify which fields are identifiers, indirect identifiers, demographics, and outcomes.

   Step 4: Export a test response

   Block Builder

   Flow

   Preview

   Deploy

   Export

   Export

   Download analysis-ready response data from the Export tab.

5. Step 5: Document access rules. Record who may download exports and how sensitive fields should be stored or removed.

   Step 5: Document access rules

   Top Navigation

   This is the same navigation component used in the app shell.

• Minimize identifiers: collect only the names, emails, ids, IP-adjacent details, or contact fields the study actually needs.
• Use broader categories: prefer ranges or regions when exact age, location, income, institution, or job title is unnecessary.
• Write accurate consent language: do not promise anonymity if links, tokens, incentives, or exports can identify respondents.
• Choose links deliberately: use public or personal links based on whether respondent-level tracking is required.
• Review exports before launch: identify sensitive fields before participants submit real data.

Personal links can support invitations, tracking tokens, or longitudinal workflows, but they may reduce anonymity depending on how they are used. Decide whether your protocol requires identifiable links or whether a public link is sufficient.

• Use personal links when: each respondent needs a unique invitation, a follow-up wave, or a one-response tracking workflow.
• Use public links when: broad anonymous collection is acceptable and respondent-level tracking is not part of the protocol.
• Separate incentives when possible: avoid storing payment contact information in the same export as sensitive outcomes unless the study requires it.
• Document token meaning: analysts should know whether a token is random, panel-provided, personally identifying, or linked to outside records.

Document which exported fields are identifiers, indirect identifiers, demographics, or research outcomes. Keep sensitive exports controlled according to your study protocol and institutional expectations.

When creating an analytic dataset, consider keeping a raw restricted export, a de-identified working export, and a cleaning log that explains which fields were removed or generalized. For response review, see Review and Clean Survey Responses.

• Consent and Screening in Research Surveys
• Survey Participant Links
• Demographic Survey Questions
• Export Research Survey Responses