ORBITRA / SUBPROCESSORS
Subprocessors.
The third parties that process customer personal data on Orbitra's behalf, what they do, and where.
A subprocessor is a third party that Orbitra engages to process customer personal data as part of the Orbitra service. This list forms part of your Data Processing Addendum with Orbitra, which is part of your signed agreement, and customers are notified of changes under it.
We tell customers at least 30 days before a new or replacement subprocessor starts processing their data, and at least 90 days before we move their tenant to a different hosting provider. You can object during that time. If we must replace a subprocessor sooner to keep the service secure or available, we tell you as soon as we can. Moving to another region of the same provider in the same country is not a subprocessor change.
Last updated:
Current subprocessors
The list is being prepared. It will be published here before Orbitra provides the service under a Data Processing Addendum, and changes will then follow the notice rules above.
Not subprocessors
- Destinations a customer configures, such as Slack, Microsoft Teams, a SIEM or a webhook. They act on the customer's instructions and are the customer's vendors.
- AI model keys a customer brings and connects to Orbitra.
- A cloud account the customer owns and controls, where Orbitra is deployed in it.
Upcoming changes
No changes are scheduled.
Change log
No changes yet.
Versions
No published version yet. A dated PDF of each published version will be listed here.
More information and transfers
For more detail about a subprocessor, such as its security certifications or the safeguards for a transfer, email privacy@orbitrasecurity.com.
Follow changes
RSS feed (opens in a new tab)We email customers about changes at the notice address they named in their agreement, as the DPA describes. Anyone else can check this page or follow its change log with the RSS feed (opens in a new tab) ↗; reading the feed shares nothing with us.