Subprocessors | TrackQUAL

This page lists the third party subprocessors and service providers that TrackQUAL may use in connection with providing its services.

For the purposes of our Data Processing Addendum, a "Subprocessor" is a third party appointed by TrackQUAL to process Customer Personal Data on behalf of a customer. Some providers listed below are only used in specific circumstances, such as when optional features are enabled, when a particular provider is configured, or when a user interacts with our public brochure website rather than the core TrackQUAL application.

We may update this page from time to time to reflect operational, legal, technical, or commercial changes to our service providers.

1. How to read this page

This section explains the categories used below.

Current means the provider is reflected in the current application stack as an active or primary service provider.
Conditional means the provider is supported by the platform and may be used only where the relevant feature or configuration is enabled.
Brochure only means the provider is used for the public website rather than core customer workflow data.

2. Core platform subprocessors

These are the providers most closely tied to operating the TrackQUAL platform itself.

Provider	Service	Status	Location	Purpose	Typical data involved
Microsoft	Azure App Service / Azure hosting infrastructure	Current	United Kingdom	Application hosting, runtime infrastructure, and service delivery	Customer account data, workflow data, application content, system metadata, and data processed through the hosted application
Microsoft	Azure SQL Database	Current	United Kingdom	Primary application database and structured operational storage	User records, customer and tenant data, returns, repairs, inspections, workflow data, settings, logs, and related business records stored in the platform
Microsoft	Azure Blob Storage	Current	United Kingdom	Storage of uploaded files and media	Attachments, uploaded documents, images, branding assets, and related file metadata
Microsoft	Azure Communication Services Email	Current / Conditional	United Kingdom	Delivery of transactional emails from the platform	Recipient email address, recipient name where applicable, email subject lines, email body content, and related delivery metadata

3. Billing and commercial providers

These providers support subscriptions, invoicing, and billing-related operations.

Provider	Service	Status	Location	Purpose	Typical data involved
Stripe, Inc.	Stripe	Current / Conditional	United States / Global	Subscription billing, checkout, customer billing portal, invoicing, and payment administration	Billing contact details, customer identifiers, subscription records, invoice data, payment-related metadata, and limited account administration data

In some cases, TrackQUAL may act as an independent controller rather than a processor for limited billing, fraud prevention, financial compliance, and account administration data associated with Stripe.

4. Optional or conditional providers

These providers are used where relevant functionality is enabled or configured.

Provider	Service	Status	Location	Purpose	Typical data involved
Microsoft	Azure Translation Services	Conditional	United Kingdom	Translation of platform content and workflow text where translation functionality is enabled	Text submitted for translation, translated output, language settings, and related translation usage metadata
Google LLC	Google reCAPTCHA	Conditional	United States / Global	Bot protection and abuse prevention for public forms such as waitlist and signup flows	IP address, browser and device signals, interaction signals, and submitted captcha tokens
Google LLC	Google Tag Manager / Google Analytics	Conditional / Brochure only	United States / Global	Public website analytics and consent-managed usage measurement	Brochure-site usage data, browser/device data, page interaction data, cookie identifiers, and IP-related analytics signals, subject to consent configuration where applicable

5. Notes on scope

This section clarifies what is and is not included.

This list reflects TrackQUAL's service-provider landscape and may be updated from time to time.
It does not list vendors that appear only as transitive software dependencies unless they are used as actual service providers processing data in connection with the service.
It does not necessarily include Customer's own downstream systems, integrations, or third party services connected by Customer outside the TrackQUAL-controlled service boundary.
Where a provider is marked as conditional, it may not be active in every TrackQUAL environment or customer deployment.
Where a provider is used only for brochure-site functionality, it may fall outside the narrower meaning of "Subprocessor" for certain customer data processing scenarios, but is listed here for transparency where relevant.

6. Questions