What we store, and who else sees it.
QuxCloud holds your account, your workspaces and your projects’ code. This says what that means in practice, which records exist, which companies process them, and how to take your data out or have it deleted.
Last updated 2 September 2026.
What we collect
- Your account. Email address, a password stored only as a salted, peppered hash, and your sessions. Each with the IP address and browser that created it, so you can see and revoke them under Security.
- Your workspaces and projects. Names, the kits you selected, members and their roles, and the contents of your project files. Your code is the substance of what we hold.
- What the Builder did. The request you typed, the plan the crew produced, the files it wrote and what the run cost in credits. This is how “undo” and your credit balance work.
- Billing records. Your plan, invoices, credit ledger and a Stripe customer reference. Card and bank details are entered on Stripe’s pages and are never sent to us or stored here.
- API keys you mint, stored as hashes with a visible prefix so you can tell them apart.
We do not use advertising or analytics trackers, and there is no third-party script on the signed-in application. The only cookie the app sets is your session.
What we do with your code
Three features send project files somewhere: the Builder sends the parts relevant to your request to an inference provider; the live preview copies your files into a sandbox container that runs them; and the project index stores chunks of your code, and their embeddings, so the Builder can find what already exists. All three are scoped to the project they belong to.
Your code is not used to train models, ours or anyone else’s, and is not shared with other customers. Isolation between workspaces is enforced by row-level security in the database, not by application code alone.
Who else processes it
| Processor | What for | Where |
|---|---|---|
| DigitalOcean | Application hosting and the managed PostgreSQL database | United States |
| Cloudflare | Inference for the Builder (Workers AI), the sandbox containers that run live previews, DNS and edge delivery | Global |
| Stripe | Payments. Card and bank details are entered on Stripe’s own pages and never reach us | United States |
| Email delivery (SMTP) | Verification, password reset and billing notices | United States |
We will tell you before adding a processor that handles project data.
How long we keep it
- Projects and their files: until you delete them, or thirty days after the workspace is closed.
- Preview containers: torn down when idle. Nothing in them outlives the container.
- Sessions: until they expire or you revoke them.
- Billing and ledger records: kept as long as tax and accounting rules require, which is longer than the account.
Getting it out, or getting it deleted
Every project can be downloaded as a zip, or checked out to your own machine with the CLI, at any time and on any plan, including after you stop paying. The @quxkit packages are licensed rather than sold and are not included; everything you wrote is.
To correct or delete your data, or to ask what we hold, write to [email protected]. Deleting a workspace deletes its projects, files, generations and index. Backups roll off within thirty days.
Contact
QuxKit, for QuxCloud at cloud.quxkit.ai. Privacy questions: [email protected].
QuxCloud