Your hosted account and connection
PTQ runs in your browser or through a Claude connection to the same account. The engine stays on our servers.
01
No hosted broker connection
Hosted PTQ does not collect broker keys or send orders to a broker. Never put broker credentials in prompts, notes or support messages.
02
Claude uses your hosted account
Claude can build and test strategies and place simulated practice orders. Requests and results travel between your client and hosted PTQ.
03
Practice orders only
Browser and Claude orders use practice money. Live trading is not available here.
04
A revocable connection
Revoke a connection in Connect Claude and its link stops working. Each request gets a fresh licence check.
What crosses the connection
The Claude Code connector stores your PTQ credential in a private file on the client. It sends that credential to hosted PTQ over HTTPS for authentication. Tool requests go to the server and results return to Claude. The connector redacts the saved credential from returned messages.
For Claude Desktop or claude.ai, paste the private link into connector settings. Keep the link and licence key out of chats, screenshots and shared documents. PTQ stores a hash of the connection token and never shows the link again.
A connection can change account data and spend credits, so ask for costs and approve changes before Claude makes them.
Access is checked on the server
The browser and Claude use the same account's strategies and credit balance. A revoked connection, an inactive licence or a licence PTQ cannot check is refused. Revocation does not undo work already completed.
Checks before a simulated fill
Every practice order needs confirmation and validation evidence, then passes risk, quote and portfolio checks. A refused request is not a fill.
Account and workspace data
Account
Your email, name if you gave one, and sign-in records, held by our sign-in provider.
Strategies
The strategies you create and their settings.
Risk profiles
Your risk profile, limits and the mechanics you switched on.
Paper trades
Simulated fills, labelled simulated, plus your backtest and validation results.
Usage
Which features you used, when, and the credits you spent.
Consent record
The jurisdiction you declared and the acknowledgements you ticked, with a timestamp.
Support
Tickets and support chats. An AI assistant may help draft the answers.
Payment records
From Stripe: name, email, what you bought, the amount and their identifiers. Card numbers never reach us.
Read the privacy policy for data handling details.
Limits to understand
No engine archive
The full engine is not available for download. Claude Code's small connector only connects to hosted PTQ. Its published checksum checks the file, not the safety of every action it can request.
Protect your connection link
Someone with the private link can use it to access your account's tools while the connection and licence are valid. Revoke an exposed link and create a new one.
Simulation is not live execution
Practice fills are simulated inside PTQ and do not reproduce broker execution. A passed test does not establish future performance.
Provider coverage varies
History is fetched and cached from configured providers, with no preloaded universal dataset. Coverage varies by market, interval and date, and a listed market may lack usable history.