Open tubbynl opened 6 years ago
Need to discuss it.
Several questions:
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
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)
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)
i assum the enum-values of initState remains are as they are used now (optin-optout-disabled)
Yes
optin = 1 optout = 0 alwayson = -1
partially fixed by #15
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'