Privacy

Draft-safe privacy language for products that are still taking shape.

This page is a placeholder privacy surface for Upcube products and websites. Final legal text, effective dates, legal entity details, official privacy contact channels, retention schedules, deletion workflows, training-use terms, vendor lists, and jurisdiction-specific disclosures were not provided in this repo. Because those details were not provided, this page does not present itself as a final or binding privacy policy.

Current status

Use this page as a truthful draft placeholder. It exists so the site can link to a privacy page without inventing commitments that are not yet supported by reviewed legal or operational documentation.

What privacy may need to cover later

Depending on the product surface, future reviewed privacy language may need to explain: Account and profile information Prompts, files, and workspace content Saved outputs and artifacts Tool activity and approval history Usage, device, and diagnostic information Search, retrieval, and discovery activity Product-specific data for learning, discovery, or commerce surfaces Those categories are examples of topics that may matter. They are not a confirmed statement of collection or use.

What is not provided

The repo does not provide final answers for: What data is collected Why it is used How long it is retained Whether content is used for model training How deletion or export works Which subprocessors or vendors handle data Which cookies or analytics tools are in use Which user-rights workflows are available Which privacy contact channel should be published Where those facts are not provided, the correct answer on this page is not provided.

Product framing

Ethen and related Upcube products may involve sensitive context because useful work can include prompts, files, drafts, research, tool activity, and saved outputs. That is exactly why privacy copy should stay specific, careful, and evidence-based. Marketing language should not be treated as proof of privacy behavior.

How this page should be used

This page should: Set expectations conservatively Point out which details are still missing Avoid overclaiming operational maturity Make it easier to replace placeholder text with reviewed policy text later This page should not: Invent legal commitments Invent contact details Invent retention or deletion guarantees Invent training-use terms Invent vendor or regional processing claims

Related responsibilities

Privacy is connected to product design, safety, and security, but it is not interchangeable with them. A future final privacy policy should be checked against actual runtime behavior, approved legal text, and current operational processes before publication.

The standard

Say only what is supported. Mark missing details clearly. Keep privacy language draft-safe until reviewed text exists. Privacy commitments should come from reviewed policy text and real product behavior, not from guesswork.