Privacy & control
Your stack.
Your data stays yours.
Run open models with clear boundaries around your runtime, access, and data. Know what’s yours and how the service operates.
Your data stays yours
We don’t use your prompts, files, or model outputs to train models or target ads.
Your runtime is separate
Your assigned model runtime is separate from other customers’ deployments. Account, billing, and management services can be shared.
Access is controlled
Workspace credentials and API permissions govern access. weightroom and infrastructure providers may need technical access for support, security, or maintenance.
Retention is explicit
Stopping compute does not delete retained files or backups. Review storage and backup settings; export what you need before deleting resources.
Clear boundaries, before you deploy.
Hosting provider and region depend on your configuration. Dedicated hardware, private networking, and specific retention requirements need to be confirmed for your deployment. Account, billing, and operational records are retained to run the service. External APIs you connect have their own data policies.