T-Pro

tpro.io

T-Pro declares 4 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Amazon Web Services, Microsoft and HubSpot. No published changes since we first read it on Nov 7, 2026.

Subprocessors CSV of T-Pro's subprocessors · Atom feed of T-Pro's subprocessors DORA draft CSV of T-Pro's subprocessors as declared by T-Pro what's this? · 

4 third parties.

NamePurposeLocationListed since
Amazon Web Services AI
AWS provides the cloud infrastructure for the T-Pro platform, including compute, storage, networking and database services. Production data is hosted in the AWS region approved for each deployment. The standard environment for the UK, Ireland and EU is eu-west-1 (Ireland) and the standard environment for Australia and New Zealand is ap-southeast-2 (Sydney). Amazon Bedrock, an AWS service, provides the generative AI inference used by T-Pro Scribe. The model runs within AWS in the approved region. Prompts and outputs are not shared with the model provider and are not used to train their models. Data is encrypted in transit using TLS and at rest using AES-256 with keys managed in AWS KMS.; Cloud hosting and infrastructure
EU (Ireland) and Australia (Sydney)
ClickHouse
ClickHouse Cloud hosts T-Pro’s reporting and analytics database. Selected reporting fields, including identifiers and workflow metadata, are replicated from the production platform so customers and T-Pro can report on documentation volumes, turnaround and system performance. Clinical transcription text and NLP content are not replicated to ClickHouse under the current implementation. Data is encrypted in transit and at rest, and deletions in the source platform propagate to ClickHouse so that removed records are not retained in the analytics copy.; Reporting and analytics
EU (Ireland)
HubSpot
CRM and Marketing; HubSpot is T-Pro’s customer relationship management and marketing platform. It holds business contact details for customers, prospects and partners, along with records of commercial correspondence. HubSpot is not part of the clinical processing path. Patient clinical content is not stored in HubSpot.
EU
Microsoft
Collaboration and Productivity; Microsoft 365 provides T-Pro’s email, document storage, and Teams collaboration. It is used for corporate communication, internal documentation and customer correspondence, including support and account management. Microsoft 365 is not part of the clinical processing path and is not used as a store for patient clinical records. Access is controlled by role, protected with multi-factor authentication, and logged.
EU (Ireland)

Web TechnologiesCSV of T-Pro's web technologies · Atom feed of T-Pro's web technologies

T-Pro's homepage made 350 requests to 19 domains, and 4 services controlled by another company.

Analytics (4): Google Cloud, HubSpot, LinkedIn; usually detected as Analytics: Cloudflare

4 third parties by category: Analytics 4

Third parties 4 · 67 requests
Google Cloud DoubleClick Floodlight Google Analytics Google Call Conversion Tracking Google Tag Manager 8% of the page's requests 29
HubSpotsubprocessor HubSpot HubSpot Analytics HubSpot Chat 8% of the page's requests 29
Cloudflare cloudflare.com 2% of the page's requests 6
LinkedIn Linkedin Insight Tag <1% of the page's requests 3
First party 1 · 283 requests
T-Pro Font Awesome 6.5.1 Google Font API HSTS HubSpot CMS Hub HubSpot Cookie Policy Banner Node.js Open Graph Slick Socket.io cdnjs jQuery 3.7.1 jQuery Migrate 3.6.0 81% of the page's requests 283

3 tracked companies loaded by the homepage are not in T-Pro's subprocessor list. A website can use a service without it processing customer data.

ComplianceCSV of T-Pro's compliance · Atom feed of T-Pro's compliance

Certified
Says it complies with

Certifications as T-Pro's trust center lists them; reports are usually shared on request (evidence)

Service statusCSV of T-Pro's status page incidents · Atom feed of T-Pro's status page incidents

Aug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: before our history of this status pageOct 1: before our history of this status pageOct 2: before our history of this status pageOct 3: before our history of this status pageOct 4: before our history of this status pageOct 5: before our history of this status pageOct 6: before our history of this status pageOct 7: before our history of this status pageOct 8: before our history of this status pageOct 9: before our history of this status pageOct 10: before our history of this status pageOct 11: before our history of this status pageOct 12: before our history of this status pageOct 13: before our history of this status pageOct 14: before our history of this status pageOct 15: before our history of this status pageOct 16: before our history of this status pageOct 17: before our history of this status pageOct 18: before our history of this status pageOct 19: before our history of this status pageOct 20: before our history of this status pageOct 21: before our history of this status pageOct 22: before our history of this status pageOct 23: before our history of this status pageOct 24: before our history of this status pageOct 25: before our history of this status pageOct 26: before our history of this status pageOct 27: before our history of this status pageOct 28: before our history of this status pageOct 29: before our history of this status pageOct 30: before our history of this status pageOct 31: before our history of this status pageNov 1: before our history of this status pageNov 2: before our history of this status pageNov 3: before our history of this status pageNov 4: before our history of this status pageNov 5: before our history of this status pageNov 6: before our history of this status pageNov 7: before our history of this status pageNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

No incidents reported since Nov 8, 2026

As T-Pro's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Incidents reported by T-Pro's subprocessorsCSV of incidents reported by vendors T-Pro lists · Atom feed of incidents reported by vendors T-Pro lists

8 reported incidents in the last 30 days, by 2 of the vendors T-Pro lists as subprocessors.

A subprocessor list names a company, not the service an incident touched. This does not show that T-Pro was involved.

DateCompanyIncidentImpactLasted
ClickHouseProvisioning and scaling operations may take longer in AWS ap-northeast-1 Tokyo minor7 h 38 min
HubSpotSome HubSpot tools may be unavailable for some users no impact stated51 min
ClickHouseSQL Console database connection outage minor49 min
HubSpotHubSpot is experiencing issues no impact stated22 min
HubSpotSome HubSpot tools may be unavailable for some users no impact stated2 h 47 min
ClickHouseDegraded support ticket submission and response minor2 h 47 min
HubSpotUpdate on PHP security vulnerability no impact stated1 h 53 min
ClickHouseGoogle Cloud Outage minor6 h 44 min

Who is around them.

ChangesCSV of T-Pro's changes · Atom feed of T-Pro's changes

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for T-Pro's site

T-Pro transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/t-pro"><img src="https://thirdpartyindex.com/badge/t-pro.svg" alt="T-Pro transparency rating on Third Party Index" height="20"></a>
[![T-Pro transparency rating on Third Party Index](https://thirdpartyindex.com/badge/t-pro.svg)](https://thirdpartyindex.com/vendors/t-pro)