Cookie Policy

Cookie Policy

Cookies and similar technologies help Ethen provide authenticated sessions, remember preferences, protect accounts, and understand product usage where analytics are enabled. This policy describes categories rather than claiming marketing trackers that are not verified as present.

1. What cookies and similar storage are

Cookies are small text files stored on your device by a website or app. Similar technologies include local storage, session storage, pixel tags, and SDK-based identifiers. These technologies can be first-party (set by Ethen) or third-party (set by another domain if such tools are used). Some last only for a session; others persist until they expire or are deleted. Not all storage is used for advertising. Much of it is operational. Server-side processing of prompts and files is described in the Privacy Policy; this page focuses on client-side storage.

• Cookies store small pieces of state on your device.
• Similar tech includes local/session storage.
• Many uses are operational rather than advertising.
• Server-side data is covered in Privacy Policy.

2. Essential cookies and storage

Essential technologies are required to provide core functionality such as page routing, load balancing, security checks, and basic site operation. Without them, parts of the site may not work. Essential storage is not used to build advertising profiles. It exists so the service can run. If you block essential cookies, login and secure areas may fail. Security-related essential storage may include tokens that help prevent cross-site request forgery or session fixation.

• Essential storage enables core operation.
• Not for advertising profiles.
• Blocking may break authenticated features.
• Some essential storage is security-related.

3. Authentication and session storage

When you sign in, Ethen may store session identifiers, CSRF tokens, device/session metadata, or related values needed to keep you authenticated and to protect account actions. Session lifetime depends on product configuration, idle timeouts, and security events. Signing out and clearing site data ends many client-side sessions, though server-side session invalidation is also important. Do not use shared browsers for privileged admin accounts without strict sign-out practices. If you suspect session theft, sign out everywhere if available, rotate passwords, and contact support.

• Auth storage keeps sessions working securely.
• Timeouts and sign-out matter.
• Avoid shared browsers for admin work.
• Respond quickly to suspected session theft.

4. Preferences

Preference storage may remember UI theme, dismissed banners, language hints, layout choices, or similar non-essential comfort settings. These preferences improve usability but are not required for basic legal policy reading on public pages. Clearing site data resets preferences. Preference storage should avoid holding secrets or raw credentials.

• Preferences improve usability.
• Usually limited in sensitivity.
• Clearing data resets them.
• Do not store secrets in preference fields.

5. Analytics

If product or site analytics are enabled, Ethen may use first-party analytics or carefully chosen tools to understand feature usage, performance, and errors. Analytics should be configured to avoid unnecessary personal data collection where practical. This policy does not claim a specific advertising analytics stack that is not verified. If analytics categories expand, this page should be updated. Where regional consent is required for non-essential analytics, consent mechanisms should be respected when implemented. Aggregated product metrics help reliability; they are not a substitute for customer telemetry pipelines.

• Analytics, if used, measure product usage and health.
• No unverified ad-tech claims.
• Consent applies where required and implemented.
• Product metrics support reliability.

6. Marketing tools

Marketing pixels or advertising cookies are used only if actually deployed for Ethen properties. This page does not invent a marketing stack. If marketing technologies are introduced, they should be disclosed and, where required, consent-controlled. Enterprise product use inside authenticated consoles is typically operational rather than ad-driven. Do not assume that visiting a marketing page enables the same storage as an authenticated console session.

• No invented marketing trackers.
• Future marketing tools need disclosure.
• Authenticated product use is primarily operational.
• Marketing pages and consoles may differ.

7. Third-party tools

Third parties may set cookies if you interact with embedded content, authentication providers, payment providers, or support widgets that are present on a page. Those third parties have their own policies. Review them when you use those features. Model providers used via API routing generally process request content server-side and are covered more by Privacy and BYOK policies than by browser cookies. Browser extensions you install can also read page storage; that is outside Upcube control.

• Embedded third parties may set their own cookies.
• Review third-party policies.
• Model API routing is mostly server-side.
• Browser extensions are user-controlled risk.

8. Browser controls

Most browsers let you block or delete cookies, clear local storage, and reset permissions. Mobile OS settings may offer additional controls. Blocking all cookies can prevent sign-in. Consider allowing essential cookies for Ethen domains while clearing unused site data periodically. Enterprise-managed browsers may enforce additional policies beyond individual control. Private/incognito modes may limit persistence but are not a complete privacy solution for authenticated work.

• Browsers provide cookie and storage controls.
• Blocking all cookies can break login.
• Managed devices may enforce extra rules.
• Private mode is not complete protection.

9. Relationship to Privacy Policy and changes

Cookie use is part of broader privacy practices described in the Privacy Policy. Retention of related server-side logs is described in the Data Retention policy. We may update this Cookie Policy as technologies change. Material updates will be reflected on this page with revised context as needed. Questions can be sent through published privacy or support channels. If a consent banner or preference center is presented, use it to manage non-essential categories where offered.

• Read with Privacy and Retention policies.
• Updates track technology changes.
• Contact published channels with questions.
• Use consent tools where presented.

Technologies covered

This policy covers cookies and similar client-side storage used on Ethen properties. Exact technology names can change as front-end implementations evolve. Essential storage may be required for the product to function.

• Cookies: HTTP cookies set by Ethen or, if used, certain third parties.
• Local/session storage: Browser storage for preferences and session state.
• Security tokens: Auth-related storage needed to keep you signed in.
• Optional analytics: Only where product analytics are actually enabled.

Policy status

This Cookie Policy describes categories of client-side storage without inventing unverified marketing trackers.

• Essential first: Auth and core function storage are primary.
• Analytics only if used: No fake ad-tech inventory.
• User controls: Browser settings can limit storage.
• Privacy-linked: See Privacy Policy for broader practices.

Not legal advice

These pages explain product and policy posture for Upcube / Ethen. They are not legal advice and do not replace 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. Configuration, provider selection, and enterprise agreements can change data paths and controls.

• No certification claim: No SOC 2, ISO 27001, HIPAA, PCI, or penetration-test guarantee is claimed here.
• Shared responsibility: Customers control members, keys, devices, and integrations.
• Provider-dependent paths: Third-party providers apply their own security practices.
• Continuous change: Controls evolve; public pages avoid frozen false guarantees.

Related reading

Cookies are one part of privacy and security.

• Privacy Policy
• Security Statement
• Terms of Service
• Data Retention

Related policies

• Terms of Service

  Account and workspace rules.

• Privacy Policy

  Data categories and rights.

• Data Retention

  Retention categories.

• BYOK Data Handling

  Customer keys and provider paths.

• Enterprise Security

  Enterprise security evaluation overview.

• Security Statement

  Security posture overview.

• Acceptable Use Policy

  Prohibited uses.

• Cookie Policy

  Cookies and storage.

Frequently asked questions