Design Principle

DP1 - Do not store personal data on a blockchain

Keep personal data off-chain, since blockchain's tamper-resistant storage conflicts with the rights to rectification and erasure;

Design PrincipleOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/gdpr-workflow-asylum-dp1

Open concept record

Producer label: DP1
Source paper: How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure
Timestamp: 2026-07-16T00:00:00+00:00
Bundle path: design-knowledge/gdpr-workflow-asylum-dp1.md

cross-organizationaldesign-principlegdpr-privacygdpr-workflow-asylumpublic-sectorworkflow-management

Design principle DP1: Do not store personal data on a blockchain

Keep personal data off-chain, since blockchain's tamper-resistant storage conflicts with the rights to rectification and erasure; this encourages B2B networks that do not process personal data of participants or third parties.

Source paper

This design principle is proposed by How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure (Florian Guggenmos, Annette Wenninger, Alexander Rieger, Gilbert Fridgen, Jannik Lockl, 2020).

Citations

[1] Florian Guggenmos, Annette Wenninger, Alexander Rieger, Gilbert Fridgen, Jannik Lockl. How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure. HICSS 53 (2020). https://hdl.handle.net/10125/64253 (opens in a new tab) [2] Source document: How to Develop a GDPR-Compliant Blockchain Solution for cross-organizational workflow management.pdf

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Design Principle

Design Principle1

Design Principle

design-knowledge/gdpr-workflow-asylum-dp2

DP2 - Use a highly secure off-chain mapping architecture for attribution

If a use case requires that data on the blockchain be attributable to a natural person, employ pseudonymization:

cross-organizationaldesign-principlegdpr-privacygdpr-workflow-asylum+2

Paper

Paper1

Paper

papers/gdpr-workflow-asylum

How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure

Drawing on the German Federal Office for Migration and Refugees (BAMF) case, the paper presents two actionable design principles for GDPR-compliant blockchain solutions in cross-organizational workflow management: do not store personal data on a blockchain, and, where attribution is required, use a highly secure off-chain mapping architecture.

blockchaincross-organizationaldesign-science-researchgdpr-privacy+3

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure
Paper
Source
DP1 - Do not store personal data on a blockchain
Target
How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure
Link label
How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure
Status
Resolved
Derived heading context: Source paper

Incoming backlinks

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

3 of 3 concepts · 5 directed relationships

Concept types

Design PrincipleSeed

DP1 - Do not store personal data on a blockchain

Bundle identity

Concept ID: design-knowledge/gdpr-workflow-asylum-dp1
Markdown path: design-knowledge/gdpr-workflow-asylum-dp1.md
Producer label: DP1
Native type: design-principle

Markdown summary

Design principle DP1: Do not store personal data on a blockchain Keep personal data off-chain, since blockchain's tamper-resistant storage conflicts with the rights to rectification and erasure; this encourages B2B networks that do not process personal data of participants or third parties. Source paper This design principle is proposed by How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure (Florian Guggenmos, Annette Wenninger, Alexander Rieger, Gilbert Fridgen, Jannik Lockl, 2020). Citations [1] Florian Guggenmos, Annette Wenninger, Alexander Rieger, Gilbert Fridgen, Jannik Lockl. How to Develop a…

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter

{
  "type": "design-principle",
  "title": "DP1 - Do not store personal data on a blockchain",
  "description": "Keep personal data off-chain, since blockchain's tamper-resistant storage conflicts with the rights to rectification and erasure;",
  "resource": "https://hdl.handle.net/10125/64253",
  "source_paper": "How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure",
  "label": "DP1",
  "tags": [
    "gdpr-workflow-asylum",
    "design-principle",
    "gdpr-privacy",
    "cross-organizational",
    "public-sector",
    "workflow-management"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}

Design Principle

DP1 - Do not store personal data on a blockchain

Keep personal data off-chain, since blockchain's tamper-resistant storage conflicts with the rights to rectification and erasure;

Design PrincipleOpen source resource ↗

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/gdpr-workflow-asylum-dp1

Open concept record

Producer label: DP1
Source paper: How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure
Timestamp: 2026-07-16T00:00:00+00:00
Bundle path: design-knowledge/gdpr-workflow-asylum-dp1.md

cross-organizationaldesign-principlegdpr-privacygdpr-workflow-asylumpublic-sectorworkflow-management

Design principle DP1: Do not store personal data on a blockchain

Source paper

Citations

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

Design Principle

Design Principle1

Design Principle

design-knowledge/gdpr-workflow-asylum-dp2

DP2 - Use a highly secure off-chain mapping architecture for attribution

If a use case requires that data on the blockchain be attributable to a natural person, employ pseudonymization:

cross-organizationaldesign-principlegdpr-privacygdpr-workflow-asylum+2

Paper

Paper1

Paper

papers/gdpr-workflow-asylum

How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure

blockchaincross-organizationaldesign-science-researchgdpr-privacy+3

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure
Paper
Source
DP1 - Do not store personal data on a blockchain
Target
How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure
Link label
How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure
Status
Resolved
Derived heading context: Source paper

Incoming backlinks

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

3 of 3 concepts · 5 directed relationships

Concept types

Design PrincipleSeed

DP1 - Do not store personal data on a blockchain

Bundle identity

Concept ID: design-knowledge/gdpr-workflow-asylum-dp1
Markdown path: design-knowledge/gdpr-workflow-asylum-dp1.md
Producer label: DP1
Native type: design-principle

Markdown summary

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter

{
  "type": "design-principle",
  "title": "DP1 - Do not store personal data on a blockchain",
  "description": "Keep personal data off-chain, since blockchain's tamper-resistant storage conflicts with the rights to rectification and erasure;",
  "resource": "https://hdl.handle.net/10125/64253",
  "source_paper": "How to Develop a GDPR-Compliant Blockchain Solution for Cross-Organizational Workflow Management: Evidence from the German Asylum Procedure",
  "label": "DP1",
  "tags": [
    "gdpr-workflow-asylum",
    "design-principle",
    "gdpr-privacy",
    "cross-organizational",
    "public-sector",
    "workflow-management"
  ],
  "timestamp": "2026-07-16T00:00:00+00:00"
}