Version 1.7. Effective 3 November 2026.
Authorized subprocessors
| Subprocessor | Location | Function |
|---|---|---|
| Amazon Web Services, Inc. | United States / global network; selected AWS check locations | Hosting, storage, content delivery, email and SMS; checks from the AWS locations you select |
| Stripe, Inc. | United States | Payments and billing |
| Stytch, Inc. | United States | Authentication and identity |
| Cloudflare, Inc. | United States / global network | Bot protection (signup and contact form) |
| Google Cloud (Google LLC) | United States / global network; selected Google Cloud check locations | Sign-in with Google, push notifications to Android devices and page speed tests; checks from the Google Cloud locations you select, including all ping checks |
| Microsoft Azure (Microsoft Corporation) | Selected Azure check locations | Checks from the Azure locations you select |
| Whoxy | Vendor infrastructure | WHOIS / domain expiry |
| Zoho Corporation | United States | Inbound support email |
| Slack Technologies, LLC | United States | Internal ops alerts; customer Slack alerts if enabled |
Other alert destinations you configure yourself (PagerDuty, Discord, Teams, Telegram, webhooks, and similar) are recipients you choose, not our subprocessors. Telegram delivers alerts to the chat you link under its own terms and offers no data processing agreement.
Marketing-site tools (analytics, ads measurement, session recording, affiliate attribution, contact form host, docs hosting, marketing email) are described in our Privacy Policy and Cookie Policy. They do not process customer product monitoring data.
Available check locations, with their country and provider, are listed on our locations page. Check results, including browser-check screenshots, HAR files and video, are stored in AWS us-east-1 in the United States.
Changelog
| Effective | Version | Change |
|---|---|---|
| 3 November 2026 | 1.7 | Removed WhoisXML API, Inc., which we no longer use. Domain expiry checks ask the domain’s registry first and Whoxy only when the registry cannot answer. |
| 1 November 2026 | 1.6 | Listed Google and Microsoft by cloud provider, as Google Cloud and Microsoft Azure, and described each provider’s function in general terms. Google Cloud’s function now includes sign-in with Google and push notifications to Android devices. The Amazon Web Services location now includes its global content delivery network. |
| 22 October 2026 | 1.5 | Added TCP port checks to the check functions of Amazon Web Services, Google Cloud and Microsoft Azure. Google Cloud also runs ping (ICMP) checks, which run only on Google Cloud locations; a ping monitor with no selected location runs from Google Cloud in the United States. New Google Cloud check locations in the United States, Chile, Germany, the Netherlands, India and Australia. |
| 21 October 2026 | 1.4 | Amazon Web Services now also runs browser checks from the AWS check locations you select. Their results, screenshots, HAR files and video are stored in AWS us-east-1. |
| 12 October 2026 | 1.3 | Removed Telegram. Telegram is a recipient you choose for alerts, like Discord or Teams, and not a Site Qwality subprocessor. It offers no data processing agreement. |
| 9 October 2026 | 1.2 | Added Google Cloud and Microsoft Azure for customer-selected HTTP check locations, and regional AWS check processing. |
| 12 August 2026 | 1.1 | Shortened the public list to vendor, location and function only. Detailed operational descriptions moved out of the public page. |
| 9 August 2026 | 1.0 | First published as a standalone page. Product email is Amazon SES; Mailgun and SendGrid decommissioned on the product notification domain. |
Questions: privacy@siteqwality.com.