We rely on the following third-party sub-processors. Each is contractually required to handle personal data under appropriate data protection terms.
- Cloudflare, Inc. (US, UK GDPR safeguards via UK IDTA / SCCs): Bot detection (Turnstile) on contact forms.
- Postal (self-hosted mail server, Toronto, Canada): Transactional email delivery (contact form, service notifications). Postal is the open-source MTA software we operate on our own infrastructure in Toronto, Canada; no third-party processing of email content occurs in transit. Canada has a UK adequacy decision for commercial organisations subject to PIPEDA, so no additional transfer safeguards are required for this transfer.
- Amazon Web Services EMEA SARL (Amazon SES) (Luxembourg, with infrastructure in EU/UK regions and possible onward transfers to Amazon Web Services, Inc. in the US under UK IDTA / SCCs): Outbound transactional email delivery for selected message flows. Amazon SES processes email envelope and content data solely to deliver messages on our behalf.
- Google LLC (Google Analytics) (US, UK GDPR safeguards via UK IDTA / SCCs): Website usage analytics, loaded only after cookie consent where required.
- Google LLC (Sign in with Google) (US, UK GDPR safeguards via UK IDTA / SCCs): Single sign-on (SSO) for customer portal authentication, where the customer chooses to sign in using their Google account. Google receives only the authentication assertion required to identify the user and the basic profile fields they choose to share; we do not transmit additional customer personal data to Google for this purpose.
- PeeringDB Inc. (US, UK GDPR safeguards via UK IDTA / SCCs): Single sign-on (SSO) for customer portal authentication, where the customer chooses to sign in using their PeeringDB account. PeeringDB receives only the authentication assertion required to identify the user and the basic profile fields they choose to share; we do not transmit additional customer personal data to PeeringDB.
- Stripe Payments UK, Ltd. (UK, with onward transfers to Stripe, Inc. in the US under UK IDTA / SCCs): Card payment processing (PCI-DSS Level 1 compliant). Full card numbers are tokenised by Stripe and never stored on our systems.
- PayPal (Europe) S.à r.l. et Cie, S.C.A. (Luxembourg, with onward transfers to PayPal, Inc. in the US under UK IDTA / SCCs): Payment processing for customers paying via PayPal. PayPal acts as an independent controller for its own anti-fraud, regulatory, and account-relationship purposes.
- GoCardless Ltd (UK): Direct Debit collection under the Bacs scheme, including Direct Debit mandate setup and payment instruction handling. GoCardless is FCA-authorised as an Authorised Payment Institution.
This list may change as we add or remove providers. Material changes are reflected here. For an up-to-date list please contact legal@pdxnet.co.uk.
7.1 Network Carriers and Internet Exchanges
To deliver IP transit and connectivity services, customer traffic transits a blend of:
- Upstream IP transit providers (a mix of Tier 1 and Tier 2 networks), and
- Internet Exchange Points (IXPs) such as LINX, AMS-IX, and similar UK and European exchanges.
These carriers and exchanges are independent network operators, not our sub-processors. They carry traffic in transit under standard interconnection arrangements.
Traffic telemetry: Some upstream carriers and IXPs collect aggregated traffic telemetry (sFlow, NetFlow, or IPFIX samples) for capacity planning, peering analysis, and abuse handling. We do not control how each carrier or IXP handles this telemetry.
What may be sampled: Packet headers, including source and destination IP addresses, ports, and protocol, may be sampled and processed by these third parties as a normal part of internet routing.
What is not exposed: Application-layer content carried over TLS or other encrypted protocols is not exposed by this telemetry.