Assume, there's a model called **CustomerDetails**, which contains the following properties:


* ContactEmail - an email address for contacting purposes,
* ContactAddress - a postal address for contacting purposes,
* DefaultDeliveryAddress - default address for delivery when creating orders,
* DefaultInvoiceAddress - default address to be printed on invoice, when creating orders,
* and other properties.


All entities in the system are by default audited, ie. they contain change log / revisions history.


Any user can change own CustomerDetails data by himself/herself.


If user changes that information via web-interface, then what is correct:


* there can be no trace of previous information: no revisions history for the CustomerDetails entity, or
* there must be a possibility to delete own revisions for user: extra user interface to view+delete revisions, or
* there is only obligation to delete revisions of CustomerDetails, if Right to erasure (‘right to be forgotten’) is exercised?



Is revision history (audit/change log) compliant with GDPR's right to rectification?