Research responsibility

A checkbox is not a consent system.

Short answer: the field lab displays exactly the participant information and optional acknowledgement a researcher writes. It cannot determine whether the information is complete, lawful, understood, voluntary, current, appropriate to the audience, or approved by an organization.

What a study-specific information process may need to cover

Requirements depend on jurisdiction, organization, audience, topic, and research context. Government service-design guidance identifies topics such as purpose, data collected, use, sharing, voluntariness, withdrawal, retention, rights, controller/processors, observers, and recording. Use your organization's approved process and professional/legal review where needed.

What the app records

A response can record whether the researcher-authored acknowledgement was checked. That is one technical fact about the interaction. It is not a signature, identity proof, versioned consent-management record, capacity assessment, ethics approval, or proof of informed consent.

Session codes

Use a short code that does not directly identify the participant. Do not use names, emails, phone numbers, employee/student numbers, patient identifiers, or combinations that expose identity. Even a random code can be personal data if a researcher keeps a lookup table. Secure or avoid that lookup, define access, and apply the approved deletion schedule.

Comments and notes

The participant file asks people not to enter names or contact details. Free text can still contain identifying or sensitive information. Researcher notes, file names, emails, chat messages, and transfer systems can add more. Avoid unnecessary identifying details and follow the same access, retention, withdrawal, and deletion process across every copy.

Withdrawal in a file-based workflow

The app has no central participant directory or remote deletion endpoint. Your external process must explain how someone can request withdrawal, what code or evidence is needed to locate their response, the deadline after which aggregation may prevent removal, and who handles the request. Test that process before recruitment.

Minimize the study

Collect only grouping evidence needed for the research question.
Do not ask for demographics or sensitive attributes in this tool.
Do not include clinical, employment, education, safeguarding, or payment records.
Avoid recordings; the product does not create or manage them.
Keep approved information and retention records beside the study files.
Delete or archive according to the external approved process, not browser convenience.

Not legal or ethics advice: this page describes the product boundary. It does not determine your lawful basis, consent standard, ethics obligations, controller/processor roles, notice content, accessibility duty, retention period, international transfers, or incident response.