UK GDPR FOR RESEARCH

Research surveys built around UK GDPR, hosted in London

Your project data stays in the UK. You decide what is collected and why, and Indacas gives you the tools a controller needs: marked identifiers, erasure on request, versioned consent and the documents your review asks for.

Start building for free
  • Stored in London
  • Encrypted in transit and at rest
  • Audit log nobody can edit
  • Two-factor sign-in you can require

What a reviewer asks, and where Indacas answers

The questions ethics committees, information governance teams and data protection officers usually ask about a data collection platform.
The reviewer asksIndacas
Where is the data stored?In ISO 27001 certified data centres in London, encrypted in transit and at rest. More
Who is the controller?You or your institution. Indacas processes project data on your instructions. More
How is consent recorded?Against the exact published version each person saw, with the time they accepted. More
Can personal data be erased on request?Yes. Direct identifiers are blanked, the research data is kept, and the erasure is logged. More
Who can see and export the data?Only people on the project, by role. Special category data is only exported when an owner or admin includes it. More
Is access recorded?Every view, change and export is in the audit log, with who, when and the IP address. More
Is there a DPIA?One is generated from the study, following the ICO’s template, for your team to complete. More

Documents made from your project

Word or PDF Data protection impact assessment Follows the ICO's template, with the blanks your team completes marked in red.
Word or PDF Participant privacy notice Filled in from the project, ready to finish and show participants.
PDF Information security summary Hosting, encryption, access control and audit, on one page.
PDF Data management facts What is collected, where it is stored, who can reach it and for how long.

Know what personal data you hold

Every field in your data dictionary says whether it is a direct identifier or special category data, and those fields are kept out of tables, exports and analysis by default.
  • Special category data is only exported when an owner or admin includes it
  • Generated IDs let your team work without names
  • Erasure clears direct identifiers and keeps the research data
The data dictionary

Consent people can see and change

Participants consent to a versioned statement before anything is collected, and can see what the project holds about them.
  • Every acceptance is recorded against the exact version they saw
  • Participants can withdraw from their own dashboard at any time
  • Withdrawal stops automatic surveys to them
GDPR and your rights

Show your working

Everything a data protection or ethics review asks about, recorded as you work.
  • An audit trail of who viewed, changed or exported data, which nobody can edit
  • Roles that limit who can see and export what, and two-factor sign-in you can require
  • A DPIA following the ICO’s template, and a participant privacy notice, both prefilled
Project documents and the DPIA

Popular features

Help centre

Common questions

Something else? Ask us or browse the help centre.
Who is the controller?
You, or your institution, are the controller for your project data, and Indacas processes it on your instructions. Indacas is the controller only for account data such as your sign-in details.
Does any data leave the UK?
Project data is stored in London. Some of our service providers are based outside the UK, and our subprocessor list sets out what each one handles and the safeguards in place.
Can participants ask to see their data?
Yes. Each participant has a dashboard showing what the project holds about them, and can update their details or withdraw there.

Build your project for free, hosted in the UK.

Build for free, pay when you go live. Set the whole project up for free. When you go live, pay monthly or yearly, by card or by invoice. Academic and non-profit research gets a discount. See other use cases