Privacy Policy

This policy covers personal data and related workspace data processed for Ethen product and site experiences. Depending on context, Upcube may act as a service provider/processor for customer workspace content and as a controller for account administration, site analytics where used, security logs, and business operations data. Enterprise customers may have separate data processing terms. If a signed agreement conflicts with this public policy for that customer’s covered services, the signed agreement controls to the extent of the conflict. This policy does not cover third-party websites, model provider consoles, or services that you access outside Ethen, even if linked from the product. Organizations should document internal handling rules for this category, including who may access it, how long it should be kept beyond product defaults, and whether export is required before offboarding. When in doubt, minimize personal data in prompts and uploads and prefer dedicated secret storage over free-text fields.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Account data may include name, email address, authentication identifiers, organization membership, role assignments, profile preferences, billing contact details where configured, support tickets, and security settings such as session metadata or multi-factor status indicators. We use account data to authenticate users, administer workspaces, provide support, secure accounts, communicate service notices, and operate commercial features where enabled. Account data is generally required to provide the service you request. You should keep account contact details accurate so security and service notices can reach the right people. Organizations should document internal handling rules for this category, including who may access it, how long it should be kept beyond product defaults, and whether export is required before offboarding. When in doubt, minimize personal data in prompts and uploads and prefer dedicated secret storage over free-text fields.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Workspace data may include projects, sessions, labels, configuration, member lists, integration settings, route preferences, feature flags, and operational metadata about how a workspace is used. Workspace data helps Ethen present history, permissions, and product state. Admins and members may create additional structured data such as saved views, workflow definitions, or approval queues. The visibility of workspace data depends on product permissions and sharing settings. Workspace data should be treated as business-sensitive. Invite only trusted members and review integration scopes regularly. Organizations should document internal handling rules for this category, including who may access it, how long it should be kept beyond product defaults, and whether export is required before offboarding. When in doubt, minimize personal data in prompts and uploads and prefer dedicated secret storage over free-text fields.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Prompts, instructions, system messages, model parameters, and generated outputs may be processed to provide chat, coding, research, media, voice, and related features. These materials can contain personal data if users include it. Prompts and outputs may be stored as part of sessions, runs, logs, or evidence records depending on feature design and settings. They may also be transmitted to model providers or tools according to the selected route. Users should avoid placing unnecessary sensitive personal data in prompts. Organizations should set internal rules for confidential content, customer data, and regulated information. Organizations should document internal handling rules for this category, including who may access it, how long it should be kept beyond product defaults, and whether export is required before offboarding. When in doubt, minimize personal data in prompts and uploads and prefer dedicated secret storage over free-text fields.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Users may upload or attach documents, source code, images, audio, archives, or other files. Files may be parsed, previewed, embedded for retrieval, or passed to models and tools as needed for the requested operation. File processing can expose personal data contained inside documents. Malware scanning or type validation may occur for security. Large files or binary assets may have different storage paths than short text prompts. You are responsible for ensuring you have rights to upload files and that sharing them with a model workspace is appropriate for your organization. Organizations should document internal handling rules for this category, including who may access it, how long it should be kept beyond product defaults, and whether export is required before offboarding. When in doubt, minimize personal data in prompts and uploads and prefer dedicated secret storage over free-text fields.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Where workflows, approvals, receipts, or evidence packages are enabled, Ethen may process records such as run status, tool traces, diffs, reviewer comments, approval decisions, timestamps, and related artifacts. These records help teams inspect what happened. Evidence and approval data may include personal data about actors in a workflow (for example, who approved a change). Retention of these records may be longer when needed for security, auditability, or dispute review, subject to the Data Retention policy. Do not assume evidence records are a complete legal archive unless your organization configures and validates them for that purpose. Organizations should document internal handling rules for this category, including who may access it, how long it should be kept beyond product defaults, and whether export is required before offboarding. When in doubt, minimize personal data in prompts and uploads and prefer dedicated secret storage over free-text fields.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

If you connect repositories, storage, messaging, issue tracking, browsers, or other services, Ethen may process tokens, scopes, resource identifiers, and content retrieved or written through those connections. The categories of data depend on the integration and permissions you grant. Connected-service data may leave Ethen when actions are executed in external systems. Likewise, external content may be pulled into prompts, tools, or workspace history. Review scopes carefully and revoke unused connections. Upcube does not control the privacy practices of connected third-party services themselves. Organizations should document internal handling rules for this category, including who may access it, how long it should be kept beyond product defaults, and whether export is required before offboarding. When in doubt, minimize personal data in prompts and uploads and prefer dedicated secret storage over free-text fields.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

When requests are routed to model or tool providers—whether through platform-configured providers or customer BYOK credentials—prompt content, files, outputs, and request metadata may be processed by those providers under their terms and settings. BYOK gives customers control over provider account selection, but provider-side terms, billing, logs, and retention may still apply. Upcube may still process operational metadata needed to operate routing, show status, enforce limits, or secure the product. Customers should evaluate provider data handling for their industry and risk profile. See the BYOK Data Handling policy for additional detail. Organizations should document internal handling rules for this category, including who may access it, how long it should be kept beyond product defaults, and whether export is required before offboarding. When in doubt, minimize personal data in prompts and uploads and prefer dedicated secret storage over free-text fields.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Voice features may process audio recordings, live microphone input, transcripts, generated speech, voice settings, and related metadata. Voice data can reveal identity and may capture bystanders if used carelessly. Voice processing should occur with appropriate notice and permission. The Voice Consent Policy and Voice Cloning Policy describe additional expectations for recording, transcription, synthesis, and voice likeness use. Users should avoid submitting voice content containing sensitive personal data unless they have authority and a suitable workflow.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Where local or private model lanes are supported, some processing may run on customer-controlled machines or environments rather than remote provider endpoints. Local lanes can reduce certain third-party transmissions, but they do not automatically eliminate all product telemetry, account authentication, or workspace metadata processing. Local runtime security depends heavily on the customer’s device posture, network, and operational practices. Upcube can provide product pathways; customers control the local environment. Availability of local lanes may vary by feature and setup.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Ethen sites and apps may use cookies, local storage, session storage, and similar technologies for authentication, preferences, security, and product analytics where enabled. Details are described in the Cookie Policy. Essential storage is typically required for login sessions and core functionality. Analytics or non-essential technologies, if used, should be configurable according to product and regional requirements as those controls are implemented. Browser settings can block some cookies, which may affect login or feature availability.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Upcube applies administrative, technical, and organizational measures designed to protect personal data and workspace content, as described at a high level in the Security Statement. No method of transmission or storage is completely secure. Access to production systems is expected to follow least-privilege and need-to-know principles. Customers control workspace membership, keys, and integrations on their side of the shared responsibility model. Report suspected security issues through published security or support channels.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Retention is described by category because exact periods depend on account configuration, product settings, legal obligations, and provider behavior. Account records, workspace content, logs, backups, billing records, and security records may follow different timelines. Deletion requests are handled through available account or support paths. Deletion may not immediately remove all copies from backups, security logs, or provider systems where retention is required or technically delayed. See the Data Retention policy for category-level expectations.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Depending on your jurisdiction and relationship to Upcube, you may have rights to access, correct, delete, or export personal data, object to or restrict certain processing, or withdraw consent where processing is consent-based. Enterprise end users may need to contact their organization administrator first for workspace content controlled by that organization. We may need to verify requests and may deny or limit requests where permitted by law—for example, when disclosure would harm others’ privacy, reveal security-sensitive information, or conflict with legal obligations. Use published privacy or support contact paths to submit requests.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

We may share data with infrastructure, model, analytics, support, payment, or security service providers that process data on our instructions or as independent providers for specific functions. We may also disclose data when required by law, to protect rights and safety, or in connection with corporate transactions subject to appropriate safeguards. Provider routing means some content is disclosed to model or tool providers as part of fulfilling a user request. BYOK may mean the disclosure is authenticated under the customer’s provider account. We do not sell personal data as “sale” is commonly understood in ordinary commerce. If regional definitions of sale or sharing require additional notices or opt-outs, those mechanisms will be provided where applicable as product and legal requirements mature.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Ethen is not directed to children, and we do not knowingly collect personal data from children in violation of applicable law. If you believe a child has provided personal data inappropriately, contact us so we can take suitable steps. Ethen may be accessed from multiple countries. Data may be processed in locations where Upcube, its providers, or connected services operate. International transfers may rely on appropriate contractual or legal mechanisms depending on context. Users are responsible for determining whether their cross-border use of model workspaces is allowed under their local laws and employer policies.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

We may update this Privacy Policy to reflect product changes, legal requirements, or clearer explanations. Updated versions will show a revised effective or update date when published. Material changes may also be communicated through product or account notices when appropriate. Continued use of Ethen after an update means the updated policy applies to subsequent use, except where mandatory law or a signed agreement requires a different process. For questions about this policy, use published Upcube / Ethen contact channels.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

We may send service notices, security alerts, product changes, and administrative messages related to your account. These communications are part of operating the service and are distinct from optional marketing mail. Marketing communications, if used, should provide unsubscribe mechanisms where required. Organizational admins may receive notices on behalf of their workspaces. Keep contact emails current so security notices are not missed. Support interactions may create ticket records containing the information you submit. Do not place secrets in support tickets when a secure channel exists. Telephone or meeting support, if offered, may generate notes used to resolve issues. Those notes follow support retention practices rather than chat history defaults.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Ethen uses models and routing logic to generate outputs and choose routes. These systems assist users; they are not intended as sole automated legal, credit, or employment decision engines. Product telemetry may aggregate usage patterns to improve reliability. Aggregated operational metrics should not be confused with advertising profiles. If a feature applies automated safety filtering, that filtering may block or transform some outputs to reduce abuse. Safety systems are imperfect and may produce false positives or false negatives. Users remain responsible for reviewing model outputs before high-impact use. Organizations should not present Ethen outputs as unreviewed automated determinations in regulated processes without appropriate human oversight and legal analysis.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Privacy questions, requests, and complaints may be submitted through published privacy or support contact channels on Upcube / Ethen properties. Include enough detail to identify your account and request type. We may need to verify identity or organizational authority before fulfilling requests about personal data or workspace content. Enterprise end users may be directed to their organization administrator for content controlled by that organization. If you are unsatisfied with a response, you may have the right to contact a supervisory authority in your jurisdiction, where applicable law provides that right. This statement does not limit rights that cannot be limited by contract. Regional representatives or additional notices may be published when required for particular markets. Until such notices are published, use the general contact paths.

Readers should treat this section as operational guidance for product use and evaluation. Where a control or retention behavior depends on plan, region, provider route, or admin configuration, confirm the live setting in product UI or a written enterprise agreement before relying on a specific outcome. Upcube updates public policy pages when material product posture changes, but customers remain responsible for their internal compliance programs.

Ethen processes account data, workspace content, prompts, outputs, files, workflow records, and related operational metadata to provide a model workspace. Some content is transmitted to model or tool providers according to selected routes, including BYOK paths where enabled. Local lanes may reduce certain remote transmissions but do not automatically eliminate all product metadata processing.

Users and organizations should minimize unnecessary personal data in prompts, manage membership carefully, protect keys, and use available deletion and export tools where offered. Rights requests are handled through published channels with verification as needed.

This Privacy Policy avoids unsupported certification claims and should be read with the Cookie Policy, Data Retention policy, BYOK Data Handling policy, Security Statement, and Voice policies where relevant.

If your use case involves regulated data classes, obtain internal legal and security approval before broad enablement. Public transparency is not a substitute for a fit-for-purpose risk assessment.