You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
According to GDPR, an end-user should be able to request the removal of his/her history. It cannot be done right now.
Urgency
To facilitate in becoming a GDPR compliant implementation in a standardized way
Describe the solution you'd like
Add an endpoint removing bookings (per booking-id). The functional request is actually to remove all personal information from this booking, it shouldn't be possible to trace it to a person. This means removal of references to persons (id), but also driver license, etc. This endpoint should be in the support module.
Describe alternatives you've considered
Removal based on a person's id, but this doesn't hold in the case of rotating person ids.
Possible Implementation
DELETE /booking/{id}. Although it is starting with /bookings/, it's not part of the booking module
The text was updated successfully, but these errors were encountered:
TO and MP have a legal and fiscal obligations to maintain certain records in line with the use/rental of [their] assets.
They should publish the retention period of specific information.
If a user has booked and/or used assets - it will not be possible to remove the personal info unless the retention period has been reached.
Is your feature request related to a problem? Please describe.
According to GDPR, an end-user should be able to request the removal of his/her history. It cannot be done right now.
Urgency
To facilitate in becoming a GDPR compliant implementation in a standardized way
Describe the solution you'd like
Add an endpoint removing bookings (per booking-id). The functional request is actually to remove all personal information from this booking, it shouldn't be possible to trace it to a person. This means removal of references to persons (id), but also driver license, etc. This endpoint should be in the support module.
Describe alternatives you've considered
Removal based on a person's id, but this doesn't hold in the case of rotating person ids.
Possible Implementation
DELETE /booking/{id}. Although it is starting with /bookings/, it's not part of the booking module
The text was updated successfully, but these errors were encountered: