Users
Protect access
Keep credentials private and use only authorized features.
Terms of use
Clear responsibilities for using the platform.
These terms explain the responsibilities of users, organizations, platform administrators, and deployment operators when managing accounts, project data, codebases, and service operations.
Terms at a glance
The main areas covered by this agreement
01
Responsible access
Use verified accounts and respect assigned roles.
02
Accurate project data
Organizations remain accountable for records entered by their members.
03
Safe operations
Production services and recovery actions require authorized oversight.
Agreement structure
The terms follow the way the platform is actually operated.
Responsibilities are separated across individual accounts, organization tenants, platform administration, and the infrastructure used to run the service.
Organizations
Maintain accuracy
Review members, roles, project records, and deployments.
Operators
Run safely
Manage infrastructure, recovery, backups, and administrative actions.
01
Acceptable use
Use the platform for legitimate software development, consulting, and project delivery. Do not use it to enter false records, impersonate users, or bypass role restrictions.
02
Account responsibility
Users are responsible for keeping credentials private, verifying account email addresses, and signing out of shared devices. Organization owners are responsible for inviting the right staff and reviewing role assignments.
03
Project data accuracy
Organizations are responsible for the accuracy of project requirements, code repositories, deployment configurations, and client deliverables entered by their members.
04
Platform administration
Platform administrators may review workspace applications, manage access controls, configure integrations, and review audit records for operational safety.
05
Service operations
Production deployments depend on configured hosting, CI/CD pipelines, DNS, SSL, and monitoring services. Operators should review backups, delivery, storage, and audit records.
06
Support and recovery
Emergency recovery may require approved administrative procedures, such as workspace bootstrap or database index setup. These should be used only by authorized operators.
Responsible operation
Authorized users and operators should act within their assigned responsibilities.
Administrative scripts, platform-level actions, role changes, deployment procedures, and recovery actions should only be performed by people with the appropriate authority and operational context.