Legal
Subprocessors
Last updated 31 July 2026
Third parties that process data on behalf of Obsevo Cloud, what each one is used for, and where it runs.
Current subprocessors
| Subprocessor | Purpose | Data involved |
|---|---|---|
| Stripe | Payment processing and subscription management for Cloud | Billing email, customer and subscription identifiers, payment details (collected directly by Stripe; never seen by us) |
| GitHub (Microsoft) | Source hosting, container registry, issue tracking and private vulnerability reports | Anything you choose to include in an issue or a vulnerability report. No customer workflow data |
| Let's Encrypt (ISRG) | TLS certificate issuance | Hostnames only |
What is deliberately absent
There is no analytics provider, no error-tracking service, no session replay, no tag manager, no CDN-hosted fonts and no third-party authentication provider. Not as a policy aspiration — there is no such code in the product or on this website, and you can confirm it from your browser’s network tab or from the source.
Changes
We will update this page before a new subprocessor begins processing customer data. If you have a data processing agreement with us that requires advance notice, that notice period applies.