This document provides information on a range of topics that may need to be reviewed by stakeholders as part of the process of getting a departmental licence. If you have further questions, please don't hesitate to contact us by email.
How is Gorilla different from a Survey Tool. Read about Key Differences here.
The Business Case for Gorilla
Read the Business Case for Gorilla here.
Read Testimonials from clients here.
Online Timing Accuracy
When conducting research online, rather than in the lab, it's important to understand how timing accuracy changes.
The schematic below shows the main differences:
Modern techniques refers to the
Performance.now() function common in all major
browsers which provides microsecond timing. We do not have control
of the underlying operating system, so we cannot make the same OS-level timing calls that native software
can. While clearly there will always be some experiments that require extremely high fidelity timing, the
precision offered by Gorilla is appropriate for a wide range of research.
The latency between the cloud storage and local computer is irrelevant because Gorilla downloads all task information (i.e. stimuli) to the local machine in advance and collects local timestamps.
This article, Woods et al., 2016, is an excellent summary of the strength and weakness of online research.
This article, Hilbig, 2015, presents the effect of lab- versus web-based research on reaction times.
A detailed technical overview of the timing techniques employed in Gorilla is located here.
Anonymity and Ethics
In compliance with BPS (The British Psychological Society) requirements, identifying data, demographic information and performance data are all stored separately. They are downloaded separately from the metrics tab and joined together outside Gorilla using the Private IDs provided.
Our database architecture supports double-blind studies; you can join demographic data with performance data while remaining blinded.
If using Gorilla in conjuction with a third party recruitment service, it may be that you do not collect any identifying data.
GDPR: General Data Protection Regulation
Gorilla is fully compliant with GDPR.
Gorilla is built around the existing BPS (The British Psychological Society) and NIHR (National Institute for Health Research) standards which were far more stringent than the Data Protection Act. Moreover, GDPR does not apply to data that “does not relate to an identified or identifiable natural person or to data rendered anonymous in such a way that the data subject is no longer identifiable.” The majority of our recruitment policies anonymise participants.
Gorilla is made, owned and sold by Cauldron Science Ltd (Cauldron).
Cauldron is incorporated in England and Wales under company number 07071678. Our VAT number is GB996693829.
Our registered office is 2 Old Bath Road, Newbury, Berks, RG14 1QL and our business address is St John's Innovation Centre, Cowley Road, Cambridge, CB4 0WS.
Our Terms and Conditions can be found here.
Data Protection and Security
Gorilla is fully compliant with data protection and security policies.
The Code Editor
Go here for more information about the code editor.
We have a seat licensing model. Each person signs up with their own email address and effectively has their own account. Each user then has complete control over any task, questionnaire, experiment and associated data that they have authored. This model fits with BPS (The British Psychological Society) requirements around data security; data is only accessible by the person that owns the experiment or those that they are collaborating with.
Users can also collaborate on projects. When sharing projects the level of access (read, write, admin) can also be set.
We don't currently have the idea of student accounts and supervisors. Any account holder is able to publish their experiments and the onus is on them to ensure they have done so in compliance with their institutions ethics and code of conduct.
What happens when my licence expires?
When your licence expires, your account will revert to a Pay-per-Participant account. All you data, task, questionnaires and experiments will be maintained. You will still have access to all the editing tools and the previewing tools. You just won't be able to collect more data without first purchasing pay-per-participant tokens.
Gorilla is an ideal environment for teaching Research Methods, as students can get valuable experience in operationalising experiments, collecting data, and analysing the data collected.
The Experiment Tree makes the experimental design clear, which can often help students understand whether their experiment is adequately controlled.
We have a suite of tools that allow teachers to manage classrooms. These allow you to:
For Masters students who may not have the time or inclination to learn to code, Gorilla offers a user-friendly environment in which to author completely novel tasks.
Read our Case Studies about UCL's and Birkbeck's experiences here:
Microsoft Azure guarantees that our servers will be working 99.95% of the time. There are 525,600 minutes in a year. That 0.05% when our servers could be down - outside of our control - equates to ~263 minutes a year. This is equivalent to ~2 minutes a month or ~44 seconds a day. At scale, very rare events happen surprisingly often.
Microsoft Azure performs far above this threshold, nevertheless server downtime is a reality of internet research, and we want to give you the information you need to make an informed decision.
The risk to your experiment of server downtime will depend on your recruitment method and target participants.
On our side – as long as you haven’t included participants at the start node – no Gorilla fees would be due. If you are paying participants through a participant recruitment service, you may need to check their policy.
We're often asked to provide draft text for an ethics application.
We will use Gorilla (www.gorilla.sc) to collect data for our study. Gorilla is a cloud software platform specifically for the behavioural sciences.
Publications & Referencing
We also recommend stating the date window within which data was collected, so that someone reading the study could cross-references this with our release notes.
We used the Gorilla Experiment Builder (www.gorilla.sc) to create and host our study. Data was collected between 01 Jan 2017 and 15 Jan 2017.
44 Participants were testing online using Gorilla (gorilla.sc). Data was collected between 01 Jan 2017 and 15 Jan 2017.
A list of publications that cite Gorilla can be found here.
We also have the following interviews from ambitious researchers that have embraced online research methods.