Effective: January 1, 2020
To support delivery of our Services, LexBlog, Inc. may engage and use data processors with access to certain Customer Data (each, a “Subprocessor“). This page provides important information about the identity, location and role of each Subprocessor. Terms used on this page but not defined have the meaning set forth in the Terms of Service or superseding written agreement between Customer and LexBlog (the “Agreement“).
Third Parties
LexBlog currently uses third party Subprocessors to provide infrastructure services, and to help us provide customer support and email notifications. Prior to engaging any third party Subprocessor, LexBlog performs diligence to evaluate their privacy, security and confidentiality practices, and executes an agreement implementing its applicable obligations.
Infrastructure Subprocessors
LexBlog may use the following Subprocessors to host Customer Data or provide other infrastructure that helps with delivery of our Services:
| Entity Name | Subprocessing Activities | Entity Country |
| Google LLC | Cloud Service Provider | United States |
| Cloudflare, Inc. | Content Delivery Network | United States |
| New Relic, LLC | Performance Analytics | United States |
| HubSpot, LLC | Customer Relationship Management | United States |
| Segment.io, Inc. | Analytics | United States |
Other Subprocessors
LexBlog may use the following Subprocessors to perform other Service functions:
| Entity Name | Subprocessing Activities | Entity Country |
| Zendesk, Inc. | Cloud-based Customer Support Services | United States |
| Disqus | Cloud-based Commenting System | United States |
| Mailchimp | Email Subscription Provider | United States |
Updates
As our business grows and evolves, the Subprocessors we engage may also change. We will endeavor to provide the owner of Customer’s account with notice of any new Subprocessors to the extent required under the Agreement, along with posting such updates here. Please check back frequently for updates.