From 73039fbdea1318d151a5417e394d56ab3e60a14d Mon Sep 17 00:00:00 2001 From: Stefan Giehl Date: Wed, 12 Feb 2020 21:26:35 +0100 Subject: makes Ask for Consent page translatable (#15557) --- .../PrivacyManager/templates/askingForConsent.twig | 72 +++++++++++----------- 1 file changed, 36 insertions(+), 36 deletions(-) (limited to 'plugins/PrivacyManager/templates') diff --git a/plugins/PrivacyManager/templates/askingForConsent.twig b/plugins/PrivacyManager/templates/askingForConsent.twig index 6927505d1b..1ef5450a6d 100644 --- a/plugins/PrivacyManager/templates/askingForConsent.twig +++ b/plugins/PrivacyManager/templates/askingForConsent.twig @@ -4,64 +4,64 @@ {% block content %}
-

Asking for consent

-

Consent means offering individuals choice and control about how their personal data is processed.

+

{{ 'PrivacyManager_AskingForConsent'|translate }}

+

{{ 'PrivacyManager_ConsentExplanation'|translate }}

-
+

- In the context of the GDPR privacy regulations, when you are processing personal data, in some cases you will need to ask for your users' consent. To identify whether you need to ask for consent, you need to determine whether your lawful basis for processing personal data is "Consent" or "Legitimate interest", or whether you can avoid collecting personal data altogether. We recommend to learn more about the lawful basis under the GDPR for Matomo. + {{ 'PrivacyManager_WhenConsentIsNeeded1'|translate }}

- Note that when you require to have your users' consents and if you cannot prove that you got the "Consent" of your users in the past, then we recommend to anonymise your previously tracked users' raw data. + {{ 'PrivacyManager_WhenConsentIsNeeded2'|translate('', '.')|raw }}

-
+

- Follow the steps below to ask your user for their consents before their data is processed within Matomo. + {{ 'PrivacyManager_AskForConsentFollowSteps'|translate }}

-

Step 1: require consent

+

{{ 'PrivacyManager_AskForConsentStep1'|translate }}

- To require consent, insert the following line at top of your existing Matomo Tracking code on all your pages: + {{ 'PrivacyManager_AskForConsentStep1Desc1'|translate }} 

// require user consent before processing data
 _paq.push(['requireConsent']);
 _paq.push(['trackPageview']);
 [...]

- Once this function ‘requireConsent' is executed then no tracking request will be sent to Matomo. Note that some tracking cookies will be set during this page view but will be deleted as soon as the user navigates to a different page or closes the browser. + {{ 'PrivacyManager_AskForConsentStep1Desc2'|translate('', '')|raw }}

-

Step 2: asking for consent through your privacy notice

-

Now you can ask the user for consent for example by displaying a clear privacy notice on your pages. Learn more about privacy notices and asking for user consent. Note that Matomo does not yet offer the feature to display a privacy notice, but may implement such a feature in the future to easily let you display the notice and gather user consent. +

{{ 'PrivacyManager_AskForConsentStep2'|translate }}

+

+ {{ 'PrivacyManager_AskForConsentStep2Desc'|translate }}

-

Step 3: user gives consent

+

{{ 'PrivacyManager_AskForConsentStep3'|translate }}

- Once a user gives consent, you can either A) let Matomo remember the consent, or B) use your own consent tool to remember the consent. We present the two solutions below: + {{ 'PrivacyManager_AskForConsentStep3Desc'|translate }}

- A) if you want to let Matomo remember the consent + {{ 'PrivacyManager_AskForConsentStep3DescA'|translate }}
- Once a user gives their consent, you can let Matomo remember that the user has given consent by simply calling the following method once the user has given her or his consent: + {{ 'PrivacyManager_AskForConsentStep3DescADesc1'|translate }} 

_paq.push(['rememberConsentGiven'])

- Matomo will then remember on subsequent requests that the user has given her or his consent by setting a cookie named "consent". As long as this cookie exists, Matomo will know that consent has been given and will automatically process the data. This means that you only need to call _paq.push(['rememberConsentGiven']) once, and it is not needed to call _paq.push(['setConsentGiven']) on any page view. + {{ 'PrivacyManager_AskForConsentStep3DescADesc2'|translate("_paq.push(['rememberConsentGiven'])", "_paq.push(['setConsentGiven'])")|raw }}

- Notes: + {{ 'PrivacyManager_AskForConsentStepNotes'|translate }}

    -
  1. By default, the cookie and consent will be remembered forever. It is possible to define an optional expiry period for your user consent by calling: - +
  2. {{ 'PrivacyManager_AskForConsentStep3DescANote1'|translate }}
    _paq.push(['rememberConsentGiven', optionallyExpireConsentInHours]).
    3. -
  3. When you're tracking multiple sub-domains into the same website in Matomo, you want to ensure that when you ask for Consent, the user gives consent for all the sub-domains on which you are collecting data. If the user only gives consent for a particular domain or sub-domain(s), you may need to restrict or widen the scope of the consent cookie domain and path by using 'setCookieDomain' and ‘setCookiePath' (learn more in the JavaScript tracking guide).
    4. -
  4. It is required that you do not disable cookies.
    5. +
  5. {{ 'PrivacyManager_AskForConsentStep3DescANote2'|translate }}
    6. +
  6. {{ 'PrivacyManager_AskForConsentStep3DescANote3'|translate }}



- B) if you use your own consent tool to remember the consent + {{ 'PrivacyManager_AskForConsentStep3DescB'|translate }}
- In some cases, you record the information that the user has given consent to be tracked directly in your own system or CMS (for example when you use your own a cookie to remember user consent). Once you have the consent by the user to process their data, you need to call the 'setConsentGiven' method: + {{ 'PrivacyManager_AskForConsentStep3DescBDesc1'|translate }} 

// require user consent before processing data
 _paq.push(['requireConsent']);
@@ -71,31 +71,31 @@ _paq.push([‘trackPageview']);
 // user has given consent to process their data
 _paq.push(['setConsentGiven']);

- This lets the JavaScript tracker know that the user has given consent and ensures the tracking is working as expected. This function needs to be called anytime after _paq.push(['requireConsent']). + {{ 'PrivacyManager_AskForConsentStep3DescBDesc2'|translate("_paq.push(['requireConsent'])")|raw }}

- Notes: + {{ 'PrivacyManager_AskForConsentStepNotes'|translate }}

    -
  1. when you call _paq.push(['setConsentGiven']), Matomo will not remember on subsequent requests that this user has given consent: it is important that you call setConsentGiven on every page.
    2. -
  2. when the user has given consent, you could also avoid calling _paq.push(['requireConsent']) in the first place.
    3. +
  3. {{ 'PrivacyManager_AskForConsentStep3DescBNote1'|translate("_paq.push(['setConsentGiven'])")|raw }}
    4. +
  4. {{ 'PrivacyManager_AskForConsentStep3DescBNote2'|translate("_paq.push(['requireConsent'])")|raw }}
-

Step 4: user removes consent

+

{{ 'PrivacyManager_AskForConsentStep4'|translate }}

- In order to remove his consent the user needs to perform a specific action, for example: clicking on a button "I do not want to be tracked anymore". + {{ 'PrivacyManager_AskForConsentStep4Desc'|translate }}

- A) if you want to let Matomo remember the consent + {{ 'PrivacyManager_AskForConsentStep4DescA'|translate }}
- When the user has expressed she or he no longer gives consent, you need to call the following method once: + {{ 'PrivacyManager_AskForConsentStep4DescADesc'|translate }} 

 _paq.push(['forgetConsentGiven']);
-

This makes sure the cookie that remembered the given consent is deleted. - +

+ {{ 'PrivacyManager_AskForConsentStep4DescADesc2'|translate }}

- B) if you use your own consent tool to remember the consent
- When the user has expressed she or he no longer gives consent, you shall not call the following method anymore: + {{ 'PrivacyManager_AskForConsentStep4DescB'|translate }}
+ {{ 'PrivacyManager_AskForConsentStep4DescBDesc'|translate }} 

// do not call this once user has removed their consent
-- 
cgit v1.2.3