Your data, plainly.

What the agent can read

Only what is in the project and the tools you turned on: files you uploaded, integrations you connected, MCP servers you added. Per-project tool narrowing limits it further. It cannot reach your desktop or your local network.

What is stored

Your projects, their files and versions, the run transcripts, and the automations you scheduled. Runs execute in an isolated workspace on the fleet.

How long

For as long as the project exists. Delete a project and its files, versions and transcripts go with it. Delete your account and everything goes.

Your keys

API keys you bring are stored encrypted, shown once when you paste them, and never written to logs. Runs on your keys go to your vendor at their price. We never use your keys for anything but your runs.

Your prompts and files

They are never used to train QGI One or any other model, ours or a vendor’s. Vendor engines on your keys are governed by your agreement with that vendor.

Who can see your projects

You, and the teammates you share a project with. Owners and admins of a team workspace can edit shared projects. Private tools ride only in your runs.

Export and leave

Export any artifact. Delete any project. Your keys and your data leave with you.

Certifications

None to claim yet. When an audit completes it is listed here with its date. Regulated deployments (private cloud, on-premises, air-gapped) are a separate product at QGI.

Legal text: privacy policy, terms of service. Questions: [email protected]. Private deployment and enterprise controls: QGI.