Terms of Service

Terms of Service

These Terms of Service (“Terms”) govern access to and use of Ethen, a model workspace operated by Upcube (“Upcube,” “we,” “us,” or “our”). By creating an account, accessing a workspace, submitting prompts or files, connecting services, configuring BYOK, or otherwise using Ethen, you agree to these Terms and the related policies referenced here. If you use Ethen on behalf of an organization, you represent that you have authority to bind that organization.

1. Who may use Ethen

Ethen is intended for users and organizations that can lawfully enter into these Terms and that will use the product for legitimate model work such as drafting, coding assistance, research organization, routing, review, workflow design, and related productivity tasks. You must provide accurate account information, keep credentials secure, and use Ethen only in compliance with applicable law, these Terms, the Acceptable Use Policy, and any enterprise agreement that applies to your organization. If you are under the age of majority in your jurisdiction, you may use Ethen only with the involvement of a parent, guardian, or other authorized adult where permitted by law and by product eligibility rules. Organizations are responsible for deciding which employees, contractors, and guests may access a workspace, what permissions they receive, and what internal policies govern prompts, files, connected services, and approvals. Upcube may refuse, suspend, or limit access where required for security, legal, or abuse-prevention reasons.

• Users must be able to lawfully accept these Terms.
• Organizations control who may access their workspaces.
• Eligibility and access may be limited for security or legal reasons.

2. Accounts and account responsibility

You are responsible for activity that occurs under your account credentials, API keys, session tokens, and authorized integrations, except to the extent caused by Upcube’s verified system failure. You must protect passwords, multi-factor authentication factors, recovery methods, personal access tokens, and any secrets stored in environment settings or secret stores you control. If you believe an account, key, or session has been compromised, you should revoke or rotate credentials where available, end active sessions, and notify Upcube through published support or security contact paths. Shared credentials are discouraged. Team access should use individual identities and role-based permissions where the product provides them. You agree not to bypass authentication, probe for unauthorized access, or use another person’s account without permission. Upcube may require identity verification, organization domain controls, or additional security measures for certain features or risk levels.

• Account holders are responsible for credential security.
• Compromised credentials should be rotated and reported.
• Shared logins are discouraged in favor of individual identities.

3. Workspace access and permissions

Ethen organizes work inside workspaces, projects, sessions, or similar containers depending on product surface. Workspace owners and admins are responsible for inviting members, assigning roles, managing connected services, configuring model routes, and reviewing approvals or evidence records when those features are enabled. Access control is a shared responsibility. Upcube provides product mechanisms for authentication and authorization where implemented. Customers decide who is invited, which external systems are connected, which secrets are stored, and which workflows may perform state-changing actions. Guests and temporary collaborators should receive the minimum access required for the task. When a member leaves an organization, admins should revoke access promptly, review remaining secrets and integrations, and reassign ownership of critical projects. Upcube does not independently police every internal personnel change.

• Admins control invites, roles, and integrations.
• Least-privilege access is recommended.
• Offboarding is a customer operational responsibility.

4. User content

“User Content” means prompts, instructions, messages, uploaded files, code, images, audio, transcripts, comments, workflow definitions, labels, metadata you provide, and similar materials submitted to or created inside Ethen by you or people acting on your behalf. You retain rights in User Content that you already own, subject to the licenses needed for Upcube to operate the service. You grant Upcube a limited license to host, process, transmit, display, store, and otherwise use User Content only as needed to provide, secure, maintain, troubleshoot, and improve the service in accordance with the Privacy Policy and product settings. You represent that you have the rights, permissions, and lawful basis needed to submit User Content, including content involving other people, employers, customers, or regulated data. Do not submit content you are not allowed to process in a model workspace.

• Users keep ownership of content they already own.
• Upcube needs a limited operational license to run the service.
• Users must have rights to submit the content they provide.

5. Prompts, outputs, and files

Prompts and files you submit may be routed to models, tools, connected services, local runtimes, or approval workflows depending on configuration. Outputs generated by models or tools may be inaccurate, incomplete, insecure, biased, outdated, or otherwise unsuitable. Files may be parsed, indexed for retrieval within a workspace context, attached to runs, or included in evidence packages when those features are used. You are responsible for reviewing outputs before relying on them, shipping them, publishing them, or using them to take action in production systems. Generated code should be reviewed for security, correctness, licensing, and operational impact. Generated text, media, or voice should be reviewed for factual accuracy, rights clearance, and misuse risk. Do not treat model confidence language as a warranty. Different models and routes may produce different results for the same prompt. Upcube does not guarantee that any particular output is original, non-infringing, correct, or fit for a particular purpose.

• Outputs require human review before reliance.
• Files and prompts may follow configured processing paths.
• No warranty of correctness or originality is provided for model output.

6. Model output limitations

Ethen is a model workspace and coordination layer. It does not convert model output into professional advice merely because a prompt asks for legal, medical, financial, safety, employment, immigration, or other specialized guidance. High-impact decisions should be reviewed by qualified humans and governed by your organization’s policies. Security findings, vulnerability suggestions, remediation advice, and dual-use technical content can be incomplete or wrong. Treat them as starting points for investigation, not as certified assessments. Creative and media outputs may raise copyright, trademark, publicity, or privacy issues depending on inputs and use. The AI Use Policy provides additional guidance on human review, professional boundaries, generated code, security work, creative content, voice features, and automated actions. These Terms incorporate that policy by reference for product-use expectations.

• Model output is not professional advice by default.
• High-impact decisions need qualified human review.
• The AI Use Policy is part of product-use expectations.

7. Third-party model providers

Ethen may route requests to third-party model, tool, storage, voice, or infrastructure providers. Provider availability, latency, content filters, rate limits, outages, and policy enforcement are outside Upcube’s exclusive control. Provider terms, acceptable use rules, and privacy practices may apply to processing performed on their systems. When a request is sent to a provider, that provider may process prompts, files, outputs, and related metadata according to its terms and your configuration. Upcube can describe routing posture and product controls, but it does not restate or guarantee every provider policy. You should review provider documentation relevant to your use case, especially for regulated or confidential work. Provider changes, deprecations, and safety interventions may affect results. Upcube may update model catalogs, default routes, or availability labels as product and provider conditions change.

• Third-party providers process some workloads.
• Provider terms and availability may apply independently.
• Catalogs and routes can change over time.

8. BYOK (bring your own key)

Where BYOK is supported, you may connect your own provider accounts or credentials so that selected requests are billed and authenticated through those accounts. BYOK gives customers control over provider account selection, but provider-side terms, billing, logs, and retention may still apply. You are responsible for the accuracy, security, rotation, scopes, and lawful use of keys or tokens you supply. You must ensure the provider account is authorized for the intended workloads and that your organization accepts the provider’s commercial and privacy terms. Upcube is not responsible for unexpected provider charges created by your keys, automation, retries, or team usage. If a key is revoked, expired, mis-scoped, or rate-limited, related routes may fail. Admins should treat BYOK credentials as sensitive secrets and limit who can view or change them.

• BYOK uses customer-managed provider credentials.
• Provider billing and logs may still apply under BYOK.
• Customers control rotation, scopes, and account authorization.

9. Connected services

Ethen may allow connections to repositories, cloud storage, issue trackers, communication tools, browsers, local runtimes, or other services. Connected services expand what a workspace can read or change. You are responsible for authorizing only the integrations you intend, reviewing scopes, and disconnecting services that are no longer needed. Actions taken through connected services—such as creating issues, writing files, sending messages, or opening pull requests—may have real-world effects. Use approval workflows, least privilege, and human review for state-changing actions. Upcube does not assume responsibility for external system changes authorized through your account configuration. Connected-service credentials and tokens should be stored using the product’s supported secret mechanisms where available. Do not paste long-lived secrets into ordinary prompts if a dedicated secret path exists.

• Integrations require intentional authorization.
• State-changing actions can affect external systems.
• Secrets should use supported storage paths where available.

10. Workflows, approvals, and evidence

Some Ethen surfaces support workflows, approval packets, receipts, run logs, and evidence records. These features are designed to make model work more inspectable. They do not guarantee that a decision was correct, that a policy was satisfied, or that an automated step should be trusted without review. Users who approve actions are responsible for understanding what they approve. Organizations should define who may approve risky operations, what evidence must be retained, and when a human must intervene. Evidence records may include prompts, tool traces, diffs, findings, comments, or status metadata depending on the feature. Do not treat an approval checkbox as a substitute for domain expertise. If a workflow is experimental or preview in product UI, treat it as unfinished capability and avoid production-critical reliance until your organization accepts the risk.

• Approvals and evidence support review, not guaranteed correctness.
• Organizations should define approval authority.
• Preview workflow features require extra caution.

11. Acceptable use

You must comply with the Acceptable Use Policy. Prohibited uses include illegal activity, fraud, malware development or deployment, unauthorized access, credential theft, abusive surveillance, exploitation, prohibited weapons assistance, and other harmful categories described in that policy. Upcube may investigate suspected abuse, require additional information, remove content, disable features, suspend accounts, or cooperate with lawful requests where required. Enforcement decisions may consider severity, intent, recurrence, risk to others, and legal obligations. If you become aware of misuse in a workspace you administer, you should stop the activity, preserve relevant evidence if required by law or internal policy, and report serious issues through published channels.

• Acceptable Use Policy is binding for product use.
• Abuse may result in suspension or feature disablement.
• Admins should interrupt and report serious misuse.

12. Billing, refunds, and commercial terms

Commercial pricing, usage metering, credits, invoices, taxes, and refunds may depend on plan, region, provider path, and agreement type. Public marketing or pricing pages may describe direction and packaging; final charges are governed by the applicable order form, checkout terms, invoice, or enterprise agreement, together with the Refund & Cancellation Policy where published. BYOK and third-party provider charges may appear on your provider bills rather than Upcube invoices. Usage estimates in product UI are operational aids and may not match final provider billing. Taxes, currency conversion, and payment-processor fees may apply. If billing systems are not configured for a particular environment, product UI should not be read as a guarantee of live payment processing. Contact published sales or support paths for commercial questions.

• Billing depends on plan, path, and agreement type.
• Provider bills may apply separately under BYOK.
• Refund details are described in the Refund & Cancellation Policy.

13. Preview, beta, and experimental features

Ethen may expose preview, beta, lab, or experimental features. These features may be incomplete, change without notice, lack full documentation, or behave differently across environments. They are provided to gather feedback and enable early evaluation, not as guaranteed production capabilities. You should avoid placing unique production-critical data or irreversible actions on experimental surfaces unless your organization accepts the risk. Feature flags, environment labels, and honesty banners in product UI are part of risk communication and should be read carefully. Upcube may promote, modify, or retire experimental features. Continued availability is not guaranteed.

• Preview features may be incomplete or unstable.
• Production-critical reliance requires caution.
• Experimental features may change or retire.

14. Suspension, enforcement, and termination

Upcube may suspend or terminate access, limit features, or remove content when necessary to address security incidents, legal requirements, Acceptable Use violations, non-payment where billing applies, or risk of harm. Where practical and lawful, Upcube will provide notice, but emergency suspension may occur without prior notice when risk is urgent. You may stop using Ethen at any time. Account closure, data export, and deletion options depend on product capabilities and the Data Retention and Privacy policies. Some records may be retained for security, fraud prevention, legal compliance, or backup integrity after closure. Upon termination, licenses granted to you to use the service end. Provisions that by nature should survive—such as ownership, disclaimers, limitations of liability subject to law, and accrued payment obligations—continue according to applicable law and any governing agreement.

• Access may be suspended for security, legal, or abuse reasons.
• Users may stop using the service at any time.
• Some records may persist after account closure where required.

15. Disclaimers and limitation boundaries

To the maximum extent permitted by law, Ethen is provided on an “as is” and “as available” basis. Upcube disclaims warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted availability, and error-free operation, except where such disclaimers are prohibited. Model outputs, routing decisions, security findings, and workflow results are not warranted as accurate or complete. Third-party services are not warranted by Upcube beyond what is required by law or expressly agreed in a signed enterprise contract. Nothing in these Terms excludes liability that cannot be excluded under applicable law, including liability for fraud or certain personal injury claims where such exclusions are invalid. Detailed liability caps, indemnities, and dispute terms for enterprise customers may appear in negotiated agreements. Public pages do not invent jurisdiction-specific litigation terms that require legal finalization.

• Service is provided as available, subject to mandatory law.
• Outputs and third-party services are not broadly warranted.
• Mandatory legal rights are not waived where prohibited.

16. Changes and related policies

Upcube may update these Terms and related policies to reflect product changes, legal requirements, or clearer user guidance. Material changes will be communicated through reasonable channels such as product notices, account email, or updated effective dates on public pages when those channels are available. Related policies include the Privacy Policy, Acceptable Use Policy, AI Use Policy, Security Statement, Enterprise Security page, BYOK Data Handling policy, Data Retention policy, Cookie Policy, Voice Consent Policy, Voice Cloning Policy, and Refund & Cancellation Policy. If there is a conflict between a signed enterprise agreement and these public Terms, the signed agreement controls for that customer to the extent of the conflict. Questions about these Terms may be directed to published contact channels for Upcube / Ethen.

• Policies may be updated as the product evolves.
• Related public policies form one policy set.
• Signed enterprise agreements may control in conflict.

How to read these terms

These Terms explain public product and account responsibilities for Ethen. Enterprise agreements, order forms, and jurisdiction-specific notices may add or supersede parts of this page for particular customers. Where product behavior depends on configuration or third-party providers, those dependencies are called out instead of overstated.

• Account and workspace use: Access requires an authorized account and responsible workspace behavior.
• Provider and BYOK paths: Model routing may use platform or customer-managed provider accounts.
• Related policies: Acceptable use, privacy, security, retention, cookies, voice, and refunds remain part of the policy set.
• No fake guarantees: These Terms do not invent uptime SLAs, certifications, or provider guarantees.

Policy status

This Terms of Service page is published public policy text for Ethen by Upcube. It describes account and product responsibilities without unsupported certification, SLA, or compliance badges.

• Public policy text: Intended for transparent product use rules.
• Enterprise agreements: Negotiated contracts may add commercial terms.
• Related policies: Read with privacy, acceptable use, security, and AI use pages.
• Product changes: Feature availability can change with product updates.

Not legal advice

These pages explain product and policy posture for Upcube / Ethen. They are not legal advice, do not create a lawyer-client relationship, and do not replace advice from qualified counsel for your jurisdiction, industry, or use case.

Evidence and claim boundaries

This statement describes Ethen’s current posture without making unsupported certification or compliance claims. Where a control depends on account configuration, provider selection, local runtime setup, or enterprise agreement terms, that dependency is called out instead of implied as universal.

• No certification claim: This page does not claim SOC 2, ISO 27001, HIPAA, PCI, or similar certification status.
• Provider-dependent behavior: Model and service providers may apply their own terms, logs, billing, and retention practices.
• Configuration-dependent behavior: Workspace settings, BYOK, local lanes, and connected services can change data paths.
• Human responsibility: Users remain responsible for prompts, files, outputs, approvals, and downstream use.

Related reading

Use these pages together when evaluating Ethen for personal, team, or enterprise use.

• Privacy Policy
• Acceptable Use
• AI Use Policy
• Security Statement

Related policies

• Privacy Policy

  How Ethen handles account, workspace, and provider-related data.

• Acceptable Use Policy

  What uses are permitted or prohibited.

• AI Use Policy

  How to treat model outputs and high-impact work.

• Security Statement

  Security posture without unsupported certification claims.

• BYOK Data Handling

  Customer-managed provider keys and routing responsibilities.

• Data Retention

  Retention categories and deletion expectations.

• Cookie Policy

  Cookies, storage, and preference controls.

Frequently asked questions