Skip to content
This repository has been archived by the owner on Feb 19, 2022. It is now read-only.

GDPR Compliance #52

Open
synap5e opened this issue May 12, 2019 · 0 comments
Open

GDPR Compliance #52

synap5e opened this issue May 12, 2019 · 0 comments
Assignees
@synap5e
Labels
further awaiting discussion This needs some thought, discussion needs to happen to confirm the expected outcome requires backend changes This will require changes to the backend/API before it can be implemented

Comments

@synap5e
Copy link
Collaborator

synap5e commented May 12, 2019

Overtrack uses cookies to store a user session ID when logged in, and stores user data serverside.
I'm not fully clear on what would be required here.

Perhaps we could make the agreement part of the signup process (at least for new users) since users that aren't logged in don't have any data stored on them.
For existing users we would either need to force-logout everyone or store if they have agreed.
@synap5e synap5e added further awaiting discussion This needs some thought, discussion needs to happen to confirm the expected outcome requires backend changes This will require changes to the backend/API before it can be implemented labels May 12, 2019
@synap5e synap5e self-assigned this May 12, 2019
@synap5e synap5e mentioned this issue May 12, 2019
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@synap5e synap5e

Labels
further awaiting discussion This needs some thought, discussion needs to happen to confirm the expected outcome requires backend changes This will require changes to the backend/API before it can be implemented
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@synap5e