Subprocessors

Subprocessor information should stay enumerable.

The public subprocessors route exists to make external processing dependencies legible when they matter.

Subprocessors

Subprocessor coverage should be explicit and updateable.

The route should clarify what kind of third-party processing surfaces exist and where questions should go.

Subprocessors

What subprocessors list should communicate

It should state the role of third-party providers without turning into a vague vendor cloud page.

Utility surface

Operational vendors

List relevant third-party processors or point to the maintained record.

Scope boundary

Differentiate website operations from enterprise deployment-specific discussions.

Contact route

Complex questions should route to privacy or enterprise channels.

Reference routes

Related policy routes

Subprocessors should stay connected to privacy and DPA surfaces.

Privacy Policy

Open

Public privacy scope and contact posture.

DPA

Open

Contract-led processing terms.

Contact Sales

Open

Enterprise route for detailed deployment questions.