Early-access note: This page describes the current product and operating practices. It will be updated as Leona Quantum grows, adds paid services, and formalizes its operating entity.
1. Information we receive
We may receive account information such as your email address and authentication details when you create or use an account.
When you use the workbench, we may process prompts, generated code, circuit data, run settings, simulation results, verification records, saved artifacts, and related metadata that you choose to submit.
If you contact us, we receive the information you include in that message and the reply details needed to respond.
2. How we use information
We use information to authenticate users, run and verify requested workflows, save and reopen Studio artifacts, provide support, secure the service, diagnose failures, and improve reliability and product quality.
We may use aggregated or de-identified operational information to understand performance. We do not present private workspace artifacts as public Atlas material without an explicit publish action.
3. Service providers and infrastructure
Leona Quantum relies on specialized providers for hosting, authentication, databases, observability, model access, and isolated code execution. Those providers may process information only as needed to provide their services.
Generated code is treated as untrusted input and is intended to run in an isolated, network-restricted execution environment. Do not submit secrets or information you are not authorized to process.
4. Public and private work
Public Atlas entries are separate from private Studio workspaces. A Studio entry is private by default. Publishing is an explicit action that may make an artifact, its code, and its evidence available to other people; review the content before publishing.
5. Retention and your choices
We retain account and workspace records for as long as needed to provide the service, meet legitimate operational needs, resolve disputes, and comply with applicable obligations. Retention may vary by record type and account status.
You can ask about the information associated with your account, request correction or deletion where applicable, or ask a privacy question through the contact page. We may need to verify your request before acting on it.
6. Cookies and security
The authenticated product uses cookies or similar technologies to maintain a secure session. The public site may also receive ordinary technical information from your browser and hosting infrastructure.
We use reasonable technical and organizational measures for the stage of the product, but no online service can promise perfect security. Keep account credentials private and do not place API keys, passwords, or regulated data in prompts or generated code.
7. Changes and contact
We may update this policy when the service changes. The date above identifies the latest version published on this page. Use the contact page for questions.