Request Data Minimization Policy
policy · created
Evidence record
- What is verified
- Uses in published workflows: 0
- Revision
- Version 0.1.3
- Validation status
- Public-sanitized publication; no independent validation is claimed.
What this is and why
The Talomnia site database stores only reference identifiers and bounded technical sync fields for incoming requests; all personal data lives solely in the Arcanada Support Center. Minimization is structural rather than disciplinary: the request table has no free-text column and no JSON catch-all, so personal data has nowhere to live, and the column set is pinned by a test that turns red if any column is added. Deleting records is a deliberate operator procedure, not a runtime code path.
Where it was applied and what it helped deliver
No published workflow records this capability yet — the count includes only ledger mentions that resolve.
Relations
- Uses: derived-from
- sanitized-projection
- Uses: related
- projection-pipeline
- Used by: related
- projection-pipeline
- Required by: governed-by
- sc6-support-center
Metadata and provenance
- id
- tal-policy-request-data-minimization
- type
- policy
- version
- 0.1.3
- origin
- created in Talomnia
- lifecycle
- public_sanitized
- tags
- privacy, data-minimization, tz-6-3
The source is the private knowledge repository; only the sanitized public projection reaches this site.
verified · tal-policy-request-data-minimization · v0.1.3