Russian Data Privacy

Introduction

• Data Privacy Module and its Russian Data Privacy sub-module must be enabled for the account on the Implementation > Products page.
• Help is available at help@certain.com to enable these features.
• Data protection laws apply to all acts of data processing, including collection, recording, systematization, accumulation, storage, alteration (update, modification), retrieval, use, transfer (dissemination, provision, access), depersonalization, blocking, deletion or destruction of data.
• Electronic (automated) and manual (non-automated) records of personal data will be subject to the data protection legislation.
• The Russian Data Privacy feature enables the following scenario: The registrant registers for an event via a form or SSO.
• One or more fields on the registrant profile are checked for compliance.
• If the fields comply, the data is sent to a third-party via a web service.
• The data is saved temporarily elsewhere, such as in a specific country, by that service.
• The data is passed back to Certain for storage on Certain's servers.
• Note: Each section on this page has its own Save button.

Privacy Configurations

• Privacy Configurations define how privacy controls are configured for the Russian Data Privacy feature.

Policy

• Policy is the technical type of privacy policy. Example: "RDP".

Config Name

• Config Name is the name of the configuration, as set by Certain for the system.

Start Date

• Start Date is the date the configuration comes into effect.

End Date

• End Date is the end of the "in effect" period.

Service Auth Type

• Service Auth Type selects the authorization type: either OAuth2 or Basic Auth.

Service URL

• Service URL is the URL provided by the third-party supplier for access to its web service.

OAuth2 Fields

• Client ID is required and provided by the third-party application.
• Client Secret is required.
• Token URL is required.
• Resource is required.

Basic Auth Fields

• Username is required.
• Password is required.

Wait Message

• Wait Message is the message to be displayed to attendees while the web service is making the request.
• Note: For future use. Not in use at present.

Service Error Messaging

• Service Error Messaging is the error message to be shown if the web service is down or unsuccessful.
• Technical note: Unsuccessful means the external webservice returns anything other than an HTTP 200 (OK) response.

Capture External ID Key

• Capture External ID Key is provided by the third-party supplier.

Event Trigger

• The field and value(s) that the post will watch.

Trigger Field

• Trigger Field selects a Certain field for the policy to watch.
• Those available include Standard Profile Enumerated Fields, specifically Country.

Trigger Values

• Trigger Values are the values that the policy will watch, and invoke the web service based on its evaluation.

Field Mappings

• You must map at least First Name, Last Name and Email in Certain to the equivalent Target Fields.

Certain Field

• Certain Field selects a Certain field to map. Those available include:
• Standard Profile fields
• Static Profile fields
• Custom Profile fields
• Static fields

Target Field

• Target Field enters the name of the matching field from the third-party app.
• Example: if Certain Field = "First Name", then Target Field might be "firstname".

Add field mapping

• Add field mapping adds a row to map another pair of fields.

Policy Compliance Audit

• The Policy Compliance Audit lists only non-compliant records.

• Records are compliant when the profile has gone through either of two entry points, SSO or Form, and Trigger Field is one of those selected in Trigger Values defined under Trigger Fields above.

• The table lists these fields for each record:
• Audit Date Time – When the compliance audit was run.
• Profile Date Created – When the Profile was created via a registration form.
• Correlation Id – Unique ID and associated records, generated by Certain.
• External Id – A unique ID generated by the third party app, and associated with the records in their database.
• Non Compliance Reason – Generated message for non-compliant records.

[JSON-LD block will follow]