Abstract
A data platform carries machine-readable retention policy at the granularity of individual tables and columns: for each column, what is stored, why, for how long, and the terminal action (delete the row, null the field, or overwrite the field with a placeholder where the platform marks the column required and a null write would be rejected), while preserving the audit trail. The policy is embedded in version-controlled schema documentation and validated on every build against a periodically captured snapshot of the live database schema, so a policy referencing a column that does not exist, or nulling a column the platform marks required, fails the build. Retention proposals for uncovered tables are derived automatically from the platform's own relationship and cascade-delete configuration, resolving multi-parent tables by a most-restrictive-parent rule. The validated policy is emitted as a machine-readable artefact with per-entry provenance, and an enforcement engine consumes it to perform the per-field terminal actions on schedule.
Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.
Recommended Citation
AlpenShield GmbH, "Schema-Validated Field-Level Data Retention Policy Coupled to a Live Database Schema, Driving Automated Per-Field Erasure", Technical Disclosure Commons, ()
https://www.tdcommons.org/dpubs_series/11429