Scope
This draft describes the information Horizon AI Runtime may handle while the MVP is developed and operated. It is intentionally limited to the current control-plane, web application, and worker architecture.
Information you provide
When you create an account, Horizon stores your name, email address, and a password hash. Passwords are not stored in plaintext.
Authentication and sessions
Horizon uses a server-side session. A session identifier is sent in an HTTP-only browser cookie, while the control plane stores only a hash of that identifier and an expiration time.
Infrastructure metadata
The platform may store operational metadata needed to represent connected infrastructure and workloads, including worker hardware information, model metadata, deployment configuration, status, and health information.
How information is used
This information is used to authenticate users, operate the control plane, represent deployments, monitor worker and runtime state, and improve the reliability of the MVP.
Worker and model boundaries
Workers communicate with the Control Plane. Workers do not directly connect to the Horizon database. Model weights and local runtime data may remain on the worker machine according to its runtime configuration.
Retention and deletion
Retention practices are still being established for this early MVP. Session records expire, and account or operational data may be retained while needed to operate or debug the service.
Changes
This document may change as Horizon's architecture and product scope develop. Material updates will be reflected on this page.