Marking personal data and erasing it
Indacas only knows which data is personal because you tell it. Marking fields and questions decides what is hidden from tables, exports and analysis, what an erasure removes, and what your DPIA lists.
Mark the fields in your data dictionary
Each field in the data dictionary has two flags. Tick whichever actually applies. A field can be one, both or neither.
Direct identifier. A value that points at one person on its own, such as a name, email, phone number, address, date of birth or NHS number.
- Restricted from record tables, exports and analysis.
- This is what an erasure removes.
Special category data. Health, genetics, biometrics, ethnicity, religion, politics, trade union membership, sex life or sexual orientation. These need an Article 9 condition.
- Left out of record tables and exports unless a project owner or admin explicitly includes them.
- Analysis shows counts only.
- Listed as special category data in the project’s DPIA.
A name is a direct identifier but not special category data. A diagnosis is special category data but not a direct identifier on its own.
Mark the questions in your surveys
In the survey builder, open a question’s settings:
- Turn on Identifies the respondent when the answer points at the person, such as a name, email, phone number or address. Erasing a participant’s personal data removes answers to questions marked this way and leaves the rest of the response intact.
- Turn on Special category when the answer is about ethnicity, religion, sexual orientation, gender identity, health or similar. It is left out of exports unless you include sensitive data, analysis shows only how many people answered, and results are never compared by it.
Questions in the Indacas templates come marked already. The equality monitoring, PHQ-9 and GAD-7 questions are special category.
Showing sensitive data in analysis
Project owners and admins can choose Show sensitive data on a survey’s analysis, when comparing records, and on Record data. Answers and values marked as special category or identifying then show in full until they choose Hide sensitive data. Each time it is turned on, the project’s activity log records who did it and on which page.
Erase a participant’s personal data
When someone asks for their personal data to be removed, open their record and find Erasure requests. Project owners and admins can see it.
Erase personal data blanks every value on the record held in a field marked as a direct identifier. Research data, dates and outcomes are untouched, and the record and its responses stay.
- Include their survey answers also erases answers to questions marked as personal data, in every response attached to the record. It is on by default. Leave it on unless you have a reason to erase the record alone.
- Type ERASE to confirm. This cannot be undone.
- Consent records are kept as evidence that the project was allowed to collect the data, with the signature removed.
- The erasure is written to the project’s audit log.
If no fields are marked as direct identifiers, erasing changes nothing on the record. Mark them first.
Delete a record instead
Deleting a record keeps nothing at all. It is only available once the participant has left the project, for example by withdrawing. Like erasure, it is written to the audit log.
Choose erasure when you are allowed to keep the research data, and deletion when nothing may be kept. Your ethics approval and your participant privacy notice should say which applies.