Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rotation of asset ID after rental #234

Closed
ewooonk opened this issue Sep 2, 2020 · 1 comment · Fixed by #235
Closed

Rotation of asset ID after rental #234

ewooonk opened this issue Sep 2, 2020 · 1 comment · Fixed by #235
Assignees
Labels
WT1 To be discussed at the next meeting

Comments

@ewooonk
Copy link

ewooonk commented Sep 2, 2020

Is your feature request related to a problem? Please describe.

The current spec of ​/operator​/available-assets allows to derive individual trips of similar vehicles using the vehicle ID.

Urgency

Major, because publishing individual trips is not in accordance with GDPR regulations.

Additional context

MobilityData/gbfs#147

Describe the solution you'd like

Rotate the vehicle ID after every trip.

Describe alternatives you've considered

  • Hide the vehicles for a random time period after the end of rental.

Possible Implementation

See GBFS 2.0.

@edwinvandenbelt edwinvandenbelt self-assigned this Sep 9, 2020
@edwinvandenbelt edwinvandenbelt added the WT1 To be discussed at the next meeting label Sep 9, 2020
@edwinvandenbelt edwinvandenbelt added this to the DragonFly - 1.0.0 milestone Sep 9, 2020
@edwinvandenbelt
Copy link
Collaborator

The TOMP API DOESN'T publish individual trips. But the available-assets could be used to expose asset-locations and thereby can be in conflict with the GDPR.

It should be implemented as follows: the returned objects are collections of assets, including a number of available assets. Not the assets themselves.

Only when a TO wants to publish locations of assets, the assets can be added. If there are snapshots taken from TOs that implemented this endpoint in this way, it might be possible to track people. So I agree with you, I'll add some comment in de swagger file and add a paragraph with this topic in the Wiki.

edwinvandenbelt added a commit to edwinvandenbelt/TOMP-API that referenced this issue Sep 9, 2020
@edwinvandenbelt edwinvandenbelt linked a pull request Sep 9, 2020 that will close this issue
edwinvandenbelt added a commit that referenced this issue Sep 18, 2020
#234 changed description (GDPR compliant assetId)
@edwinvandenbelt edwinvandenbelt moved this to Done in WT1 Kanban Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WT1 To be discussed at the next meeting
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants