01Scope under review
Information participants may provide
BuilderStudy’s research experience may ask participants to provide information such as:
- Contact details, including a name, email address, or other details used to follow up or support verification.
- Home, builder, community, property, buying, warranty, or HOA context relevant to a participant’s experience.
- Survey selections, ratings, written narratives, and optional supporting material if an upload feature is offered.
- Permissions or preferences about follow-up, quotation, moderation, and possible public use.
The final notice still needs to confirm the exact fields collected, which fields are optional, and what information the selected platforms generate automatically.
02Purpose review
Potential intended uses
Subject to review, participant information may be used to operate the research experience, organize responses, evaluate response quality, prevent misuse, communicate about a submission, moderate narratives, and develop eligible community-level or builder-related insight.
Any future use for outreach, research invitations, product improvement, or another purpose should be assessed and described before a final notice is published.
03Design principle
Private working layer vs. public insight layer
The planned model distinguishes information used privately to administer and review submissions from information that might become part of a public research output.
Private working layer
May include contact or verification details, full responses, submission context, supporting material, and moderation notes. Access roles and safeguards remain to be confirmed.
Public insight layer
Is intended to focus on eligible aggregates, summaries, and moderated excerpts where appropriate permission and reporting rules have been satisfied. Exact standards remain under review.
This separation is a planning principle, not a guarantee of anonymity or a finalized description of technical controls.
04Due diligence pending
Platform and vendor processing
BuilderStudy is reviewing which website, survey, hosting, communications, analytics, security, and storage providers may process participant information on its behalf.
The final notice should describe the relevant provider categories, processing purposes, data locations or transfers where applicable, contractual protections, and any participant-facing choices. Those details have not been finalized.
05Processes to be defined
Retention, access, correction, and withdrawal
- Retention: schedules, deletion triggers, backup handling, and different retention periods by information type are TBD.TBD
- Access and correction: the request channel, identity-check process, response timing, and available exceptions are TBD.TBD
- Withdrawal: the method, timing, and effect of withdrawing a submission or permission—including how prior aggregate outputs would be handled—are TBD.TBD
Any rights available under applicable law, and the way a participant may exercise them, require legal review and should be set out in the final notice.
06Publication blocker
Privacy contact details
A dedicated privacy contact, mailing details, request intake method, and escalation process are still TBD. No privacy request should be directed through this placeholder as though it were an active request channel.
Before publication: add verified contact details, confirm who monitors the channel, and document how requests are acknowledged, assessed, and completed.