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

Define cookie policy 🍪 #1797

Closed
fedekunze opened this issue Jan 4, 2019 · 9 comments · Fixed by #2348
Closed

Define cookie policy 🍪 #1797

fedekunze opened this issue Jan 4, 2019 · 9 comments · Fixed by #2348
Assignees
Labels
design-work-needed 🎨 issues that require design work before development documentation 📚 Issues that require documentation either on the repository or in the Cosmos Docs high priority ❗

Comments

@fedekunze
Copy link
Contributor

Description:

We need to define this on Voyager web for GDPR compliance

@fedekunze fedekunze changed the title Define cookie policy 🍪 Define cookie policy 🍪 Jan 4, 2019
@fedekunze fedekunze added the documentation 📚 Issues that require documentation either on the repository or in the Cosmos Docs label Jan 4, 2019
@jbibla
Copy link
Collaborator

jbibla commented Jan 4, 2019

giphy-1

@faboweb
Copy link
Collaborator

faboweb commented Jan 7, 2019

We can use @nylira approach.

@faboweb faboweb self-assigned this Feb 25, 2019
@jbibla
Copy link
Collaborator

jbibla commented Feb 25, 2019

i will share some design ideas.

@jbibla jbibla self-assigned this Feb 25, 2019
@jbibla jbibla added the design-work-needed 🎨 issues that require design work before development label Feb 25, 2019
@jbibla
Copy link
Collaborator

jbibla commented Feb 26, 2019

i'd like to hear from our lawyers on this before i design anything. is that ok?

@faboweb
Copy link
Collaborator

faboweb commented Feb 26, 2019

That could still take some time ^^ We can use something standard in the meantime.

@jbibla
Copy link
Collaborator

jbibla commented Feb 26, 2019

i don't really want to emulate the cookie popup just because everyone else is doing it - if we are not sure what is actually required. plus, we won't really even be certain we're covering our bases in terms of event and error tracking.

i'm just saying let's make sure we do it right.

@faboweb faboweb added the blocked ✋ issues blocked by other implementations/issues label Feb 28, 2019
@faboweb
Copy link
Collaborator

faboweb commented Mar 4, 2019

Note:
I think we should have error tracking for people who don't sign in. For those a popup and following a set cookie about the preferences would be nice.

@jbibla
Copy link
Collaborator

jbibla commented Mar 5, 2019

here is a nice example from https://safe.gnosis.io/

screen shot 2019-03-05 at 3 57 50 pm

@faboweb
Copy link
Collaborator

faboweb commented Mar 6, 2019

I like it, let's do it.

@faboweb faboweb removed the blocked ✋ issues blocked by other implementations/issues label Mar 11, 2019
@faboweb faboweb mentioned this issue Mar 25, 2019
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-work-needed 🎨 issues that require design work before development documentation 📚 Issues that require documentation either on the repository or in the Cosmos Docs high priority ❗
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants