Snapshot 64327

Document

Subprocessor list

URL

https://www.metarouter.io/sub-processors

Fetched

2026-10-08 12:39:31 UTC

HTTP status

200

Content type

text/html; charset=utf-8

Fetch mode

static

Size

107497 bytes

SHA-256 (raw)

8d6a0d521ba2175880024f9c7de89e291f8a5acddc3e3b475efc11b31a5e3090

SHA-256 (normalized text)

277ede0ddaf2a4ed5bd8f30d0b8170472c2ce3c48600e6246f12eee7e2331511

Normalized text

Scripts and page chrome removed; this is what change detection compares.

We engage a limited number of trusted third-party service providers (sub-processors) to support the delivery of our services. These sub-processors may process customer data only as necessary to provide their services to us. Below is a list of sub-processors included in our Data Processing Agreement (DPA) and the type of data they may access.
Sub-Processor
Purpose / Role
Type of Data Processed
Address
Cloudflare
DNS and network performance
DNS data, which may include end-user IP addresses
101 Townsend St., San Francisco, CA, 94107, United States
Google Cloud Platform (GCP)
Infrastructure hosting (MetaRouter-hosted environments only)
Customer behavioral data including event metadata
1600 Amphitheatre Parkway, Mountain View, CA 94043, United States
Microsoft Azure
Infrastructure hosting (MetaRouter-hosted environments only)
Customer behavioral data including event metadata
One Microsoft Way, Redmond, Washington 98052, United States
Amazon Web Services (AWS)
Infrastructure hosting (MetaRouter-hosted environments only)
Customer behavioral data including event metadata
410 Terry Avenue North, Seattle, WA 98109-5210, United States
Note: Sub-processors are only applicable to MetaRouter-hosted environments. If you deploy MetaRouter in a self-hosted configuration, these sub-processors may not apply.