> Not sure how when all that changes is the clock. This is most surely not the case. Many data stores are simply dated collection of files. With fixed expirat

> Not sure how when all that changes is the clock. This is most surely not the case. Many data stores are simply dated collection of files. With fixed expiration for all data you can simply implement GDPR with things like TTLs and making sure that any downstream systems do not consume data older than a certain date. With individual wipeouts that can happen at any time this becomes much more challenging. Now all data, in all systems that use that data have to the ability to wipe data at the individual record level on demand. This broad implications especially depending on how interpret whether things like derived models, aggregate stats, etc. need to be recalculated in light of GDPR requests.