Difference between revisions of "ATC/Current/AdminGuide/GDPR"

From Genesys Documentation
Jump to: navigation, search
(Published)
m (Text replacement - "Genesys Cloud" to "Genesys Cloud CX")
 
(21 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
{{ArticleUnstructured
+
{{Article
−
|DisplayName=GDPR
+
|Standalone=No
−
|Platform=PureEngage, PureConnect, PureCloud
+
|DisplayName=General Data Protection Regulation (GDPR)
 +
|TocName=General Data Protection Regulation
 
|Context=Learn how to use {{MINTYDOCSPRODUCT}} in a GDPR-compliant way.
 
|Context=Learn how to use {{MINTYDOCSPRODUCT}} in a GDPR-compliant way.
−
}}
+
|Dimension=Compliance
−
=={{MINTYDOCSPRODUCT}} and GDPR==
+
|ComingSoon=No
−
For the purposes of GDPR compliance, Genesys is a data processor on behalf of customers who use the {{MINTYDOCSPRODUCT}} product. You, our customers, are the data controllers of the personal data you collect from your end customers, the data subjects. This article describes how to adhere to GDPR consent requirements, should you identify consent as the most appropriate lawful basis for processing personal data. Note that there is no ‘right’ or ‘wrong’ lawful basis for processing personal data; the GDPR requires that data controllers consider the most appropriate lawful basis. A helpful link for what to consider when determining the most appropriate lawful basis can be found {{#Widget:ExtLink|link=https://ico.org.uk/for-organisations/resources-and-support/lawful-basis-interactive-guidance-tool/|displaytext=here.}}
+
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 +
|Section={{Section
 +
|alignment=Vertical
 +
|structuredtext={{NoteFormat|This article only applies to customers using {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=About_web_chats|display text=web chat}}. If you are a Genesys Cloud CX customer, we encourage you to use the new {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat.
  
−
{{NoteFormat|Be sure you understand the steps you need to take '''before''' you collect, process, or store your end-customers' personal data.|1}}
+
For web messaging, tracking starts as soon as you deploy Genesys Messenger to your web site. Deployment implies acknowledgment that you are aware of the implications of capturing data.|}}
 +
|Status=No
 +
}}{{Section
 +
|sectionHeading=GDPR compliance
 +
|alignment=Vertical
 +
|structuredtext=As part of the Genesys Cloud CX platform, Genesys Predictive Engagement complies with GDPR regulations. For more information about Genesys Cloud CX and GDPR, see [https://help.mypurecloud.com/articles/?p=161527 Genesys Cloud CX and GDPR compliance].
  
−
{{MINTYDOCSPRODUCT}} collects data about visitors' activities on business websites. It uses machine learning and AI to analyze customer-generated events (page views, searches, form-fills, and chats) to determine the probability of a specific customer achieving a specific outcome. An outcome is an event the business wants to maximize or minimize. Example outcomes are making a purchase, signing up for a webinar, or filling out a complex form online. For information about how {{MINTYDOCSPRODUCT}} uses cookies to track visitor activity on websites, see {{#mintydocs_link:manual=Developers|topic=Cookies|link text=Cookie usage.}} 
+
Genesys Cloud CX provides a [https://developer.genesys.cloud/api/rest/v2/generaldataprotectionregulation/index.html GDPR API]. The GDPR API is the preferred self-service solution for Genesys Cloud CX customers to respond to GDPR requests. The GDPR API enables responses to data subject requests to access, rectify, or delete their personal data in Genesys Cloud CX.
 +
|Status=No
 +
}}{{Section
 +
|sectionHeading=Genesys Predictive Engagement considerations
 +
|alignment=Vertical
 +
|structuredtext=For the purposes of GDPR compliance, Genesys is a data processor on behalf of customers who use the Genesys Predictive Engagement product. You, our customers, are the data controllers of the personal data that you collect from your end customers, the data subjects. This article describes how to adhere to GDPR consent requirements, should you identify consent as the most appropriate lawful basis for processing personal data. Note that there is no ‘right’ or ‘wrong’ lawful basis for processing personal data; the GDPR requires that data controllers consider the most appropriate lawful basis. For more information about what to consider when determining the most appropriate lawful basis, see [https://ico.org.uk/for-organisations/gdpr-resources/lawful-basis-interactive-guidance-tool/ Lawful basis interactive guidance tool].
  
−
Businesses use end-customer data that {{MINTYDOCSPRODUCT}} collects for three primary purposes:
+
Genesys Predictive Engagement collects data about visitors' activities on business websites. It uses machine learning and AI to analyze customer-generated events (page views, searches, form-fills, and chats) to determine the probability of a specific customer achieving a specific outcome. An outcome is an event the business wants to maximize or minimize. Example outcomes are making a purchase, signing up for a webinar, or filling out a complex form online. For more information about how Genesys Predictive Engagement uses cookies to track visitor activity on websites, see {{Link-SomewhereInThisVersion|manual=SDK|topic=Cookie_usage|display text=Cookies}}.
−
* Customer support - proactive or AI-driven engagement via chat and callback offers;
 
−
* Sales engagement - proactive or AI engagement via chat, callbacks, and content offers;
 
−
* Marketing - proactive or AI; for example, sign-up for an event or webinar via content offer.
 
  
−
If you are still unsure as to whether you should obtain the data subject's consent to process their personal data, you may wish to consult your legal advisor.
+
Businesses use end-customer data that Genesys Predictive Engagement collects for three primary purposes:
  
−
{{NoteFormat|Genesys does not pass end customer personal data processed through {{MINTYDOCSPRODUCT}} to any advertising or re-targeting companies. End-customer personal data processed through {{MINTYDOCSPRODUCT}} may be shared with business-integrated tools such as Salesforce and Marketo. This will happen '''only''' when one of our business customers configures that behavior for their organization. |1}}
+
*Customer support - proactive or AI-driven engagement through chat and callback offers;
 +
*Sales engagement - proactive or AI engagement through chat, callbacks, and content offers;
 +
*Marketing - proactive or AI; for example, sign-up for an event or webinar through a content offer.
  
−
===PureCloud and GDPR===
+
If you are still unsure whether you should obtain the data subject's consent to process their personal data, consult your legal advisor.{{NoteFormat|Genesys does not pass end-customer personal data processed through Genesys Predictive Engagement to any advertising or re-targeting companies. End-customer personal data processed through Genesys Predictive Engagement may be shared with business-integrated tools such as Salesforce and Marketo. Sharing only happens when one of our business customers configures that behavior for their organization.|}}
−
For more information on how PureCloud addresses GDPR compliance, see
+
|Status=No
−
{{#Widget:ExtLink|link=https://help.mypurecloud.com/articles/gdpr-compliance/|displaytext=GDPR compliance.}}
+
}}{{Section
 +
|sectionHeading=Conditions for consent
 +
|alignment=Vertical
 +
|structuredtext=If you identified consent as the most appropriate lawful basis for processing end customer personal data, then the following conditions should be met when obtaining consent:
  
−
==Conditions for consent==
+
*You must be able to demonstrate that the data subject has consented to processing of his or her personal data. That means you should maintain a record or audit trail of consent being given.
−
If you have identified consent as the most appropriate lawful basis for processing end customer personal data, then the following conditions should be met when obtaining consent:
 
  
−
* You must be able to demonstrate that the data subject has consented to processing of his or her personal data. That means you should maintain a record or audit trail of consent being given.
+
*If the data subject's consent is given in the context of a written declaration which also concerns other matters, the request for consent shall be presented in a manner which is clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language.
  
−
* If the data subject's consent is given in the context of a written declaration which also concerns other matters, the request for consent shall be presented in a manner which is clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language.
+
*The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal. Prior to giving consent, the data subject shall be informed thereof. It shall be as easy to withdraw as to give consent.
  
−
* The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal. Prior to giving consent, the data subject shall be informed thereof. It shall be as easy to withdraw as to give consent.
+
*When assessing whether consent is freely given, utmost account shall be taken of whether, among other things, the performance of a contract, including the provision of a service, is conditional on consent to the processing of personal data that is not necessary for the performance of that contract.
  
−
* When assessing whether consent is freely given, utmost account shall be taken of whether, among other things, the performance of a contract, including the provision of a service, is conditional on consent to the processing of personal data that is not necessary for the performance of that contract.
+
If you identified consent as the most appropriate lawful basis for processing end customer personal data, consider what consent was given before calling the following functions:
  
−
If you have identified consent as the most appropriate lawful basis for processing end customer personal data, then you should consider what consent has been given before calling the following functions.
+
*<code>ac('init',...)</code> starts Genesys Predictive Engagement tracking on your website
 +
*<code>ac('record',...)</code> allows Genesys Predictive Engagement tracking of custom visitor actions on your website
 +
*<code>ac('identify',...),</code> is used to identify visitors
  
−
The <tt>ac('init',...)</tt> function starts {{MINTYDOCSPRODUCT}} tracking on your website.
+
For more information about these functions and others where you might need to consider consent, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=Tracking with Predictive Engagement}}.{{NoteFormat|If you require consent to be GDPR-compliant, obtain that consent before passing any personally identifiable data to Genesys Predictive Engagement.|}}
−
 
+
|Status=No
−
The <tt>ac('record',...)</tt> function allows {{MINTYDOCSPRODUCT}} tracking of custom user actions on your website.
+
}}{{Section
−
 
+
|sectionHeading=Stop tracking
−
The <tt>ac('identify',...),</tt> function is used to identify end-users.
+
|alignment=Vertical
−
 
+
|structuredtext=For more information about how to stop tracking when a visitor revokes consent, see {{Link-SomewhereInThisVersion|manual=SDK|topic=Web_tracking_API|anchor=StopTracking|display text=Stop tracking if a customer revokes consent.}}
−
For more information about these functions and others where consent may need to be considered, see  
+
|FAQHeading=How to stop tracking if a visitor revokes consent
−
{{#mintydocs_link:manual=Developers|topic=Tracking_code|link text=About the tracking snippet.}}
+
|Status=No
−
 
+
}}
−
{{NoteFormat|If you require consent to be GDPR-compliant, obtain that consent before passing any personally identifiable data to {{MINTYDOCSPRODUCT}}.|1}}
+
}}
−
 
 
−
==Make a "right to be forgotten" request==
 
−
As a data controller, you can make a "right to be forgotten" request on behalf of a visitor. To do this, send an email to [mailto:DataPrivacy@Genesys.com DataPrivacy@Genesys.com]. Be sure to provide the following identifying parameters for the visitor. These parameters are the primary keys by which {{MINTYDOCSPRODUCT}} recognizes unique visitors:
 
−
*Email address
 
−
*Phone number
 
−
*Cookie ID
 
−
*Business-specific ID that has been passed to {{MINTYDOCSPRODUCT}} with other customer data
 
−
 
 
−
{{NoteFormat|
 
−
It is your responsibility as the data controller to:
 
−
*Confirm the visitor's identity before submitting a "right to be forgotten" request on their behalf to Genesys.
 
−
*Provide the identifying parameters of the visitor who is requesting to be forgotten.
 
−
'''Notes:'''
 
−
*All identities related to these parameters will be subject to deletion.
 
−
*After Genesys deletes visitor data, it cannot be recovered.|1}}
 
−
 
 
−
Genesys honors "right to be forgotten" requests within 28 days. Genesys sends a confirmation to the data controller when data has been deleted.
 
−
 
 
−
==Make a "right of access" request==
 
−
As a data controller, you can make a "right of access" request. To do this, the designated representative from your organization should send an email to [mailto:DataPrivacy@Genesys.com DataPrivacy@Genesys.com]. The email should contain the identifying parameters for the visitor. These parameters are the primary keys by which {{MINTYDOCSPRODUCT}} recognizes unique visitors:
 
−
*Email address
 
−
*Phone number
 
−
*Cookie ID
 
−
*Business-specific ID that has been passed to {{MINTYDOCSPRODUCT}} with other customer data
 
−
 
 
−
{{NoteFormat|
 
−
It is your responsibility as the data controller to:
 
−
* Confirm the visitor's identity before submitting a "right of access" request on their behalf to Genesys.
 
−
* Provide the identifying parameters of the visitor whose data is to be provided.
 
−
 
 
−
Note:
 
−
*Genesys will provide all data related to the identities having these parameters.
 
−
|1}}
 
−
 
 
−
Genesys honors "right of access" requests within 28 days. Genesys sends your designated representative the data in a suitable format.
 
−
 
 
−
==Stop tracking==
 
−
For information on how to stop tracking if a visitor revokes consent, see ''Stop tracking if a visitor revokes consent'' in the {{#mintydocs_link:manual=Developers|topic=Web_Tracking_API|link text=Web Tracking API}} article. 
 
−
 
 
−
[[Category:V:ATC:Draft]]
 

Latest revision as of 21:28, November 9, 2021

This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.

Learn how to use Genesys Predictive Engagement in a GDPR-compliant way.

Important
This article only applies to customers using web chat. If you are a Genesys Cloud CX customer, we encourage you to use the new web messaging feature to replace web chat. For web messaging, tracking starts as soon as you deploy Genesys Messenger to your web site. Deployment implies acknowledgment that you are aware of the implications of capturing data.

GDPR compliance

As part of the Genesys Cloud CX platform, Genesys Predictive Engagement complies with GDPR regulations. For more information about Genesys Cloud CX and GDPR, see Genesys Cloud CX and GDPR compliance.

Genesys Cloud CX provides a GDPR API. The GDPR API is the preferred self-service solution for Genesys Cloud CX customers to respond to GDPR requests. The GDPR API enables responses to data subject requests to access, rectify, or delete their personal data in Genesys Cloud CX.

Genesys Predictive Engagement considerations

For the purposes of GDPR compliance, Genesys is a data processor on behalf of customers who use the Genesys Predictive Engagement product. You, our customers, are the data controllers of the personal data that you collect from your end customers, the data subjects. This article describes how to adhere to GDPR consent requirements, should you identify consent as the most appropriate lawful basis for processing personal data. Note that there is no ‘right’ or ‘wrong’ lawful basis for processing personal data; the GDPR requires that data controllers consider the most appropriate lawful basis. For more information about what to consider when determining the most appropriate lawful basis, see Lawful basis interactive guidance tool.

Genesys Predictive Engagement collects data about visitors' activities on business websites. It uses machine learning and AI to analyze customer-generated events (page views, searches, form-fills, and chats) to determine the probability of a specific customer achieving a specific outcome. An outcome is an event the business wants to maximize or minimize. Example outcomes are making a purchase, signing up for a webinar, or filling out a complex form online. For more information about how Genesys Predictive Engagement uses cookies to track visitor activity on websites, see Cookies.

Businesses use end-customer data that Genesys Predictive Engagement collects for three primary purposes:

  • Customer support - proactive or AI-driven engagement through chat and callback offers;
  • Sales engagement - proactive or AI engagement through chat, callbacks, and content offers;
  • Marketing - proactive or AI; for example, sign-up for an event or webinar through a content offer.
If you are still unsure whether you should obtain the data subject's consent to process their personal data, consult your legal advisor.
Important
Genesys does not pass end-customer personal data processed through Genesys Predictive Engagement to any advertising or re-targeting companies. End-customer personal data processed through Genesys Predictive Engagement may be shared with business-integrated tools such as Salesforce and Marketo. Sharing only happens when one of our business customers configures that behavior for their organization.

Conditions for consent

If you identified consent as the most appropriate lawful basis for processing end customer personal data, then the following conditions should be met when obtaining consent:

  • You must be able to demonstrate that the data subject has consented to processing of his or her personal data. That means you should maintain a record or audit trail of consent being given.
  • If the data subject's consent is given in the context of a written declaration which also concerns other matters, the request for consent shall be presented in a manner which is clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language.
  • The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal. Prior to giving consent, the data subject shall be informed thereof. It shall be as easy to withdraw as to give consent.
  • When assessing whether consent is freely given, utmost account shall be taken of whether, among other things, the performance of a contract, including the provision of a service, is conditional on consent to the processing of personal data that is not necessary for the performance of that contract.

If you identified consent as the most appropriate lawful basis for processing end customer personal data, consider what consent was given before calling the following functions:

  • ac('init',...) starts Genesys Predictive Engagement tracking on your website
  • ac('record',...) allows Genesys Predictive Engagement tracking of custom visitor actions on your website
  • ac('identify',...), is used to identify visitors
For more information about these functions and others where you might need to consider consent, see Tracking with Predictive Engagement.
Important
If you require consent to be GDPR-compliant, obtain that consent before passing any personally identifiable data to Genesys Predictive Engagement.

Stop tracking

For more information about how to stop tracking when a visitor revokes consent, see Stop tracking if a customer revokes consent.

Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/GDPR (2024-05-05 02:35:47)"
Comments or questions about this documentation? Contact us for support!