Service Terms
Product, package, provisioning, connector, support, usage, and service-specific terms for OmegaOS.
Published following operator-authorized Omega privacy, security, claims, and operational review. External counsel review is not recorded.
Service Terms is operator-authorized for public publication. External counsel approval is not recorded and remains recommended before material commercial or regulatory reliance.
Order of precedence
A signed master agreement, order form, DPA, security addendum, or SLA controls for its subject matter. These Service Terms supplement the Terms of Use and the package or checkout terms presented at purchase.
Packages and scope
Each package identifies included products, environments, capacity, usage, support, implementation, and commercial limits. Package names and availability may change. The package recorded in Omega's commercial system and the customer's accepted order control over marketing summaries.
Provisioning
Provisioning may require verified customer information, payment, administrator designation, security configuration, domain or identity setup, and connector authorization. Estimated dates depend on customer cooperation, provider availability, and agreed implementation scope.
Usage and capacity
Services may be limited by users, environments, execution capacity, concurrency, storage, model or tool usage, connectors, or other metered activity. Omega may enforce limits, quote additional usage, or require a package change. Internal metering records support service operation, billing, and dispute review.
Connectors and customer systems
The customer authorizes access only to systems and data it controls or may lawfully use. The customer is responsible for third-party licenses, permissions, source-system changes, and connector configuration. Omega may pause a connector that is insecure, unsupported, rate-limited, or no longer authorized.
Implementation and acceptance
Implementation deliverables, dependencies, acceptance criteria, and change control are defined in the order or statement of work. Silence is not acceptance unless the signed document says so. Work outside scope requires a new estimate or order.
Support
Support channels, hours, severity handling, response objectives, and escalation depend on the package or signed support schedule. Public contact forms and email do not create an uptime or resolution commitment beyond the controlling agreement.
Beta and preview services
Beta and preview capabilities may change, lack features, contain defects, or have additional limits. They are provided for evaluation unless the order expressly authorizes production use. Omega may require feedback, migration, or discontinuation.
Changes and dependencies
Omega may update services to improve security, reliability, usability, legal compliance, or provider compatibility. Omega will use reasonable efforts to provide notice of a material reduction in contracted functionality and will follow the signed agreement for material adverse changes.
Billing records
Checkout, invoice, subscription, usage, credit, refund, and revenue records are maintained through Omega's commercial and finance boundaries. A receipt or dashboard estimate does not override the accepted order, payment-provider record, or applicable tax document.
Read this page with the related policy, trust, and service information that applies to your use of Omega.