LEGAL · TERMS OF SERVICE
A contract needs two names on it. This page only has one.
Terms of service bind two named parties, and the second one — the legal entity that runs ORBIS.ID — has not been published yet. Real terms covering usage rights, liability, and the exit clause already promised on Issue are being drafted with counsel, and nothing invented stands in for them here. What already holds without a signed contract: every claim on this site carries its own receipt, and you can check any of them yourself before a single term is agreed to.
What this page is missing, named plainly.
Two things are missing from this page, and both are named rather than guessed at: the legal entity a contract would bind, and the terms document itself. Neither has a row in the register because neither exists yet.
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
- terms-of-service
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'A term nobody signed is not a term. It is a draft, and this page says so.
Straight answers.
- Can I read the terms today?
- No. There is nothing published yet. What you can read is what the platform already does — every page under Trust describes the running system, not a promise about it.
- Does anything on this site depend on a signed contract to work?
- No. Verification, the register, and every endpoint linked from this site work the same way with or without one.
Do not trust us. Check us.