ATC/Current/AdminGuide/GDPR

Genesys Predictive Engagement is compliant with GDPR.

Genesys Predictive Engagement and GDPR

For the purposes of GDPR compliance, Genesys Predictive Engagement is a Data Processor on behalf of our customers. Our customers are the Data Controllers of the personally identifiable data they collect from their end customers, the Data Subjects. This article describes how to adhere to GDPR consent requirements, should consent be necessary. To determine whether you need to obtain your end-customers' consent to collect their personally identifiable data, consult your legal advisor.

Important

Be sure you understand the steps you need to take before you collect, process, or store your end-customers' personally identifiable data.

Genesys Predictive Engagement collects data about visitors' activities on business websites. We use machine learning and AI to analyze customer-generated events (page views, searches, form-fills, and chat) 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 a complex form online. For information about how Genesys Predictive Engagement uses cookies to track visitor activity on websites, see How Genesys Predictive Engagement uses cookies to identify visitors in the [[ATC/Current/Developers/Tracking_code|]] article.

Important

Genesys Predictive Engagement does not pass end-customer data to any advertising or re-targeting companies. Genesys Predictive Engagement passes end-customer data to business-integrated tools such as Salesforce, Marketo, and so on only when one of our business customers configures that behavior for their organization.

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

• 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

You may have additional legitimate bases for collecting, storing, and processing end-customer data. Customer support or sales engagement use cases are typically legitimate. Marketing use cases do not typically qualify as applicable, legitimate interests for collecting personally identifiable data. Consult the appropriate legal sources to determine the applicable bases for collecting personally identifiable data as per your business model.

Implement consent for tracking visitors on your website

Work with your legal counsel to determine whether you need explicit consent to track visitors on your website. If you need explicit consent, see Obtain consent in the [[ATC/Current/Developers/Tracking_code|]] article.

Important

Be sure to state on your user interface why you require consent.

The ac('init',...) function starts Genesys Predictive Engagement's tracking on your website. Call this function only after you receive explicit consent.

Implement consent for form-fill data on your website

Work with your legal counsel to determine whether you need explicit consent to collect form data. To obtain consent for collecting personally identifiable data via a form submit action, include a checkbox with a label such as the following on your website:

• I agree or disagree to allow the business to use this data for purpose.

Also:

• Enable the form's Submit button only after the visitor has selected the checkbox.
• When the visitor clicks the Submit button, call the ac('record',...) function to pass the visitor's data to Genesys Predictive Engagement.
• Whenever you call ac('identify',...), consider whether you need to obtain consent.

For more information about these functions, see [[ATC/Current/Developers/Tracking_code|]].

Important

If you require consent to be GDPR-compliant, obtain that consent before passing any personally identifiable data to Genesys Predictive Engagement.

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 DataPrivacy@Genesys.com. Be sure to provide the following identifying parameters for the visitor. These parameters are the primary keys by which Genesys Predictive Engagement recognizes unique visitors:

• Email address
• Phone number
• Cookie ID
• Business-specific ID that has been passed to Genesys Predictive Engagement with other customer data

Important

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 Predictive Engagement.
• 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 Predictive Engagement deletes visitor data, it cannot be recovered.

Genesys Predictive Engagement honors "Right to be forgotten" requests within 28 days. Genesys Predictive Engagement sends a confirmation to the Data Control 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 email to DataPrivacy@Genesys.com. The email should contain the identifying parameters for the visitor. These parameters are the primary keys by which Genesys Predictive Engagement recognizes unique visitors:

• Email address
• Phone number
• Cookie ID
• Business-specific ID that has been passed to Genesys Predictive Engagement with other customer data

Important

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 Predictive Engagement.
• Provide the identifying parameters of the visitor whose data is to be provided.

Note:

• Genesys Predictive Engagement will provide all data related to the identities having these parameters.

Genesys Predictive Engagement honors "Right of access" requests within 28 days. Genesys Predictive Engagement sends your designated representative the data in JSON 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 [[ATC/Current/Developers/Tracking_code|]] article.