Common use of Preventing Unauthorized Product Access Clause in Contracts

Preventing Unauthorized Product Access. Outsourced processing: SyncForce hosts its Service with outsourced cloud infrastructure providers. Additionally, SyncForce maintains contractual relationships with vendors in order to provide the Service in accordance with our Data Processing Agreement. SyncForce relies on contractual agreements, privacy policies, and vendor compliance programs in order to protect data processed or stored by these vendors. Physical and environmental security: SyncForce hosts its product infrastructure with multi-tenant, outsourced infrastructure providers. The physical and environmental security controls are audited for SOC 2 Type II and ISO 27001 compliance, among other certifications. Authentication: SyncForce implemented a uniform password policy for its customer products. Customers who interact with the products via the user interface must authenticate before accessing non-public customer data. Authorization: Customer data is stored in multi-tenant storage systems accessible to Customers via only application user interfaces and application programming interfaces. Customers are not allowed direct access to the underlying application infrastructure. The authorization model in each of SyncForce’s products is designed to ensure that only the appropriately assigned individuals can access relevant features, views, and customization options. Authorization to data sets is performed through validating the user’s permissions against the attributes associated with each data set. Application Programming Interface (API) access: Public product APIs may be accessed using an API key or through Oauth authorization.

Preventing Unauthorized Product Access. Outsourced processing: SyncForce Wakeupsales hosts its Service with outsourced cloud infrastructure providers. Additionally, SyncForce Wakeupsales maintains contractual relationships with vendors in order to provide the Service in accordance with our Data Processing Agreement. SyncForce Wakeupsales relies on contractual agreements, privacy policies, and vendor compliance programs in order to protect data processed or stored by these vendors. Physical and environmental security: SyncForce Wakeupsales hosts its product infrastructure with multi-multi- tenant, outsourced infrastructure providers. The physical and environmental security controls are audited for aligned with SOC 2 Type II and ISO 27001 compliance27001, among other certificationsstandards. Authentication: SyncForce implemented Wakeupsales implements a uniform password policy for its customer products. Customers who interact with the products via the user interface must authenticate before accessing non-public customer data. Authorization: Customer data is stored in multi-tenant storage systems accessible to Customers via only application user interfaces and application programming interfaces. Customers are not allowed direct access to the underlying application infrastructure. The authorization model in each of SyncForce’s Wakeupsales products is designed to ensure that only the appropriately assigned individuals can access relevant features, views, and customization options. Authorization to data sets is performed through validating the user’s permissions against the attributes associated with each data set. Application Programming Interface (API) access: Public product APIs may be accessed over secured socket layer (SSL) or Transport Layered Security (TLS) based HTTPS using an and security API key or through Oauth authorizationonly.

Preventing Unauthorized Product Access. Outsourced processing: SyncForce Keeper Security hosts its Service with outsourced cloud infrastructure outsourced, US-based data center providers. Additionally, SyncForce Keeper Security maintains contractual relationships with vendors in order to provide the Service in accordance with our Data Processing AgreementService. SyncForce Keeper Security relies on contractual agreements, privacy policies, and vendor compliance programs in order to protect assure the protection of data processed or stored by these vendors. Physical and environmental security: SyncForce Keeper Security hosts its product infrastructure with multi-tenant, outsourced infrastructure data center providers. The physical and environmental security controls are audited for SOC 2 Type II and ISO 27001 compliance, among other certifications. Authentication: SyncForce Keeper Security implemented a uniform password policy for its customer products. Customers who interact with the products via the user interface must authenticate before accessing non-public customer data. Authorization: Customer data is stored in multi-tenant storage systems accessible to Customers via only application user interfaces and application programming interfaces. Customers are not allowed direct access to the underlying application infrastructure. The authorization model in each of SyncForceKeeper Security’s products is designed to ensure that only the appropriately assigned individuals can access relevant features, views, and customization options. Authorization to data sets is performed through validating the user’s permissions against the attributes associated with each data set. Application Programming Interface (API) access: Public product APIs may be accessed using an API key or through Oauth authorization.

Preventing Unauthorized Product Access. Outsourced processing: SyncForce Contexxt hosts its Service with outsourced cloud infrastructure providers. Additionally, SyncForce Contexxt maintains contractual relationships with vendors in order to provide the Service in accordance with our Data Processing Agreement. SyncForce Contexxt relies on contractual agreements, privacy policies, and vendor compliance programs in order to protect data processed or stored by these vendors. Physical and environmental security: SyncForce Contexxt hosts its product infrastructure with multi-tenant, outsourced infrastructure providers. The physical and environmental security controls are audited for SOC 2 Type II and ISO 27001 compliance, among other certifications. Authentication: SyncForce Contexxt implemented a uniform password policy for its customer products. Customers who interact with the products via the user interface must authenticate before accessing non-public customer data. Authorization: Customer data Data is stored in multi-tenant storage systems accessible to Customers via only application user interfaces and application programming interfaces. Customers are not allowed direct access to the underlying application infrastructure. The authorization model in each of SyncForceContexxt’s products is designed to ensure that only the appropriately assigned individuals can access relevant features, views, and customization options. Authorization to data sets is performed through validating the user’s permissions against the attributes associated with each data set. Application Programming Interface (API) access: Public product APIs may be accessed using an API key or through Oauth authorization.

Preventing Unauthorized Product Access. Outsourced processing: SyncForce Zapflow hosts its Service Ecosystem with outsourced cloud infrastructure providersprovider. Additionally, SyncForce ▇▇▇▇▇▇▇ maintains contractual relationships with vendors in order to provide the Service in accordance with our this Data Processing AgreementAd- dendum. SyncForce Zapflow relies on contractual agreements, privacy policies, and vendor compliance com- pliance programs in order to protect data processed or stored by these vendors. Physical and environmental security: SyncForce Zapflow hosts its product infrastructure with multi-tenant, outsourced infrastructure providers. The physical and environmental security se- curity controls are audited for SOC 2 Type II and ISO 27001 compliance, among other certifications. Authentication: SyncForce implemented a uniform password policy for its customer products. Customers and Vendors who interact with the products via the user interface must authenticate before accessing non-public customer data. Authorization: Customer data Data is stored in multi-tenant storage systems accessible to Customers via only application user interfaces and application programming interfacesinter- faces. Customers are not allowed direct access to the underlying application infrastructureinfra- structure. The authorization model in each of SyncForceZapflow’s products is designed to ensure that only the appropriately assigned individuals can access relevant features, views, and customization options. Authorization to data sets is performed through validating the user’s permissions against the attributes associated with each data set. Application Programming Interface (API) access: Public product APIs may be accessed ac- cessed using an API key or through Oauth authorization.

Preventing Unauthorized Product Access. Outsourced processing: SyncForce CloudBerry hosts its Service with outsourced cloud infrastructure providers. Additionally, SyncForce CloudBerry maintains contractual relationships with vendors in order to provide the Service in accordance with our Data Processing Agreement. SyncForce CloudBerry relies on contractual agreements, privacy policies, and vendor compliance programs in order to protect data processed or stored by these vendors. Physical and environmental security: SyncForce CloudBerry hosts its product infrastructure with multi-multi- tenant, outsourced infrastructure providers. The physical and environmental security controls are audited for SOC 2 Type II and ISO 27001 compliance, among other certifications. Authentication: SyncForce CloudBerry implemented a uniform password policy for its customer products. Customers who interact with the products via the user interface must authenticate before accessing non-public customer data. Authorization: Customer data is stored in multi-tenant storage systems accessible to Customers via only application user interfaces and application programming interfaces. Customers are not allowed direct access to the underlying application infrastructure. The authorization model in each of SyncForceCloudBerry’s products is designed to ensure that only the appropriately assigned individuals can access relevant features, views, and customization options. Authorization to data sets is performed through validating the user’s permissions against the attributes associated with each data set. Application Programming Interface (API) access: Public product APIs may be accessed using an API key or through Oauth authorization.