Optimizely subprocessors
Every party Optimizely names in its own subprocessor list and DPA annexes. Nothing here is inferred from traffic or page scripts.
SUBPROCESSOR GRAPH
Explore the next levels
See how Optimizely's declared subprocessors connect, level by level.
All declared parties, A–Z
The list as it stood on the last read.
| Subprocessor | Stated purpose |
|---|---|
|
|
Cloud-based Email Services |
|
|
Cloud hosting and infrastructure provider |
|
|
Large language model |
|
|
SMS Delivery (US and Canada only) |
|
|
Tracking for bug resolution |
|
|
Content Delivery Network |
|
|
Observability and Alerting |
|
|
User Session Recording (US region customers only) |
|
|
Google Analytics use is optional and may be enabled. If disabled the Optimizely customer will need to supply their own solution or certain functionality may be limited |
|
|
Cloud Service Provider |
|
|
Large language model |
|
|
SMS Delivery |
|
|
Email rendering testing across browsers |
|
|
Front-end monitoring and session replay |
|
|
SMS Delivery |
|
|
Cloud Service Provider |
|
|
Database |
|
|
User Authentication and Authorization is via OptiID. Customer can optionally bring in their own SSO. |
|
|
Database |
|
|
Customer Data Platform |
|
|
SEO Analytics |
|
|
Cloud-based Email Services |
|
|
Observability - App Event Management |
|
|
Database |
|
|
SMS delivery and RCS messaging |
|
|
Ecommerce Integrations |
|
|
27 declared subprocessors
Back to the Optimizely profile →