Skip to main content
Legal · Pre-Launch

Cookie Policy

How we use cookies and similar technologies

Pre-Launch Notice

Project Lyra is currently Coming Soon. This landing site uses only the bare minimum of essential cookies required to serve pages and protect the waitlist form. The cookies described below will come into effect when the Project Lyra console launches — we are publishing this policy now so that prospective customers can review it before joining the waitlist.

What Are Cookies?

Cookies are small text files that websites place on your device when you visit them. They allow a site to recognize your browser across pages and sessions, remember your preferences, and keep you signed in. Cookies can be set by the site you are visiting (first-party cookies) or by a trusted service the site relies on (third-party cookies).

In this policy, "cookies" also refers to similar technologies such as local storage, session storage, and pixel tags, which serve comparable purposes inside modern web applications like Project Lyra.

How We Use Cookies

Project Lyra is a B2B SaaS Quantum Bridge platform that routes classical workloads to quantum and quantum-inspired backends. Once the console is live, we will use cookies to keep your account secure, remember your workspace preferences, understand how teams use the platform, and make workload routing decisions faster. We do not use cookies to build advertising profiles or to track you across unrelated websites — not today on this landing site, and not after launch.

Our use of cookies falls into four clearly defined categories, described below.

Types of Cookies We Use

Essential Cookies

Strictly necessary for the platform to function. These cookies handle authentication, maintain your logged-in session, protect against cross-site request forgery, and enforce security boundaries between tenants. The platform cannot operate without them, so they cannot be disabled through our preference center. You can still block them in your browser, but doing so will prevent you from signing in or using the console.

Functional Cookies

Used to remember choices you make so the platform behaves the way you expect on your next visit. Examples include your current subscription tier display, workspace selection, theme, and language preference. These are not required for the platform to run, but disabling them will reset your preferences on every visit.

Analytics Cookies

Help us understand how teams use Project Lyra so we can improve the product. They measure aggregate usage patterns, feature adoption, and navigation flows. All analytics data is anonymized and aggregated before analysis — we do not link it back to individual users or quantum workloads. You can opt out of analytics cookies in our preference center at any time.

Performance Cookies

Store short-lived data that speeds up the platform, such as cached QPU routing decisions, backend availability signals, and workload classification hints. These cookies reduce latency when you dispatch jobs but hold no personally identifiable information. They expire quickly and are rebuilt automatically as routing conditions change.

Cookies We Don't Use

Project Lyra is a B2B platform and we deliberately keep our cookie footprint narrow. We do not set or allow:

  • Advertising cookies or ad-targeting pixels
  • Cross-site tracking cookies
  • Third-party marketing or retargeting scripts
  • Social media sharing trackers
  • Fingerprinting or device-identification tags beyond what is needed for security

If you ever find a cookie on our domain that does not match the categories listed above, please report it to privacy@projectlyra.io so we can investigate.

Third-Party Cookies

A small number of trusted infrastructure providers set cookies on our domain so that core platform features can work. We limit these to providers that are contractually bound to process data only on our behalf.

  • Stripe — processes subscription payments and fraud checks. Stripe sets cookies on billing and checkout pages to detect anomalies and secure transactions. See the Stripe Privacy Policy for details.
  • AWS Cognito — handles authentication, multi-factor verification, and session management for the Project Lyra console. Cognito sets secure session cookies when you sign in and clears them when you sign out.

These providers never receive information about your quantum workloads, routing decisions, or backend telemetry.

Specific Cookies We Set

The table below lists the first-party cookies set directly by Project Lyra. Cookie names are prefixed with lyra_ to make them easy to identify in your browser's developer tools.

  • lyra_session — Maintains your authenticated session with the Project Lyra console. Essential. Expires after 7 days or on sign-out.
  • lyra_tier — Stores your current subscription plan so the UI can display the correct tier badge and feature set without re-querying the billing service. Functional. Expires after 30 days.
  • lyra_pref — Remembers UI preferences such as theme, sidebar state, default workspace, and language. Functional. Expires after 1 year.
  • lyra_route_cache — Caches recent QPU routing decisions to reduce dispatch latency for repeated workload shapes. Performance. Expires after 24 hours.

How to Manage Cookies

You have two ways to control cookies on Project Lyra:

  1. Our preference center — At launch, this will be available from the footer of every page and inside your account settings. You will be able to toggle functional, analytics, and performance cookies on or off at any time, and your choice will be remembered across sessions.
  2. Your browser settings — Every major browser lets you view, block, or delete cookies on a per-site basis. Step-by-step instructions are published by each vendor:
    • Chrome: Settings → Privacy and security → Third-party cookies
    • Firefox: Settings → Privacy & Security → Cookies and Site Data
    • Safari: Settings → Privacy → Manage Website Data
    • Edge: Settings → Cookies and site permissions → Manage and delete cookies
    • Brave: Settings → Shields → Cookies
    Blocking essential cookies will prevent you from signing in once the console launches.

If you clear cookies or switch browsers, your preferences will reset to defaults and you will need to sign in again.

Do Not Track

We honor the Do Not Track (DNT) signal sent by your browser. When we detect DNT, we automatically disable analytics cookies for that session, regardless of your preference center setting. Essential, functional, and performance cookies continue to operate because they are required for the platform to work securely and quickly.

We also support the Global Privacy Control (GPC) signal on the same terms.

Updates to This Policy

We may update this Cookie Policy from time to time to reflect changes in the platform, new integrations, or evolving legal requirements. When we make material changes, we will:

  • Update the "Last updated" date at the top of this page
  • Notify account administrators by email at least 14 days before the change takes effect
  • Display an in-app notice the next time affected users sign in to the console

Continued use of Project Lyra after the effective date of an updated policy constitutes acceptance of the changes.

Contact

Questions, concerns, or requests about cookies and related technologies can be sent to our privacy team:

Privacy Team

Cookie & privacy inquiries: privacy@projectlyra.io

Legal inquiries: legal@projectlyra.io

Security reports: security@projectlyra.io

We aim to respond to all cookie-related inquiries within five business days. For time-sensitive security concerns, please mark your message as urgent in the subject line.