Links last opened 8 October 2026. Record confirmed by a person on 7 October 2026. 1 recorded change, listed below.
Chronosphere contracts through Chronosphere, Inc., registered in United States. Its trust center is published at https://chronosphere.io/security-overview/. Its customer data processing agreement, also called a data processing addendum, is published by Chronosphere itself; the link is below. Its sub-processor list is published by Chronosphere itself; the link is below. We open those pages every day — last on 8 October 2026 — and a person last went through this record on 7 October 2026.
A ready row. Replace the purpose with what your client actually uses Chronosphere for.
| Subprocessor | Legal entity | Country | Purpose | Transfer | DPA |
|---|---|---|---|---|---|
| Chronosphere | Chronosphere, Inc. | US | Analytics | — | https://explore.openli.com/privacy/chronosphere/data-processing-agreements |
Changes we noticed on Chronosphere's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.
7 October 2026
We recorded a change to the data processing agreement link.
Enter your website: each service it loads, what it is for and links to its own DPA, in a minute or two. No sign-up.
Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.
Six of them. All analytics in the registry.