Common use of Regulated Data Clause in Contracts

Regulated Data. Customer acknowledges and agrees that Services are not configured to receive, store, or process (a) technical data controlled by International Traffic in Arms Regulations (ITAR), (b) covered defense information as defined under US Defense Federal Regulation Supplement (DFARS), (c) items and data controlled under the Export Administration Regulations (EAR), (d) Health Insurance Portability and Accountability Act (HIPAA) protected health information (PHI), (e) Payment Card Industry Data Security Standard (PCI-DSS) cardholder data, (f) Federal Information Modernization Act (FISMA) personal data, or (g) any other form of government sensitive information, including but not limited to, Controlled Unclassified Information (CUI), Federal Contract Information (FCI), and other similar data categories governed by US federal regulations (“Regulated Data”). Customer agrees neither Customer nor its Subscription Users will use Services to store Regulated Data or provide access to or submit or transmit any Regulated Data to Sugar when requesting Services or otherwise. Customer also acknowledges and agrees that Services are not configured to receive or store “special categories of data” as such is defined in GDPR, or other similar categories of sensitive information as set forth under Data Protection Laws.

Regulated Data. Customer Partner acknowledges and agrees that Services are SaaS is not configured to receive, store, or process (a) technical data controlled by International Traffic in Arms Regulations (ITAR), (b) covered defense information as defined under US Defense Federal Regulation Supplement (DFARS), (c) items and data controlled under the Export Administration Regulations (EAR), (d) Health Insurance Portability and Accountability Act (HIPAA) protected health information (PHI), (e) Payment Card Industry Data Security Standard (PCI-PCI- DSS) cardholder data, (f) Federal Information Modernization Act (FISMA) personal data, or (g) any other form of government sensitive information, including but not limited to, Controlled Unclassified Information (CUI), Federal Contract Information (FCI), and other similar data categories governed by US federal regulations (“Regulated Data”). Customer Partner agrees neither Customer Customers nor its Subscription Users their users will use Services SaaS to store Regulated Data or provide access to or submit or transmit any Regulated Data to Sugar when requesting Services Products, Support Services, or otherwise. Customer Partner also acknowledges and agrees that Services are ▇▇▇▇ is not configured to receive or store “special categories of data” as such is defined in GDPR, or other similar categories of sensitive information as set forth under Data Protection Laws.

Regulated Data. Customer acknowledges and agrees that Services are not configured to receive, store, or process (a) technical data controlled by International Traffic in Arms Regulations (ITAR), (b) covered defense information as defined under US Defense Federal Regulation Supplement (DFARS), (c) items and data controlled under the Export Administration Regulations (EAR), (d) Health Insurance Portability and Accountability Act (HIPAA) protected health information (PHI), (e) Payment Card Industry Data Security Standard (PCI-DSS) cardholder data, (f) Federal Information Modernization Act (FISMA) personal data, or (g) any other form of government sensitive information, including but not limited to, Controlled Unclassified Information (CUI), Federal Contract Information (FCI), and other similar data categories governed by US federal regulations (“Regulated Data”). Customer agrees neither Customer nor its Subscription Users will use Services to store Regulated Data or provide access to or submit or transmit any Regulated Data to Sugar when requesting Services or otherwise. Customer also acknowledges and agrees that Services are not configured to receive or store “special categories of data” as such is defined in GDPR, or other similar categories of sensitive information as set forth under Data Protection Laws. 2.