> For the complete documentation index, see [llms.txt](https://docs.pulselabs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulselabs.ai/settings/privacy-policy-compliance.md). # Privacy and Compliance ### How Pulse Labs protects research data Pulse Labs is built for research involving real people and their personal data. The platform implements security and compliance measures designed for this context. #### Encryption * **In transit** — All data is encrypted using TLS during transmission * **At rest** — Stored data (recordings, responses, participant information) is encrypted on the server side * **Access-controlled** — Data access follows the role-based permission model (Admin, Editor, Viewer) at the project level #### Access controls * Every project starts as **Hidden** — data is only accessible to the creator until explicitly shared * Role-based permissions limit what each team member can see and do * Participants can only access the specific capture methods they've been assigned to * Audit trails track data access and modifications ### Participant privacy #### Consent Pulse Labs supports structured consent management for participants: * **Terms acceptance** — Participants agree to platform terms during sign-up * **Study-specific consent** — Participants complete the Document Signature verification step to sign consent forms, NDAs, or IRB-approved participation agreements before they access your study * **Opt-in participation** — Participants choose to join studies and can decline or withdraw #### Participant data Participant data collected through the platform includes: * **Profile information** — Name, email, demographics (provided during sign-up) * **Verification data** — Screener survey responses, location checks, ID verification results, signed documents * **Research data** — Survey responses, evaluation task submissions All participant data is scoped to the project it was collected in. Team members can only access participant data for projects they've been added to, at the permission level of their assigned role. #### Participant rights Participants can: * See which studies they're enrolled in * View their own verification status * Decline invitations * Access their data through the participant portal ### Regulatory compliance The platform is designed to support compliance with common regulatory frameworks:
FrameworkHow Pulse Labs Supports It
GDPRConsent management, data minimization, participant access rights, data deletion capabilities
CCPAParticipant rights to know, delete, and opt-out; non-discrimination protections
HIPAAAvailable upon special request for healthcare research contexts with appropriate data handling controls.
#### Data retention * Research data is retained for the duration of the project * Archived projects preserve data but stop new collection * Data deletion can be requested through administrative channels #### Bring Your Own Participants (BYOP) Within a project you have the ability to invite your own panelists by their emails. These panelists will still sign in and create Pulse Voices accounts * **Limited Profile information** — Skip demographics, only capture name, email, and location. * **Blocked from seeing other studies** — In addition to not receiving emails, the ‘explore’ section of their app is disabled until the end of the BYOP study * **Blocked from marketing emails** — These panelists are marked as do-not-market unless they proactively seek to join other studies which they are blocked from doing until the end of the BYOP study * **Active opt-in post study** — Upon closure of the project for which they were originally recruited, BYO Participants may, at their next platform sign in, voluntarily opt-in to the Platform's general research panel to access future study opportunities. In the unlikely scenario where a participant currently active in a BYOP project is added to another project, this is permitted. From within the Pulse Voices portal, they do not have the opportunity to join the Pulse Voices general projects until after the original BYOP project has ended. However, if a participant navigates to an externally launched Pulse Voices screener independently, they are permitted to sign up as a Pulse Voices participant. If a panelist is already a Pulse Voices member when they are added to a BYOP project, the researcher adding them is informed of this. They may still be added to the project, but that participant will continue to see marketing emails if they have opted in to those, and will be able to see other projects in the explore tab of their app. ### For your IRB or legal team If your institutional review board or legal team needs to evaluate Pulse Labs for compliance: * **Consent workflows** are configurable per study, including document signature requirements * **Data access** is role-based and auditable * **Recording storage** uses encrypted cloud infrastructure * **Data export** is available for external analysis in approved environments ### Best practices * **Enable consent forms** for any study involving sensitive topics or data * **Use the minimum verification steps necessary** — only collect what you need * **Review team access** periodically — remove people who no longer need access to a project * **Use Hidden visibility** for projects involving confidential or proprietary research * **Document your data handling approach** as part of your study design, especially for regulated industries --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pulselabs.ai/settings/privacy-policy-compliance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.