From the moment a participant submits a response to the moment you download it for analysis — every step is encrypted and auditable.
Session → Transit → Storage → Export
Responses are collected trial by trial in the browser. On completion, one JSON record is assembled.
participant session
The record travels over TLS. No plaintext leaves the participant's device.
encrypted in transit
TLS · end-to-end
Records are AES-256 encrypted before writing to the database. Your key, your data.
encrypted at rest
Export the full dataset as CSV or JSON whenever you're ready. No lock-in.
export formats
lab.js sends partial (incremental) data to the server after each ~3-second pause in activity, and sends the complete dataset when the experiment ends. Only incremental saves that have a matching complete dataset are automatically removed — if the experiment never ends, you keep only the incremental data and may lose the final part of the session.
Encryption layers
Add a defined duration or a final screen that signals completion. In the lab.js builder preview, a download button slides in when the experiment ends — in Open Lab, participants are automatically redirected instead.
During a session, lab.js periodically sends partial uploads after ~3 seconds of user inactivity. At the end, it sends one complete dataset that covers the whole session.
By default, lab.js stores every variable and parameter. Prefix non-essential parameters with an underscore to exclude them from the stored dataset.