6.9.2.3 ErasureRequest
6.9.2.3.1 Purpose¶
A farm that leaves, or asks for its data to be removed. Execution anonymizes everything that leads back to the farm, while canonical values are kept under new random ids.
6.9.2.3.2 Questions it answers¶
- Has a farm asked for erasure, and when was it executed?
- Which write performed it?
6.9.2.3.3 Fields¶
| Field | Type | Cardinality | Description |
|---|---|---|---|
id |
string (uuid) |
1..1 |
Key. |
farm |
Farm | 1..1 |
|
requested_at |
datetime |
1..1 |
|
executed_at |
datetime |
0..1 |
|
executed_in |
WriteCommit | 0..1 |
|
created_at |
datetime |
1..1 |
6.9.2.3.4 Relationships¶
References
ErasureRequest.farm→ Farm (1..1)ErasureRequest.executed_in→ WriteCommit (0..1)
Referenced by
6.9.2.3.5 Rules & constraints¶
- A farm that leaves, or asks for its data to be removed. Data is anonymized and kept.
- Scope pending legal confirmation.
- Execution removes everything that can lead back to the farm: names, contacts, locations, official and farm identifiers, device serials. Canonical values stay, attached to new random ids with no stored link to the old ones; kept model datasets (
ModelRun.dataset_path) and dataset versions (MlDatasetVersion) are rewritten the same way. If a link is kept, the data is only pseudonymized and is still personal data.
Open questions
Confirm the scope with the legal adviser.