confidentialnodes.com
Marketplace Inference GPU prices Finder Listings Contact us Account
Account

Cookie Notice

The cookies and browser storage used by Confidential Nodes, why we use them, and how to control optional analytics.

Effective and last updated 24 August 2026

On this page

  1. About this notice
  2. Technologies we use
  3. Strictly necessary storage
  4. Optional analytics
  5. Server-side telemetry
  6. Your choices
  7. Third-party sites
  8. Changes
  9. Contact

1. About this Notice

This Cookie Notice explains how Alexandria Cornerstone Inc. uses cookies and similar browser storage on confidentialnodes.com. It should be read with our Privacy Policy. We use optional analytics only after you allow them. Rejecting analytics does not prevent you from using the public Services.

2. Cookies and similar technologies

A cookie is a small text record stored by a browser. Local storage and session storage are similar browser features that can remember a preference or identifier. This Notice uses “browser storage” for all of them. Some technology is necessary to remember your privacy choice or secure a service you request. Analytics storage is optional.

3. Strictly necessary storage

cn_cookie_consent
Stored in local storage by our PostHog consent integration to remember whether you allowed or rejected optional analytics. It remains until you change the choice, clear browser data, or browser policy removes it. It is necessary to respect your choice and is not used for analytics.
wos-session
A strictly necessary, encrypted first-party session cookie created through WorkOS when you sign in. It maintains the account session and is configured for a maximum of 30 days, although the session may end sooner because of inactivity, sign-out, revocation, or browser policy. It is HTTP-only, uses SameSite=Lax, and is Secure in production.
wos-auth-verifier-*
Strictly necessary, per-attempt cookies created through WorkOS for PKCE and OAuth state verification during sign-in or registration. They are HTTP-only, use SameSite=Lax, are Secure in production, expire after 10 minutes, and are removed after a completed or failed callback when possible.

Older versions of the site used PostHog’s default ph_<project key>_posthog storage name before this consent control was introduced. The current site attempts to remove that legacy browser storage during initialization.

WorkOS processes account identifiers, verified email, authentication events, and session information to provide these authentication features. These cookies are not used for advertising. See our Privacy Policy for more information about service providers and international data transfers.

4. Optional PostHog analytics and session replay

If you select “Allow analytics”, we initialize EU-hosted PostHog product analytics, error tracking, and session replay. This helps us understand which pages and features work, diagnose failures, and improve navigation and marketplace workflows. We do not use PostHog for cross-context behavioral advertising.

ph_cn_analytics
A first-party cookie and local-storage record containing a random device identifier, session information, page and referral context, and product configuration used by PostHog. The cookie is configured for 365 days and may be refreshed during later permitted use. Related session values may be kept in session storage until the browsing session ends.

PostHog may receive page URLs, referrer, timestamps, browser and device characteristics, approximate location derived from IP, interactions, errors, and a random identifier. Session replay records page structure and interactions. All form inputs are configured to be masked. You should still avoid entering secrets or unnecessary sensitive data in any free-text field.

5. Server-side operational telemetry

Our servers may send limited error events to EU-hosted PostHog without storing or reading optional analytics information on your device. These events can include the requested path, request method, response status, runtime, and technical error details. We use them to secure and repair the Services. Form bodies are not intentionally included. If you allowed browser analytics, a session identifier may link a server error to the relevant session.

6. Your choices

The first time you visit on a new browser profile, we ask whether to allow or reject optional analytics. Both choices are available in the same step. You can reopen the control at any time with “Cookie settings” in the footer.

Rejecting analytics stops browser analytics and removes PostHog analytics persistence for this browser. You can also clear cookies and local storage in browser settings. We configure PostHog to respect supported Do Not Track and Global Privacy Control signals as a rejection of optional analytics. Browser or network blocking tools may provide additional control.

7. Third-party websites

Links to provider documentation, supplier sites, or other third parties may lead to services with their own cookies and privacy choices. Their notices govern their browser storage; this Notice applies only to the Services operated by Alexandria.

8. Changes to this Notice

We update this Notice when browser storage, analytics configuration, account or payment flows, or legal requirements change. We will request fresh consent when required by law or when a change materially expands an optional purpose.

9. Contact

Questions about browser storage or privacy choices can be sent to hello@confidentialnodes.com or to Alexandria Cornerstone Inc., Crusiusstraße 1, 80538 Munich, Germany.

Explore

Marketplace Confidential inference Finder Listings For suppliers About us Contact us

Directories

GPU prices GPU providers Blog GPU guides Technologies GPU attestation Cost calculator RSS feed

Legal

Privacy Policy Terms of Use Cookie Notice
by Alexandria
confidentialnodes.com

Pricing and specifications may change.

Alexandria Cornerstone Inc.