Privacy Policy

• Account: name, email address, a hash of your password, two-factor settings, notification preferences, editor preferences.
• Billing: plan, its status, your wallet and AI-credit balances and statement, your deposit code, and the public keys and signatures of SOL deposits you send us. We never hold your private keys and never see a card, because we accept none.
• Transactions balance: your deposit memo, deposits observed on-chain (signature, amount, sender address) and the running balance.
• Machine metadata: machine size, status, public IP, box software version, resource usage samples (CPU, memory, disk, network totals) and container names.
• Workspace metadata: project names, image tags and digests, session start/stop times and exit reasons, agent thread titles, and approval decisions. Not the content of your files or threads.
• Security log: sign-ins, password and 2FA changes, key changes, with IP address and browser family.
• Support email you send to support@mail.quants.sh.

Your source code, built images, persistent agent transcript files, the transaction ledger, private keys your software uses, provider credentials, and anything else in the filesystem live on your dedicated machine. We do not copy those files to our systems. Feed traffic passes through the private channel on your machine and is not logged by us beyond per-session counts used for safeguards and billing.

The agent pane connects through the quants.sh control plane. Our API and WebSocket endpoints terminate the browser connection and relay prompt and transcript events in plaintext at the application layer to and from the agent on your machine. TLS protects those connections in transit, but this is not end-to-end encryption from our infrastructure and the control plane can technically access the relayed content while processing it. We do not use prompt or transcript content to train models, intentionally write it to application logs, or intentionally retain it after relay.

To provide the service (provision and operate the machine, route feeds, bill you, notify you), to keep it secure (rate limiting, abuse detection, the security log), to support you when you ask, and to meet legal obligations. We do not sell data and we do not use your data to train models.

• Solana RPC and price providers: we read the public chain to confirm deposits and a public price feed to price AI usage in SOL; neither receives anything about you beyond the public transaction itself.
• Resend: transactional email delivery (email address, message content).
• Cloudflare: DNS and edge protection for our web addresses (IP address, request metadata).
• Our infrastructure providers in Germany, who host the machines and feeds under data-processing terms.
• Anthropic / OpenAI: only if you sign in to Claude Code or Codex on your machine; that relationship is directly between you and them.
• Authorities, when legally required, and then only what is required.

Account and billing records are kept while the account exists and for 7 years after for tax and accounting purposes. Security logs are kept 12 months. Usage samples are kept 7 days on the machine and 30 days in the control plane. Your machine and its contents are kept while your account exists (see the Terms, section 8) and destroyed when the account is deleted.

Passwords are hashed with Argon2id. Secrets we must store (recovery codes, certificates) are encrypted at rest. Control-plane traffic to your machine uses mutual TLS with per-machine certificates. Two-factor authentication is available and required for sensitive actions when enabled. Staff access to production is limited, logged and used only for operating the service.

You can view and change your profile, preferences and keys in Settings, download your projects from the workspace or over SSH, and delete your account yourself. Email us to request a copy of the data we hold about you, to correct it, or to have it erased where we are not required to keep it. We answer within 30 days. Residents of the EU/EEA and UK have the rights set out in the GDPR; Canadian residents, those under PIPEDA.

We use one session cookie to keep you signed in. No advertising or tracking cookies. No third-party analytics. Connecting a browser wallet to pay happens entirely between your browser and the wallet extension; we receive only the signed transaction.

If this policy changes materially we email you before the change takes effect. Questions or requests: support@mail.quants.sh.