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

Descriptions based on settings #6

Open
tubbynl opened this issue Mar 27, 2018 · 6 comments
Open

Descriptions based on settings #6

tubbynl opened this issue Mar 27, 2018 · 6 comments

Comments

@tubbynl
Copy link

tubbynl commented Mar 27, 2018

Description

Some details in the description need to be based on tracker settings on the website

Expected Behavior

The description "Google Analytics verzameld geanonimiseerd gegevens over het surfgedrag op deze website. Door het anonimiseren is dit niet naar jou te herleiden." should partially be based on the initstate setting.

"Door het anonimiseren is dit niet naar jou te herleiden." depends on how GA is configured (anonymise thingie).

Possible Fix

This could reflect as a option for 'initstate'

  • disabled: Om dit mogelijk te maken staat {} altijd aan.
  • optin: Je bepaalt zelf of je {} aan- of uitzet.
  • optout: Je bepaalt zelf of je {} uit- of aanzet.
  • anonimised: Door anonimisering is dit niet naar jou te herleiden en staat {} altijd aan.
tubbynl added a commit to smile-nl/consentcookie that referenced this issue Mar 27, 2018
@StevenChoo
Copy link
Member

Need to discuss it.

Several questions:

  • is it a common setting "anonymised" of is it specific for 1 (or 2) trackers
  • if it's not common, how will we handle options that are tracker specific (in general)
  • how do we guarantee that if it's set anonymised the trackers works like that (and is this a relevant issue). Especially with the current Facebook debate and companies collecting data.

@tubbynl
Copy link
Author

tubbynl commented Mar 28, 2018

no, i think it should be a setting like "you can't disable it and i(webmaster) have set the settings of this tracker in such a way it's workings are anonimised"

being that the webmaster "says" he's done actions in the trackers config to ensure anonimity

being an explicit setting it's an webmaster's responsibility to do so

@StevenChoo
Copy link
Member

I think one of the problems is that the state currently is called: disabled.

Something like "alwayson" would be more clear.

With that, adding a flag next to the initstate property, e.g. "anomymous":"true" would give the option to let ConsentCookie know the configured tracker/app is collecting data anonymously.

connection config example:

{
	"initstate": 1,
	"anonymous": true
}

With this you can also provide an option for optin / optout and set the flag anomymous = true
In the "connections" if the flag is set, ConsentCookie will show a generic message e.g
"This website uses this tracker to collect data anonymously"

(the used naming are a proposal and for debate)

@tubbynl
Copy link
Author

tubbynl commented Mar 28, 2018

yes, that is more explicit and transparent, i also agree on the naming, i assum the enum-values of initState remains are as they are used now (optin-optout-disabled)

@StevenChoo
Copy link
Member

i assum the enum-values of initState remains are as they are used now (optin-optout-disabled)

Yes

optin = 1
optout = 0
alwayson = -1

@StevenChoo
Copy link
Member

partially fixed by #15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants