Legal

Privacy Policy

This page describes the basic data handling expectations for the public run9 service.

1. Information we collect

run9 stores the account and organization information required to authenticate users, issue API keys, attribute actions, and operate the service. This includes your primary email address, password hash when applicable, display name, organization memberships, and audit records for significant account activity.

The service may also retain operational metadata that is necessary to show resource status, keep work attributable to the correct user or organization, and diagnose failures in the product.

2. How we use information

We use collected information to provide the service, secure access, issue sessions and API keys, render account and organization settings, and maintain auditable records of significant actions.

When an organization is configured with email-domain auto-join, your login email domain may be checked to decide whether you should be added to that organization.

3. Retention and security

Account and organization records are retained as long as they are needed to operate the service or comply with legitimate operational and legal requirements. Temporary registration records created for email verification expire automatically.

Passwords are stored as hashes rather than plaintext. No public-facing system can promise perfect security, so you should use a unique password and protect your API keys and other credentials.

4. Contact

Questions about this policy or data handling for the live run9 deployment should be directed to the operator of the service through the project's normal support channels.