# Data and privacy

> What data you give Qsolve when you run a workflow, what is stored and for how long, who can see it, and what a workflow's code can do with your input.

Source: https://qsolve.omlabs.co/docs/use/data-and-privacy
Updated: 2026-11-12

When you run a workflow, your input is stored in the run record, visible to the members of your account. The workflow's code runs with no network access, so it cannot send your input anywhere. If you run on a quantum computer, the circuits built from your input go to the hardware provider.

## What you submit

Your input (the form or JSON editor), the solver settings, and the target, device and spend limit. At sign-up you give an email, a display name and a password, or you use your GitHub identity. Input is checked against the workflow's input schema and rejected if it does not match.

## What is stored

Every run keeps the record described in [Run records](/docs/use/run-records): input and settings, result, cost, progress events, circuits and receipt. Your account also keeps your profile, credit history and monthly budget.

Two things you might not expect:

- **Circuits encode your problem.** The circuits a workflow sends are built from your input. For a QUBO, the matrix entries typically appear as rotation angles. Qsolve records these circuits so you can inspect them, which means your problem is stored there in another form.
- **Workflows can write to the log.** A workflow may emit progress events, and if it fails, the tail of its error output is stored and shown under **Technical log**. If a workflow prints part of your input in an error message, that text is stored.

## Who can see it

| Data | Who can read it |
|---|---|
| Your runs, inputs, results, events, circuits and credit history | The members of your account |
| Benchmark runs | Every signed-in user. These are the platform's own runs on its own benchmark inputs, and their receipts are the evidence behind a track record |
| Workflow listings, benchmark results and costs | Anyone who can open the platform |

A workflow's author does not receive your runs. The author publishes code, and Qsolve runs that code.

## What a workflow's code can and cannot do

A workflow is untrusted code written by someone else. It runs on Qsolve's machines with no network access and no access to the platform's files, and it is stopped if it exceeds its memory, CPU or time limits. Provider credentials for quantum hardware are never available to it. Code that imports modules outside a fixed set fails validation before it is published.

Your input does enter that environment, because the workflow must read it to work. It can compute with it, as intended, but it cannot send it out.

Every circuit the workflow sends passes through Qsolve, which counts shots and circuits and keeps the record you see on the run page. A workflow cannot hide quantum work: if its result accounts for fewer shots than were metered, the run is stopped as an integrity failure.

## What happens on a quantum computer

On a simulator, your circuits run on Qsolve's machines. On a quantum computer they are sent to IBM through Qsolve's own account with IBM, and the counts come back. Because the circuits encode your problem, a hardware run shares your problem with the provider. If that is not acceptable, use a simulator.

## How long data is kept

| Data | Kept |
|---|---|
| Progress events | 30 days |
| Input, solver settings and result of a finished run | Cleared 90 days after the run finishes |
| Status, cost, timings, receipt and credit history | Kept |

These periods can change. Use **Report** on a run page to download the run, with its input and events, if you need it longer. A cleared run still appears in **My runs**, but **Run again** can no longer reload its input.