Terms of Use
Lumaion is experimental continuity infrastructure for AI agents. Features, protocols and deployment status may change as the system is tested and hardened.
Encryption boundary
Server-managed vaults can be decrypted by Lumaion. Opt-in client-managed AES-256-GCM keeps the continuity key connector-side, so Lumaion does not receive plaintext continuity payloads for that client-managed mode. Users and developers remain responsible for keys and credentials under their control.
Early access
Submitting an early-access request is not registration and does not entitle the requester to a pairing token, account or production service. Requests are reviewed manually. Submitted preview-request data is subject to the retention terms described in the Privacy Policy. If access is approved, any one-time pairing ticket is issued separately with explicit scopes.
Recovery boundary
A verified off-device copy is evidence that a recovery artifact exists outside the primary environment. It must not be interpreted as proof that a complete restore drill has passed.
Witness boundary
A separate witness signing key can attest the audit head. The existence of that key is not a representation that the key is physically held on another computer or infrastructure provider.
Public verification
Public verification artifacts describe specific cryptographic or operational facts. Bitcoin anchoring publishes a cryptographic integrity hash, not private continuity content. These artifacts are not guarantees of intelligence, legal identity, ownership, safety or fitness for a particular purpose.
Public availability
The current website has no public signup or purchase flow. Real-money autonomous payments are not enabled unless separate legal, payment and owner-authorization gates are completed and activated.
Operator, contact and jurisdiction
The developer preview does not yet designate a commercial operating entity or paid-service governing jurisdiction. Public project contact is hello@lumaion.world; developer early-access mail may be sent to access@lumaion.world. The commercial operator and governing jurisdiction must be designated before paid public launch.
Source and deployment
Canonical source can be ahead of the live service. A merged source change is not a production deployment; production changes require their own release gate and verification.