# Ethics, consent and data protection: template

A starting point for an ethics application and a data management plan for the three studies. It is **not legal
advice**. Before collecting real data: get approval from a research ethics committee (a university partner's, or an
independent one), and have the consent text and this plan checked by that committee or a data-protection officer.
Nothing here replaces their judgement.

## 1. What the kit does by default (privacy by design)

| Topic | Default |
|---|---|
| Identity | A random participant code (e.g. `K7P-3QX`). No name, e-mail, phone, IP address, location, photo, voice or camera image is collected. |
| Background questions | Age band, gender (with "prefer not to say" and self-description), VR and gaming experience, normal or corrected vision. Bands, not exact values. |
| Device | Browser family and version, operating system family, touch or not, screen and window size, pixel ratio, frame-rate statistics. **No full user-agent string** and no fingerprinting. |
| AR camera | Never recorded or sent. Only the floor height from a hit test is used. |
| Storage | In the participant's browser (localStorage) and as a downloaded file. Nothing is sent anywhere unless the researcher configures an upload address. |
| Withdrawal | During the session: a Stop button (or B/Y in a headset) offers "keep my answers" or "delete my data"; delete removes everything, including the browser copy. Afterwards: by sending the participant code, until the date set in the consent text. |
| Free text | Only one optional question (Study 2), with a warning not to write anything identifying. |
| Test data | Sessions opened with `?test=1` or in an emulated headset are flagged and left out by the merge tool. |

## 2. Is the data personal data under the GDPR?

- **With the default random code and no list linking codes to people**, the researcher cannot identify anyone, so the
  data set is close to anonymous. But the participant holds their code (to withdraw), and small groups with rare
  background answers could be singled out. Treat the data as **pseudonymous personal data** while it is being collected
  and analysed, and publish only after checking that no combination of background answers singles anyone out (for
  example, merge age bands with fewer than five people).
- **A recruitment-platform ID** passed in the link (`?pid=` from Prolific, SONA, a class list) is pseudonymous personal
  data: the platform can link it to a person. Use it only if payment or credit needs it, say so in the consent text,
  and replace it with a random code before sharing the data.
- **Sickness ratings (SSQ, FMS) are momentary health information.** Ask the committee whether they count as health
  data (GDPR Article 9) in your setting. The consent screen asks for explicit agreement, which covers Article 9(2)(a)
  if needed; a university may instead rely on scientific research (Article 9(2)(j)) with safeguards.
- **Legal basis:** universities usually use "task in the public interest" (Article 6(1)(e)) for research, with consent
  as the ethical (not the legal) basis; a company usually uses consent (Article 6(1)(a)) or legitimate interest. The
  committee or data-protection officer decides.

## 3. Consent

Each study has a `consent.html` with the information sheet. Before use:

1. Fill in every `[bracket]`: who runs the study, contact, ethics approval reference, where data is stored, for how
   long, until when withdrawal is possible, complaint contacts (including the national data-protection authority; in
   Greece the Hellenic Data Protection Authority, dpa.gr).
2. Change `data-consent-version` whenever the text changes: the version is saved with every response.
3. Keep the participant rights: voluntary, stop at any time without a reason, choose keep or delete, withdraw later with
   the code.
4. Participants must be **18 or older** (the checkbox says so). Studies with minors need parental consent and child
   assent, a different form, and usually a stricter review: do not adapt these templates for children without that.

## 4. Safety

- **Comfort Ride is designed to cause some motion sickness.** Exclusion criteria are in its consent text (epilepsy or
  seizures, pregnancy, heart conditions, balance or inner-ear disorders, screen- or motion-triggered migraine, alcohol
  or drugs, feeling unwell). The ride stops itself at FMS 15 or above; participants stay seated; the end screen asks
  them to rest and not to drive or cycle until symptoms have gone. In a lab: a chair without wheels, a researcher in the
  room, water, a bucket, and a 15-minute rest before leaving. Consider a stricter FMS stop for remote participants.
- **Headsets:** clear space around the participant, clean face pads between people, no one walks while wearing one.
- **AR:** the participant must not walk while looking at the phone (Study 2 tells them to stand still).
- **Photosensitive epilepsy:** none of the scenes flash, but say so in the information sheet only if a review confirms it.

## 5. Data management plan (fill in)

- **Collection:** [lab machine / participants' own devices]. Files reach the researcher by [download handed over /
  e-mail / upload endpoint run by the institution]. If an upload endpoint is used, it must be run or approved by the
  institution (e.g. a university server, or an institutional Google Workspace with a data-processing agreement), and the
  consent text must name it.
- **Storage:** [encrypted laptop / institutional drive], access limited to [names or roles]. Lab machines: download
  sessions daily with `research/tools/sessions.html`, then remove them from the browser.
- **Retention:** raw files kept for [e.g. 5 years after publication, or the institution's rule], then deleted.
- **Sharing:** an anonymised data set (codes replaced, rare categories merged, free text checked) on [OSF / Zenodo]
  under [CC BY 4.0], with this code and the study protocol.
- **Withdrawal requests:** delete the participant's files and rows from every copy; record the date (not the reason).
- **Breaches:** report to [data-protection officer] within 24 hours.

## 6. Ethics application checklist

- [ ] Research question, hypotheses and analysis plan written and preregistered (OSF or aspredicted.org).
- [ ] Sample size justified (TOPICS.md gives starting points).
- [ ] Information sheet and consent (`consent.html`) completed and approved.
- [ ] Recruitment text and any payment or course credit described.
- [ ] Risks and how they are handled (section 4), including what happens if someone feels unwell remotely.
- [ ] Data management plan (section 5) approved.
- [ ] Pilot with 3 to 5 people; protocol frozen before the real study.
- [ ] Test links (`?test=1`) not used for real participants; the hosted copy is the approved version.
