Protect your console account, connection credentials, private keys, signing files, tokens, environment variables, and automation configuration. Do not share accounts or place real secrets in public repositories, public logs, screenshots, or unredacted support requests.
You are responsible for the software you install, configure, and use on the node, including verifying that its licenses permit remote operation, team use, automated builds, or model inference. You bear responsibility for software licenses, code sources, model rights, and data-use permissions.
Maintain independent backups and do not treat a rented node as your only data copy. Store important code, build artifacts, model weights, test data, configuration files, and runtime logs in appropriate locations according to your team's recovery objectives.
Before the term ends, complete data export, stop tasks, rotate keys, and perform any required migration. After the term ends, the order is terminated, or security handling begins, node access may stop. You bear the risk of data becoming unavailable if you do not migrate it in time.
When submitting a support request, provide the order ID, model, node, time of occurrence, impact, reproduction steps, and redacted logs. Do not submit passwords, private keys, complete payment credentials, or other unnecessary sensitive information through tickets or email.
Keep your contact information current and monitor order, term, and service status in the console. Invalid contact details, ignored order status, or failure to handle renewal and migration on time does not change the parties' existing responsibilities.