Hands archiving pseudonymized transcripts while obsolete drafts are destroyed
Unique faceless editorial photograph created for this research workflow.
01 / PRIVACY QUESTION

Anchor retirement to approvals

Use the protocol, IRB/institutional requirements, consent commitments, funder policy and applicable law to define review dates.

Define disposal milestones and avoid presenting vault deletion as guaranteed media sanitization

Practical scenario

A project closes, but interview material has spread into analysis folders, exports, transcription-service downloads, email attachments and backups. Deleting the main archive would leave several uncontrolled derivatives behind.

02 / WORKFLOW CONTROL

Retire every derivative

Check exports, analysis copies, email attachments, transcription-service downloads and backups; deletion from one vault is not complete sanitization.

  1. 01Identify the authority that sets each retention period.
  2. 02Map every known derivative and service location.
  3. 03Place a review date and accountable owner on each record class.
  4. 04Suspend routine deletion when a lawful hold or approved research need applies.
  5. 05Document verified deletion or approved long-term transfer for every location.
03 / DECISION RECORD

Leave evidence another custodian can follow

Maintain a disposition register containing record class, authority, location, owner, trigger date, decision and verification. Do not use the register as a substitute for the institution’s official records process.

Pause and review when

  • The retention rule is described only as keep indefinitely.
  • Former team members still control project copies.
  • Backups and third-party downloads are omitted from the retirement plan.
04 / TECHNICAL BOUNDARY

Encryption does not decide permitted research use

Does not replace provider permissions, guaranteed backup, password recovery or enterprise identity management. Pseudonymized data can remain sensitive, especially when indirect identifiers or a usable code key exist. Technical protection must sit inside the approved research workflow rather than replace it.

Document the decisionRecord the data state, approved roles, participant code convention, storage location, recovery owner and review date without copying identifiers into the log.
05 / COMMON QUESTIONS

Questions to resolve before acting

Is project completion the automatic deletion date?

Not necessarily. Protocol, consent, institutional, funder and legal requirements may set different periods or conditions.

Is deleting the encrypted vault sufficient?

Only if all approved copies and derivatives are accounted for. Review exports, local devices, services and backups under the applicable policy.

PRIMARY REFERENCES

Sources for this decision

Links are selected for the question on this page, not to meet a link quota. They do not imply endorsement. Institutional, IRB, consent, legal and funder requirements control the actual study; this independent resource does not make an IRB or regulatory determination.