Sub-processors
To support +WoundDesk in delivering its Services, +WoundDesk may engage third party service providers to assist +WoundDesk with its data processing activities. When we work with these service providers in our capacity as a data processor, the third-party service provider is a sub-processor of +WoundDesk.
Effective Date: November 22, 2018
This page identifies the Sub-processor, describes where they are located, and what services they provide to us. Prior to engaging any third-party sub-processor, we evaluates their privacy, security and confidentiality practices. We do not engage a sub-processor unless our quality standards are met. +WoundDesk also requires its sub-processors to be bound by written agreements that require them to provide at least the same level of data protection as +WoundDesk makes available under its data processing addendum in compliance with applicable data protection laws.
+WoundDesk currently uses the following Sub-processors:
Entity Name | Location | Sub-processing Activities | Means of lawful transfer of data from the EU |
---|---|---|---|
Amazon Web Services | Washington, USA | Infrastructure and Storage | Privacy Shield and Standard Contractual Clauses |
California, USA | File storage, bug tracking | Privacy Shield and Standard Contractual Clauses | |
MailChimp | Georgia, USA | Customer mail services provider | Privacy Shield and Standard Contractual Clauses |
Sendgrid | Colorado, USA | Transactional mail services provider | Privacy Shield and Standard Contractual Clauses |
Hubspot | Massachusetts, USA | Customer relation management | Privacy Shield and Standard Contractual Clauses |
Stripe | California, USA | Payment services | Privacy Shield and Standard Contractual Clauses |
Metanet | Zurich, Switzerland | Hosting services (international) | - |
Logentries | Dublin, Ireland | Log management and analysis | - |
Sentry | USA | Error tracking | Privacy Shield and Standard Contractual Clauses |
Typeform | Barcelona, Spain | Customer surveys | - |
Updates
Our business needs may change from time to time. For example, we may deprecate a Sub-processor to consolidate and minimize our use of Sub-processors. Similarly, we may add a Sub-processor if we believe that doing so will enhance our ability to deliver our Services. We will periodically update this page to reflect additions and removals to our list of Sub-processors. Please check back frequently for updates.
If you have questions or concerns about a new subprocessor, we’d be happy to help. Please contact us at legal@wounddesk.com.
For more information on +WoundDesk’s privacy practices, please consult our privacy policy.