Panel Recruitment and Respondent Data: Vetting Without Compromising Privacy¶

Recruiting real respondents you don't already have a relationship with raises a fair question: how do you know they're legitimate, and what happens to their information in the process? Panel Recruitment's vetting process and its privacy protections work together, not as a trade-off between the two.

Vetting Happens Before You See a Respondent¶

Every participant in the panel goes through the panel provider's own vetting process - dozens of quality checks - before they're even eligible to take your survey. This happens upstream, as part of maintaining the panel itself, not as something you configure or manage per survey. See Data Quality Safeguards in Panel Recruitment for more on what this protects against.

What You See vs. What the Panel Provider Sees¶

As a survey owner, you see the responses your survey collects, plus the screening criteria you defined for who's eligible to participate - you don't get a database of identifiable panel members to browse or contact directly. The panel provider maintains the actual respondent relationship and identity information; your access is scoped to running your study, not to the panel's membership itself.

Screening Criteria vs. Personal Data¶

Defining an audience (age range, country, employment status, and other filters) narrows who's eligible without handing you individually identifying information about who those people are before they respond - you're filtering the pool the panel draws from, not looking up individuals.

Why This Structure Protects Respondents¶

Keeping respondent identity and screening administration with the panel provider, separate from what survey owners can access directly, is a real privacy protection for the people participating - they're recruited into your study without their identity being exposed to every researcher who runs a wave, while you still get a properly vetted, targeted audience for your research.

FAQ¶

Can I see who specifically took my survey through Panel Recruitment?
You see the responses collected, not an identity lookup for individual panel respondents - the panel relationship and identity information stays with the provider.

Does vetting slow down how quickly I get responses?
Vetting happens as part of maintaining the panel itself, upstream of any specific wave - it isn't an extra step added to your wave's timeline.

What happens if I suspect a specific response is low quality despite vetting?
File a report from inside the wave - see Panel Recruitment FAQ for how this is handled. Vetting substantially reduces low-quality participation but isn't a guarantee against every individual case.

Is respondent data from Panel Recruitment stored differently from data collected through my own distribution link?
Response data is handled consistently regardless of how respondents reached your survey - see Data Privacy and Consent Management for the general approach.

For more on the quality safeguards themselves, see Data Quality Safeguards in Panel Recruitment.