Last Modified: April 6th, 2021
Subscribe to RSS Feed for updates.
productboard, Inc. (“productboard”) uses certain subprocessors and content delivery networks to assist it in providing the productboard Services as described in the Terms of Service (“Terms”). Defined terms used herein shall have the same meaning as defined in the Terms.
A subprocessor is a third party data processor engaged by productboard, who has or potentially will have access to or process Service Data (which may contain Personal Data). productboard engages different types of subprocessors to perform various functions as explained in the tables below. productboard refers to third parties that do not have access to or process Service Data but who are otherwise used to provide the Services as “subcontractors” and not subprocessors.
productboard undertakes to use a commercially reasonable selection process by which it evaluates the security, privacy and confidentiality practices of proposed subprocessors that will or may have access to or process Service Data.
productboard requires its subprocessors to satisfy equivalent obligations as those required from productboard (as a Data Processor) as set forth in productboard’s Data Processing Agreement (“DPA”), including but not limited to the requirements to:
This policy does not give Subscribers any additional rights or remedies and should not be construed as a binding agreement. The information herein is only provided to illustrate productboard’s engagement process for subprocessors as well as to provide the actual list of third party subprocessors and content delivery networks used by productboard as of the date of this policy (which productboard may use in the delivery and support of its Services).
If you are a productboard Subscriber and wish to enter into our DPA, please email us at email@example.com.
For all Subscribers who have executed productboard’s standard DPA, productboard will provide notice via this policy of updates to the list of subprocessors that are utilized or which productboard proposes to utilize to deliver its Services. productboard undertakes to keep this list updated regularly to enable its Subscribers to stay informed of the scope of subprocessing associated with the productboard Services.
Pursuant to the DPA, a Subscriber can object in writing to the processing of its Personal Data by a new subprocessor within thirty (30) days after updating of this policy and shall describe its legitimate reasons to object. If Subscriber does not object during such time period the new subprocessor(s) shall be deemed accepted.
If a Subscriber objects to the use of a subprocessor pursuant to the process provided under the DPA, productboard shall have the right to cure the objection through one of the following options (to be selected at productboard’s sole discretion):
(a) productboard will cease to use the subprocessor with regard to Personal Data;
(b) productboard will take the corrective steps requested by Subscriber in its objection (which remove Subscriber’s objection) and proceed to use the subprocessor to process Personal Data; or
(c) productboard may cease to provide or Subscriber may agree not to use (temporarily or permanently) the particular aspect of a productboard Service that would involve the use of the subprocessor to process Personal Data.
Termination rights, as applicable and agreed, are set forth exclusively in the DPA.
The following is an up-to-date list (as of the date of this policy) of the names and locations of productboard subprocessors and content delivery networks:
productboard owns or controls access to the infrastructure that productboard uses to host Service Data submitted to the Services, other than as set forth below. Currently, the productboard production systems for the Services are located in co-location facilities in the United States. The Subscriber’s Service Data remains in that region, but may be shifted among data centers within a region to ensure performance and availability of the Services. The following table describes the countries and legal entities engaged in the storage of Service Data by productboard.
|Entity Name||Entity Type||Entity Country|
|Amazon Web Services, Inc.||Cloud Service Provider||United States
productboard works with certain third parties to provide specific functionality within the Services. These providers are the Subprocessors set forth below. In order to provide the relevant functionality these Subprocessors access Service Data. Their use is limited to the indicated Services.
|Entity Name||Entity Type||Entity Country|
|Mandrill by The Rocket Science Group, LLC||Cloud-based Email Notification Service||United States|
|Pusher, Ltd.||Cloud-based WebSockets Service||United Kingdom|
|Sqreen Inc.||Cloud-based Security Monitoring||United States|
|FullStory, Inc.||Cloud-based Metrics Service||United States|
|Datadog, Inc.||Cloud-based Monitoring Service||United States|
|Sentry, Inc.||Cloud-based Application Monitoring and Error Tracking||United States|
|Confluent.io, Inc||Cloud-based distributed messaging system||United States|
|Tray.io, Inc (only for selected customers who require integration with Tray)||Cloud-based API Integration Platform||United States|
As explained above, productboard’s Services may use content delivery networks (“CDNs”) to provide the Services, for security purposes, and to optimize content delivery. CDNs do not have access to Service Data but are commonly used systems of distributed services that deliver content based on the geographic location of the individual accessing the content and the origin of the content provider. Website content served to website visitors and domain name information may be stored with a CDN to expedite transmission, and information transmitted across a CDN may be accessed by that CDN to enable its functions. The following describes the use of CDNs by productboard’s Services.
|CDN Provider||CDN Location||Entity Country|
|Cloudflare Inc.||Global||United States
|CloudFront by Amazon Web Services, Inc.||Global||United States|