LEGAL · SUB-PROCESSORS
A sub-processor list names vendors. None are named on this page yet.
A sub-processor list discloses every vendor that touches data on ORBIS.ID's behalf — hosting, email, key storage — so a customer can see the whole chain rather than take our word for it. Publishing that list before its scope is reviewed with counsel would name a relationship before its terms are settled, so nothing is listed here as a placeholder. What is already true: the key-custody architecture on /company limits what any vendor underneath it can see, and that limit does not depend on which company is named.
What this page is missing, named plainly.
This page depends on a finished, counsel-reviewed sub-processor list, and the register has no row for one — because the list has not been compiled and reviewed yet, not because it is a secret.
The register holds 17 live · 2 partial · 2 planned · 5 not yet.
2 of the 2 capabilities this page depends on have no row in the register yet, so this page will not print a state for them. They are named rather than dropped, because a slice that silently shortens itself is the same defect as a claim with no receipt.
- legal-entity-name
- subprocessor-list
The register route serves, but it carries no row for these yet. List what it does carry:
curl -s https://id.orbis.id/api/site/register | jq -r '.entries[].slug'An empty vendor list is either nobody's business or everybody's secret. This one is neither — it is just not finished.
Straight answers.
- Can I see which vendors process ORBIS.ID data today?
- No, not yet, not here.
- Does the platform's architecture limit vendor exposure regardless of which vendors are used?
- Yes — the key-custody design does not depend on which company runs the infrastructure underneath it.
Do not trust us. Check us.