Logo
NeoArc Studio

Documenting Data Lifecycles

Learn how to document how data moves through your systems from creation to deletion using data lifecycle blocks.

Compliance audits ask difficult questions: Where is customer data stored? Who can access it? How long do you keep it? When do you delete it? Data lifecycle blocks capture these answers in a structured format that satisfies auditors and helps engineers understand data flows.

Why Document Data Lifecycles

Data governance is not optional in regulated industries:

GDPR
Requires knowing where personal data exists and enabling deletion
CCPA
Requires disclosing what data you collect and how you use it
PCI-DSS
Requires understanding where payment card data flows
SOC 2
Auditors want documentation of data handling practices

Adding a Data Lifecycle Block

Data Lifecycle Fields

This example uses the NeoArc Data Lifecycle content block.

Data Classification Levels

NeoArc supports four classification levels:

ClassificationDescriptionExamples
PublicCan be shared freelyMarketing content, public documentation
InternalFor internal use onlyInternal metrics, employee directories
ConfidentialRestricted access, business sensitiveCustomer data, financial records
RestrictedHighest protection, regulated dataPayment card data, health records

This example uses the NeoArc Data Lifecycle content block.

Connecting to Compliance Requirements

This documentation site includes data lifecycle blocks wherever we document data flows, demonstrating how to integrate lifecycle documentation with other architecture content.

Next Steps

Embedding API Endpoints
Connect data lifecycle to API documentation
Learn more →
Embedding Schemas
Link to schema definitions showing data structure
Learn more →
Documenting NFRs
Define measurable data handling requirements
Learn more →