Eyebrow Text
Title
Ultimate Regulatory Guide for Identity
Subtitle
Map regulatory laws for privacy, AI, cyber, and specific industries to Ping Identity products and solutions.
show-chat-cta
true
chat-cta-label
Ask Ping AI About Compliance
chat-cta-link
chat://open
title
theme
default

Global Regulatory Compliance by Design

How Ping Products Meet Regulations

This chart shows how key PingOne services map to common identity and privacy regulations, so you can quickly see what’s already supported and what you can configure to meet your requirements.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
Supports Consent Capture
1:1 Facial Matching

Persistent

Biometric Database

AI/ML capabilities
Government IDs
Biometric Data Processing
Zero-Day Retention
Customer-Selecting Hosting Region
Subprocessor Controls
HTML
CSS
#mktoForm_6845 .mktoButtonRow { margin-top: -24px !important; }
JS

United States

Executive Summary

The United States maintains a multi-layered privacy, biometric, and cybersecurity regulatory landscape, where the applicability of federal, state, and sector-specific laws may depend on the types of personal data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, or identity verification), the state(s) of the end user’s residence, and how a Ping Identity solution is configured and deployed.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
Comprehensive State Privacy Laws
GLBA (financial services)
HIPAA (healthcare)
State Biometric Laws
n/a
n/a
n/a
n/a
n/a
n/a
Driver’s License Capture Laws
n/a
n/a
n/a
n/a
n/a
n/a

Comprehensive State Privacy Laws

Scope: Comprehensive state privacy laws in a growing number of U.S. states (e.g., CA, CO, VA, CT, UT, TX, OR, MT, IN, IA, TN, DE, and NJ) regulate identity-related and sensitive data (including biometrics and government IDs), establish consumer rights, and impose controller–processor contractual obligations.

Core Obligations:

Gramm-Leach-Bliley Act (GLBA)

Scope: Applies to financial institutions (e.g., banks, lenders, fintechs) that collect, process, or share nonpublic personal information (NPI) about consumers in connection with financial products or services. GLBA obligations may apply in parallel with state privacy, biometric, and cybersecurity laws depending on the organization’s business model, regulated status, and use of PingOne services.

Core Obligations:

Relevance to PingOne Services:

Data Attributes
PingOne Services may process identity attributes, authentication data, and device/risk signals used in financial workflows; Verify/Recognize may process biometric and ID data
Customers may reference product fact sheets here
Authentication & Fraud Prevention
PingOne Protect, MFA/PingID, and Verify support identity assurance and fraud mitigation
These controls may support GLBA Safeguards Rule requirements. Customers may reference product fact sheets here
Notice
Customer-controlled UX (e.g., DaVinci) can support presentation of privacy notices
Customers remain responsible for GLBA-compliant privacy disclosures
Safeguards
Enterprise-grade security controls
Customers should align Ping deployments with their GLBA security program; Customers may reference product fact sheets here, our Data Supplement, and additional security information available here

Health Insurance Portability and Accountability Act (HIPAA)

Scope: Applies to covered entities (health plans, providers, clearinghouses) and their business associates that create, receive, maintain, or transmit protected health information (PHI). HIPAA may be applicable where PingOne Services are used in healthcare authentication or patient access scenarios. HIPAA obligations may apply alongside state privacy, biometric, and cybersecurity laws depending on the organization’s role, the involvement of PHI, and the use of PingOne services.

Core Obligations:

Relevance to PingOne Services:

Data Attributes
PingOne Services may process identity and authentication data; PHI processing depends on customer implementation
Customers should assess whether PHI is processed within authentication or identity workflows; Customers may reference product fact sheets here
Authentication & Access Control
Ping products support secure access to healthcare systems
These capabilities may support HIPAA Security Rule requirements (e.g., access control, authentication); Customers may reference product fact sheets here
Notice
Customer-controlled UX (e.g., DaVinci) can support presentation of privacy notices
Customers remain responsible for HIPAA-compliant privacy disclosures (e.g., Notices of Privacy Practices)
Safeguards
Enterprise-grade security controls; encryption, access controls, and monitoring capabilities
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
Business Associate Relationship
Ping may act as a business associate in CIAM use cases
Customers should determine whether a BAA is required based on their use case

State Biometric & Identity Data Laws

Scope: Several U.S. states have enacted laws regulating the collection and use of biometric identifiers and identity document data (e.g., Illinois BIPA and Texas CUBI).

Core Obligations: Organizations deploying identity verification services for residents of these states should assess whether their configuration involves the processing of biometric identifiers (e.g., facial geometry). Where applicable, these laws may require:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Notice & Consent
Disclosure and electronic consent can be presented in-flow (e.g., via PingOne DaVinci)
Customers may reference product fact sheets here and sample language here
Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here and sample language here
No Selling
Personal data is not sold by Ping Identity; processing is limited to providing identity services
Risk Assessments
Security-by-design architecture supporting identity assurance and fraud mitigation, reinforced by enterprise-grade safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here

State Driver's License and ID Data Capture Laws

Scope: Many U.S. states regulate the electronic scanning, storage, and reuse of driver’s license and state ID data (e.g., CA, TX, VA, IL, OR, NH, RI, GA, HI, NE, SC, VT, OH). These laws are generally purpose-limited rather than biometric-specific laws.

Core Obligations: Many states restrict:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes

PingOne Verify may process government IDs for identity verification and fraud prevention; essential fields captured by default

Other PingOne services generally do not process government IDs

Customers may reference product fact sheets here
Notice & Consent
Disclosure and electronic consent can be presented in-flow (e.g., via DaVinci) before ID scan
Customers may reference product fact sheets here and sample language here
Data Retention
Zero-day retention under default settings for PingOne Verify and PingOne Recognize
Customers may reference product fact sheets here
No Selling or Reuse
ID data is not sold by Ping Identity; processing is limited to identity verification and fraud prevention

United Kingdom

Executive Summary

In the UK, Ping Identity products may fall within scope of the UK GDPR, Data Protection Act 2018, and PECR when they process personal data or biometrics, or use cookies and electronic communications. Applicability depends on the data processed, enabled functionality (e.g., SSO, MFA, fraud prevention, identity verification), and deployment configuration.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
UK GDPR
Data Protection Act 2018
PECR

UK General Data Protection Regulation (UK GDPR)

Scope: Applies to processing of personal data of UK residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Lawful Basis

Contractual necessity supports core authentication

Legitimate interests supports security and fraud detection

Legal obligation supports regulatory identity verification

Explicit consent or substantial public interest may support biometric processing (can be presented in-flow (e.g., via PingOne DaVinci))

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

Data Protection Act 2018

Scope: Supplements the UK GDPR. Sets out the ICO’s enforcement powers, added safeguards for special category and criminal offence data, and UK-specific accountability rules for high-risk processing. Applies to organizations processing personal data in the UK, including identity, authentication, fraud, and biometric data.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here

Privacy and Electronic Communications Regulations (PECR)

Scope: Governs electronic communications in the UK, including cookies, device access, electronic marketing, and traffic/location data. PECR applies alongside the UK GDPR and is relevant where identity services use cookies, device fingerprinting, session tracking, SMS authentication, push notifications, or email verification.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Session Technologies
PingOne SSO uses session cookies and browser storage for federation and secure access
See product documentation here
Device Recognition
PingOne Protect may use device recognition or fingerprinting
See product documentation here
Electronic Messaging
PingOne MFA and PingID use push, SMS, and email verification within electronic communications frameworks
See product documentation here

European Union

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

This section provides the core obligations under the GDPR and EU AI Act. Local implementing laws and regulator guidance may add country-specific rules (including biometric, telecoms, and eID requirements), which organizations should review in addition to this guide.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles

For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.

Ping Identity may act as an independent controller for limited internal business purposes including platform security, fraud prevention, improvement of the products, and operational processing activities.

Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Australia

Executive Summary

Australia applies a principles-based privacy framework under the Privacy Act 1988 (Cth), supplemented by the Australian Privacy Principles (APPs). Biometric data and government-issued identity data are generally treated as sensitive information, requiring consent (typically express) and clear justification for collection and use.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, data categories processed, and customer configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
Privacy Act 1988 (APPs)

Privacy Act 1988 (Australian Privacy Principles)

Scope: Applies to private-sector organizations handling personal information in Australia.

Core Obligations:

Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Notice & Consent
Disclosure and electronic consent can be presented in-flow (e.g., via PingOne DaVinci)
Customers may reference product fact sheets here and sample language here
Privacy Notice
Configurable workflows support disclosures
Customers may reference product fact sheets here and sample language here
Data Minimization & Retention
Default configurations support session-based processing and limited data capture
Customers who want to extend the default retention settings are encouraged to document their justifications
Safeguards
Enterprise-grade security controls
Additional information available here

Austria

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Belgium

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Brazil

Executive Summary

Brazil regulates personal data under the Lei Geral de Proteção de Dados (LGPD), a comprehensive privacy law similar in structure to GDPR. Legal basis is required for all processing, especially sensitive data, including biometrics.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, data categories processed, and customer configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
LGPD

LGPD (Lei Geral de Proteção de Dados)

Scope: Applies to processing of personal data in Brazil.

Core Obligations:

Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Notice & Consent
Disclosure and electronic consent can be presented in-flow (e.g., via PingOne DaVinci)
Customers may reference product fact sheets here and sample language here
Privacy Notice
Configurable workflows support disclosures
Customers may reference product fact sheets here and sample language here
Data Minimization & Retention
Default configurations support session-based processing and limited data capture
Customers may reference product fact sheets here; Customers who want to extend the default retention settings are encouraged to document their justifications
Safeguards
Enterprise-grade security controls
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here

Canada

Executive Summary

Canada applies a principles-based privacy framework, where applicability may depend on the types of personal data processed (including biometric and identity document data), the functionality enabled (e.g., identity verification, fraud prevention, authentication), the province of the end user (e.g., Québec vs. other provinces), and how a Ping Identity solution is configured and deployed.

Canada’s federal law (PIPEDA), alongside provincial regimes (notably Québec Law 25), places strong emphasis on meaningful consent, data minimization, and accountability, particularly for sensitive data such as biometrics.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected Canadian regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, data categories processed, and customer configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
PIPEDA (Federal Privacy Law)

PIPEDA (Federal Privacy Law)

Scope: Applies to private-sector organizations engaged in commercial activities across Canada, including interprovincial and international data transfers. Governs the collection, use, and disclosure of personal information, including identity and biometric data.

Core Obligations:

Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Notice & Consent
Disclosure and electronic consent can be presented in-flow (e.g., via PingOne DaVinci)
Customers may reference product fact sheets here and sample language here
Privacy Notice
Configurable workflows and purpose-limited processing design support accurate disclosures
Customers may reference product fact sheets here and sample language here
Data Minimization & Retention
Default configurations support session-based processing and limited data capture
Customers who want to extend the default retention settings are encourage to document their justifications
No Selling
Personal data is not sold by Ping Identity; processing is limited to providing identity services
Safeguards
Security-by-design architecture supporting identity assurance and fraud mitigation, reinforced by enterprise-grade safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here

Denmark

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Finland

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

France

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Germany

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Hungary

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

India

Executive Summary

India regulates personal data under the Digital Personal Data Protection Act, 2023 (DPDP Act). The framework is consent-driven with evolving interpretation. Identity and biometric data may trigger heightened compliance considerations depending on the deployment context, applicable sectoral requirements, and the types of verification workflows implemented (e.g., financial services, telecom, or digital onboarding).

India maintains a highly regulated digital identity ecosystem, particularly in financial services and telecom onboarding contexts. Applicability of sector-specific obligations may vary depending on whether deployments interact with regulated onboarding, KYC, financial services, telecom, or digital identity frameworks.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, data categories processed, and customer configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
DPDP Act

Digital Personal Data Protection Act (DPDP)

Scope: Applies to processing of digital personal data in India. The DPDP Act’s implementation remains subject to evolving subordinate rules, regulatory guidance, and enforcement practices.

Core Obligations:

Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Notice & Consent
Disclosure and electronic consent can be presented in-flow (e.g., via PingOne DaVinci)
Customers may reference product fact sheets here and sample language here
Privacy Notice
Configurable workflows support disclosures
Customers may reference product fact sheets here and sample language here
Data Minimization & Retention
Default configurations support session-based processing and limited data capture
Customers who want to extend the default retention settings are encouraged to document their justifications
Safeguards
Enterprise-grade security controls
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here

Ireland

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Italy

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Netherlands

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

New Zealand

Executive Summary

New Zealand regulates personal information under the Privacy Act 2020, supported by Information Privacy Principles (IPPs). The framework emphasizes transparency, purpose limitation, proportionality, and reasonable safeguards when processing personal information.

The Office of the Privacy Commissioner (OPC) oversees enforcement and guidance under the Privacy Act 2020, including expectations relating to transparency, proportionality, safeguards, and cross-border disclosures.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, data categories processed, and customer configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
Privacy Act 2020 (IPPs)

Privacy Act 2020

Scope: Applies to agencies handling personal information in New Zealand.

Core Obligations:

Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Notice & Consent
Disclosure and electronic consent can be presented in-flow (e.g., via PingOne DaVinci)
Customers may reference product fact sheets here and sample language here
Privacy Notice
Configurable workflows support disclosures
Customers may reference product fact sheets here and sample language here
Data Minimization & Retention
Default configurations support session-based processing and limited data capture
Customers who want to extend the default retention settings are encouraged to document their justifications
Safeguards
Enterprise-grade security controls
Additional information available here

Singapore

Executive Summary

Singapore regulates personal data under the Personal Data Protection Act (PDPA), which emphasizes consent, purpose limitation, retention controls, and accountability. Identity and biometric data are generally treated as sensitive in practice, requiring careful handling and justification.

Applicability depends on how PingOne Services are deployed.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, data categories processed, and customer configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
PDPA

Personal Data Protection Act (PDPA)

Scope: Applies to organizations collecting, using, or disclosing personal data in Singapore.

Core Obligations:

Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Notice & Consent
Disclosure and electronic consent can be presented in-flow (e.g., via PingOne DaVinci)
Customers may reference product fact sheets here and sample language here
Privacy Notice
Configurable workflows support disclosures
Customers may reference product fact sheets here and sample language here
Data Minimization & Retention
Default configurations support session-based processing and limited data capture
Customers who want to extend the default retention settings are encouraged to document their justifications
Safeguards
Enterprise-grade security controls
Additional information available here

Spain

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Sweden

Executive Summary

Within the European Union, PingOne services may fall within the scope of the GDPR and the EU AI Act when they process personal data, including biometric data. Applicability depends on the specific data processed, the functionality enabled (e.g., SSO, MFA, fraud prevention, identity verification), and the customer’s deployment configuration and use case.

Regulations Applicable to PingOne Services Deployments

This matrix illustrates how selected regulatory regimes may be triggered by different Ping Identity product deployments, depending on the functionality enabled, the categories of data processed, and the customer’s configuration choices.

Regulation
Protect
Verify
Recognize
Credentials
AIC
SSO
MFA / PingID
DaVinci
GDPR
EU AI Act
n/a
n/a
n/a
n/a
n/a

EU General Data Protection Regulation (GDPR)

Scope: Applies to processing of personal data of EU residents, including collection, authentication, identity verification, authorization, and fraud detection. Biometric data used to uniquely identify a person is treated as special category data and requires heightened protection.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
Configurable identity attributes processed depending on product and deployment (e.g., name, email, username, device identifiers, IP address, government ID data, facial geometry).
Customers may reference product fact sheets here
Roles
For most deployments, the customer acts as a data controller and Ping acts as a processor. Customers remain responsible for lawful basis, consent, and retention policies.
Lawful Basis

Contractual necessity supports core authentication;

Legitimate interests supports security and fraud detection;

Legal obligation supports regulatory identity verification;

Substantial public interest applies in limited statutory circumstances; or

Explicit consent may justify biometric processing (e.g., captured in-flow via PingOne DaVinci); provide a non-biometric alternative if required by law and an individual declines consent. Where individuals decline biometric verification or where biometric processing is not appropriate, customers may perform in-person manual identity verification.

Customers may reference product fact sheets here and sample consent language here
Transparency & Privacy Notice
Configurable workflows, data mapping, retention controls, and purpose-limited processing design
Customers may reference product fact sheets here
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design architecture supporting identity assurance and fraud mitigation, with technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here
International Transfers
Regional storage, documented subprocessor arrangements, and contractual safeguards provided
Applicable countries here; Ping Identity is certified under the E.U.-US Data Privacy Framework; standard Data Privacy Addendum here; transfer impact assessment available upon request

EU AI Act

Scope: Establishes a risk-based framework for the development, marketing, and use of AI systems in the EU. Classifies systems as prohibited, high-risk, limited-risk, or minimal-risk, with obligations tied to risk level. Certain biometric systems, including identity verification and facial recognition, may fall within scope depending on functionality and deployment, particularly when used for access to essential services, employment, financial services, or other regulated activities.

Core Obligations:


Relevance to PingOne Services:

Control Area
Product Capability
Customer Consideration
Data Attributes
PingOne Verify, Recognize, and Protect are narrow purpose AI systems focused on 1:1 identity verification and fraud prevention, supported by lifecycle governance, human oversight, transparency, and continuous monitoring controls. Final classification depends on deployment context.
Customers may reference product fact sheets here; AI Mapping Guide and Model Governance Report upon request for applicable products
Safeguards
Enterprise-grade security controls
Additional information available here
Risk Assessments
Privacy-by-design identity assurance and fraud mitigation framework with embedded technical and organizational safeguards
Customers may reference product fact sheets here, our Data Supplement, and additional security information available here; AI Mapping Guide and Model Governance Report upon request for applicable products

Sample Notice and Consent Language

For Informational Purposes Only – Not Legal Advice

This sample language is provided for informational purposes only and does not constitute legal advice. Applicability of U.S. privacy, biometric, and driver’s license laws depends on an organization’s specific use case, configuration, and jurisdiction. Organizations are responsible for determining how laws apply to their deployment and should consult qualified legal counsel regarding compliance obligations.

Identity Services Data Processing Notice & Consent (No Biometric Data)

We use identity and access management technologies to protect your account and prevent fraud. When you sign in or access this service, we collect and process personal information such as:

We use this information to:

Authentication and fraud prevention may involve automated systems that analyze risk signals associated with your login or activity and may result in an access decision.

We retain personal information only as long as reasonably necessary for security, fraud prevention, legal compliance, and operational purposes, after which it is securely deleted or de-identified.

Depending on your location, you may have rights regarding your personal information, including rights to access, correction, deletion, and restriction of certain processing activities. For more information about how we handle personal information and your applicable privacy rights, please review our Privacy Notice.

By selecting “Continue,” you acknowledge that you have read this notice and consent to the collection and processing of your personal information for these purposes.

[Continue] [Cancel]

Identity Services Data Processing Notice & Consent (Including Biometric Data)

We use identity and access management technologies to protect your account, prevent fraud, and maintain the security of our services. When you sign in or access this service, we collect and process personal information such as:

We use this information to:

We do not use biometric information for marketing, advertising, profiling for unrelated purposes, or sale.

Authentication and fraud prevention may involve automated systems that analyze risk signals associated with your login or activity and may result in an access decision. Where biometric verification is enabled, automated facial comparison technologies may be used as part of that process.

We retain personal information, including biometric information where applicable, only as long as reasonably necessary for security, fraud prevention, legal compliance, and operational purposes, after which it is securely deleted or de-identified in accordance with our retention policies.

Depending on your location, you may have rights regarding your personal information, including rights to access, correction, deletion, and restriction of certain processing activities. For more information about how we handle personal information and your applicable privacy rights, please review our Privacy Notice.

By selecting “Continue,” you acknowledge that you have read this notice and consent, where required by applicable law, to the collection and processing of your personal information, including biometric information, for the purposes stated herein.

Sample Privacy Notice Language

Sample Biometric Policy Language

For Informational Purposes Only – Not Legal Advice

This sample language is provided for informational purposes only and does not constitute legal advice. This sample is only a starting point; organizations should tailor it to the specific jurisdictions and statutory definitions (e.g., BIPA, CUBI, Québec Law 25) that apply to their deployment. The applicability of other privacy, biometric, or identity document laws depends on an organization’s specific use case, configuration, jurisdiction, and role. Organizations are responsible for determining how laws apply to their deployment and should consult qualified legal counsel regarding compliance obligations.

Biometric Data Privacy Policy

Effective Date: [Insert Date]
Last Updated: [Insert Date]

This Biometric Data Privacy Policy (“Policy”) describes how [Company Name] (“Company,” “we,” “us,” or “our”) collects, uses, stores, safeguards, and deletes biometric identifiers and biometric information in connection with identity verification and fraud prevention activities. This Policy applies to individuals whose biometric data is collected through our identity verification processes.

  1. Purpose

This Policy is intended to address applicable biometric privacy laws, including U.S. state biometric privacy laws, U.S. comprehensive privacy laws, EU General Data Protection Regulation (GDPR), and the UK GDPR, and other applicable global privacy frameworks. Biometric data may be considered “special category” personal data under GDPR/UK GDPR and “sensitive personal information” under certain U.S. state laws.

We collect and process biometric identifiers solely for legitimate business purposes, including:

  1. Identity verification, including during onboarding or account access
  2. Document authentication
  3. Fraud prevention and detection
  4. Protecting accounts and systems
  5. Compliance with legal and regulatory obligations

Biometric data is not sold, leased, traded, or otherwise profited from.

  1. Categories of Biometric Data Collected

Depending on the services being used and configuration settings, we may collect and process the following biometric data:

  1. Facial geometry data extracted from a selfie and/or government-issued ID photo
  2. Biometric templates generated from facial images
  3. Facial similarity or match scores generated during 1:1 face comparison
  4. Liveness detection results to confirm a live human presence
  5. Confidence scores associated with biometric verification results

“Biometric information” means information based on a biometric identifier used to identify an individual. We do not use biometric data for surveillance, marketing, behavioral profiling unrelated to identity verification, or 1:many biometric identification searches across unrelated individuals.

  1. Legal Basis and Consent

Where required by applicable law, we:

  1. Provide advance notice that biometric identifiers will be collected
  2. Process biometric data only where a valid lawful basis for special category data applies. Depending on the context, this may include explicit consent of the individual; substantial public interest (where applicable under law); establishment, exercise, or defense of legal claims; or compliance with legal obligations.
  3. Offer individuals the opportunity to decline biometric processing (where feasible and legally required)

Consent records are maintained in accordance with applicable legal requirements.

  1. Retention Schedule

We retain biometric identifiers and biometric information only for as long as necessary to fulfill the purpose for which they were collected. Biometric images and derived templates are deleted promptly after completion of the identity verification process. In certain implementations, biometric data may be cached for a short operational period (e.g., up to 30 minutes) to complete processing. If retention is required for fraud investigation, legal compliance, audit, or dispute resolution purposes, biometric data may be retained for a defined period consistent with applicable law and business necessity.

Biometric identifiers will be permanently deleted when the original purpose for collection has been satisfied; or within the time period required by applicable law (e.g., no later than three years after the individual’s last interaction with the Company, where required by statute), whichever occurs first.

  1. Safeguards and Security Measures

We implement reasonable administrative, technical, and physical safeguards designed to protect biometric data from unauthorized access, acquisition, disclosure, alteration, or destruction. Administrative safeguards may include role-based access controls, confidentiality obligations for personnel, vendor due diligence and contractual data protection obligations, and incident response and breach notification procedures.

Technical safeguards may include encryption in transit and at rest, secure API communications, network segmentation, access logging and monitoring, automated deletion workflows, and secure key management practices. Physical safeguards may include secure data center environments and access-controlled facilities. Biometric data is treated as sensitive data and subject to heightened protection controls.

  1. Disclosure of Biometric Data

We do not disclose biometric identifiers except to service providers acting on our behalf under written agreements requiring confidentiality and data protection; as required by law, subpoena, court order, or other valid legal process; to detect, investigate, or prevent fraud or security incidents; or with the individual’s consent. We do not sell biometric data.

  1. International Data Transfers

Where biometric data is transferred outside the country of collection (including transfers from the EU/UK to the United States or other jurisdictions), we implement appropriate safeguards as required by applicable law, which may include Standard Contractual Clauses (SCCs), the UK International Data Transfer Addendum, or other approved transfer mechanisms. Individuals may request additional information regarding applicable transfer safeguards.

  1. Individual Rights

Subject to applicable law, individuals may have the right to:

  1. Request access to personal information we maintain
  2. Request deletion of biometric data
  3. Withdraw consent (where consent is the legal basis for processing)
  4. Receive information about our data handling practices

Requests may be submitted to: [Insert Privacy Contact Email or Portal]

  1. Updates to This Policy

We may update this Biometric Privacy Policy from time to time to reflect changes in technology, law, or business operations. Updates will be posted with a revised effective date. Where required by applicable law, material changes will be communicated in advance.

This guide is provided for informational purposes only and does not constitute legal advice. While Ping Identity provides features and configurations intended to support compliance with global privacy laws, the regulatory landscape is complex and varies by jurisdiction, specific use cases, configurations, and operational context. Customers are responsible for ensuring their specific configuration and data processing activities comply with all applicable laws.

content-source
/en-us/build-your-regulatory-guide/sheets/regulatory-chat-widget
chat-endpoint
/bin/ping/regulatoryChat
retain-session
true
trigger-label
Return to chat
display-mode
overlay
preview-state
closed
panel-disclaimer
Disclaimer: This AI-powered chat is for general informational purposes only. Responses may be incomplete, outdated, or not tailored to your circumstances. It does not provide legal, regulatory, or professional advice.
HTML
CSS
JS

(function privacyGuideQuizResponsesRefactor() {

const REVEAL_DELAY_MS = 2000;

const TOC_OBSERVER_TIMEOUT_MS = 3000;

const COUNTRY_QUESTION = "Next, Let's Get Specific.";

const ALWAYS_VISIBLE_SECTIONS = [

"global-regulatory-compliance-by-design",

"sample-consent-language",

"sample-privacy-notice-language"

];

let revealTimer = null;

let tocObserver = null;

let tocObserverTimer = null;

let isRevealed = false;

const normalizeText = (value) => (value || '').trim().toLowerCase();

function clearAsyncHandles() {

if (revealTimer) { window.clearTimeout(revealTimer); revealTimer = null; }

if (tocObserver) { tocObserver.disconnect(); tocObserver = null; }

if (tocObserverTimer) { window.clearTimeout(tocObserverTimer); tocObserverTimer = null; }

}

function reveal() {

if (isRevealed) return;

isRevealed = true;

clearAsyncHandles();

document.body.classList.add('appear');

}

function decodeQuizResponses(rawValue) {

if (!rawValue) return null;

const decodedUri = decodeURIComponent(rawValue);

const base64Normalized = decodedUri.replace(/-/g, '+').replace(/_/g, '/');

const paddingLength = (4 - (base64Normalized.length % 4)) % 4;

const base64Padded = `${base64Normalized}${'='.repeat(paddingLength)}`;

try {

return JSON.parse(window.atob(base64Padded));

} catch (error) {

try { return JSON.parse(decodedUri); } catch (parseError) { return null; }

}

}

function getSelectedCountries(payload) {

if (!payload || !Array.isArray(payload.responses)) return [];

const countryEntry = payload.responses.find((entry) => entry.question === COUNTRY_QUESTION);

const answers = Array.isArray(countryEntry?.answers) ? countryEntry.answers : [];

return answers.map(normalizeText).filter(Boolean);

}

function buildSections(article) {

const wrappers = Array.from(article.children);

const sections = [];

let activeSection = null;

wrappers.forEach((wrapper, index) => {

const h2 = wrapper.querySelector(':scope > h2');

if (h2) {

activeSection = {

heading: h2.textContent.trim(),

id: h2.id || '',

start: index,

end: index,

};

sections.push(activeSection);

return;

}

if (activeSection) {

activeSection.end = index;

}

});

return { wrappers, sections };

}

function collectSubheadings(wrappers, start, end) {

const headings = [];

wrappers.slice(start, end + 1).forEach((wrapper) => {

wrapper.querySelectorAll('h3, h4, h5, h6').forEach((heading) => {

headings.push(heading.textContent.trim());

});

});

return headings;

}

function applySectionVisibility(article, selectedCountries) {

const { wrappers, sections } = buildSections(article);

if (!sections.length) return null;

const selectedSet = new Set(selectedCountries);

const visibleHeadings = new Set();

const staticWhitelist = ALWAYS_VISIBLE_SECTIONS.map(normalizeText);

sections.forEach((section) => {

const sectionText = normalizeText(section.heading);

const sectionId = normalizeText(section.id);

const isStatic = staticWhitelist.includes(sectionId) || staticWhitelist.includes(sectionText);

const isSelected = selectedSet.has(sectionText) || selectedSet.has(sectionId);

const shouldShow = isStatic || isSelected;

for (let index = section.start; index <= section.end; index += 1) {

wrappers[index].hidden = !shouldShow;

}

if (shouldShow) {

visibleHeadings.add(section.heading);

collectSubheadings(wrappers, section.start, section.end)

.forEach((heading) => visibleHeadings.add(heading));

}

});

return visibleHeadings;

}

function filterAccordionToc(tocNav, visibleHeadings) {

const accordionItems = tocNav.querySelectorAll('.toc-item.accordion-item');

if (!accordionItems.length) return false;

const normalizedVisible = new Set(Array.from(visibleHeadings).map(normalizeText));

const whitelistIds = ALWAYS_VISIBLE_SECTIONS.map(normalizeText);

accordionItems.forEach((item) => {

const link = item.querySelector('a.toc-link') || item.querySelector('a');

if (!link) return;

const linkText = normalizeText(link.textContent);

const linkHref = normalizeText(link.getAttribute('href')?.replace('#', ''));


const shouldShow = normalizedVisible.has(linkText) || whitelistIds.includes(linkHref);

item.hidden = !shouldShow;

if (!shouldShow) return;

item.querySelectorAll('.accordion-body a').forEach((subLink) => {

const row = subLink.closest('.toc-item-row') || subLink.closest('li') || subLink;

const subText = normalizeText(subLink.textContent);

const subHref = normalizeText(subLink.getAttribute('href')?.replace('#', ''));

row.hidden = !(normalizedVisible.has(subText) || whitelistIds.includes(subHref));

});

});

return true;

}

function filterFlatToc(tocNav, visibleHeadings) {

const links = tocNav.querySelectorAll('a');

if (!links.length) return false;

const normalizedVisible = new Set(Array.from(visibleHeadings).map(normalizeText));

const whitelistIds = ALWAYS_VISIBLE_SECTIONS.map(normalizeText);

links.forEach((link) => {

const row = link.closest('li') || link.closest('.toc-item-row') || link.closest('.toc-item') || link;

const linkText = normalizeText(link.textContent);

const linkHref = normalizeText(link.getAttribute('href')?.replace('#', ''));

row.hidden = !(normalizedVisible.has(linkText) || whitelistIds.includes(linkHref));

});

return true;

}

function filterToc(visibleHeadings) {

const tocNav = document.querySelector('nav[aria-label="Table of contents"]');

if (!tocNav) return false;

return filterAccordionToc(tocNav, visibleHeadings) || filterFlatToc(tocNav, visibleHeadings);

}

function startTocObserver(visibleHeadings) {

tocObserver = new MutationObserver(() => {

if (filterToc(visibleHeadings)) reveal();

});

tocObserver.observe(document.body, { childList: true, subtree: true });

tocObserverTimer = window.setTimeout(reveal, TOC_OBSERVER_TIMEOUT_MS);

}

revealTimer = window.setTimeout(reveal, REVEAL_DELAY_MS);

const rawParam = new URLSearchParams(window.location.search).get('quizResponses');

if (!rawParam) { reveal(); return; }

const payload = decodeQuizResponses(rawParam);

const selectedCountries = getSelectedCountries(payload);

if (!selectedCountries.length) { reveal(); return; }

document.documentElement.dataset.quizFilter = 'active';

const article = document.querySelector('main article');

if (!article) { reveal(); return; }

const visibleHeadings = applySectionVisibility(article, selectedCountries);

if (!visibleHeadings) { reveal(); return; }

if (filterToc(visibleHeadings)) { reveal(); return; }

startTocObserver(visibleHeadings);

}());