Sub-Processors

WhisperAPI uses certain sub-processors (including third parties, as listed below) and content delivery networks to assist in providing the WhisperAPI Services as described in our Terms of Service.

What is a Sub-processor?

A sub-processor is a third-party data processor engaged by WhisperAPI, including entities from within WhisperAPI, who has or potentially will have access to or process Customer Content containing personal information. WhisperAPI engages different types of sub-processors to perform various functions as explained in the tables below.

Due Diligence & Contractual Safeguards

WhisperAPI evaluates the security, privacy and confidentiality practices of proposed sub-processors that will or may have access to or otherwise process Customer Content and enters into Data Protection Agreements with each such sub-processor.

This advisory does not give Customers any additional rights or remedies and should not be construed as a binding agreement. The information herein is only provided to illustrate WhisperAPI's engagement process for sub-processors as well as to provide the actual list of third party sub-processors and content delivery networks used by WhisperAPI as of the date of this advisory (which WhisperAPI may use in the delivery and support of its Services).

If you are a WhisperAPI customer and wish to enter into our DPA, please email us at [email protected].

Process to Engage New Sub-processors

WhisperAPI provides notice via this advisory of updates to the list of sub-processors that are utilized, or which WhisperAPI proposes to utilize to deliver its Services. WhisperAPI undertakes to keep this list updated regularly to enable its Customers to stay informed of the scope of sub-processing associated with the Services.

Infrastructure Sub-processors – Service Data Storage and Processing

WhisperAPI owns or controls access to the infrastructure that WhisperAPI uses to host and process Customer Content, other than as set forth herein. Currently, the WhisperAPI production systems used for hosting Customer Content for the Services are in facilities in the United States and Western Europe. The following table describes the countries and legal entities engaged by WhisperAPI in the storage of Service Data. WhisperAPI also uses additional services provided by these sub-processors to process Service Data as needed to provide the Services.

Entity Name Entity Type Entity Country
DigitalOcean Cloud Computing/Data Center Hosting US
Cloudflare Cloud Computing/CDN/Data Storage US/EU
RunPod GPU Processing for Transcriptions US

Service Specific Sub-processors

WhisperAPI works with certain third parties to provide specific functionality within the Services. These providers are the Sub-processors set forth below. In order to provide the relevant functionality these Sub-processors access Customer Content. Their use is limited to the indicated Services.

Entity Name Purpose Entity Country
Google Authentication Provider US
GitHub Authentication Provider US
SimpleAnalytics Analytics EU
Paddle Payment Processing UK

Content Delivery Networks

As explained above, WhisperAPI may use content delivery networks ("CDNs") to provide the Services, for security purposes, and to optimize content delivery. CDNs 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 use of CDNs by WhisperAPI's Services.

CDN Provider Services Using CDN Description of CDN Services CDN Location
Cloudflare All WhisperAPI Services Public website content served to website visitors may be stored with Cloudflare, and transmitted by Cloudflare to website visitors, to expedite transmission. Global

Last updated: April 20, 2025