Data Layer medium complexity frontend
0
Dependencies
0
Dependents
0
Entities
0
Integrations

Description

Manages access to DPA document versions stored as structured static assets. Reads document JSON or Markdown source files at build time and exposes them through a typed interface. Tracks version history so the UI can surface the effective date.

Feature: Data Processing Agreement (DPA)

dpa-document-repository

Sources & reasoning

Listed explicitly in the Sales Website product description at line 224. Phase mapping: Sales Website scope appears in Fase 1 MVP at lines 335-338 → "MVP". A DPA is a GDPR Article 28 prerequisite for any SaaS platform processing personal data on behalf of customer organizations; all four target organizations are data controllers bound by GDPR.

Responsibilities

  • Load current DPA document from static asset store
  • Provide version history list with effective dates
  • Validate document schema on load and surface parse errors
  • Return null-safe results for missing or malformed versions

Interfaces

getCurrent(): DpaDocument
getVersion(versionId: string): DpaDocument | null
listVersions(): DocumentVersion[]