Security
Trading software deserves precise security claims. This page lists what protects your account today, what is in development, and what we do not claim.
Sign-in is verified on the server, never in the browser. Sessions are held in HttpOnly, SameSite cookies that page scripts cannot read.
We keep data collection minimal. The public website runs no third-party analytics or advertising trackers and sets no cookies until you sign in.
The dashboard is protected at two layers: requests are checked before they reach the application, and again when the workspace renders.
Trading workflows are being built around configurable limits — position size, exposure and stop levels — enforced before an order is placed.
Platform activity and system events will be monitored for unusual behaviour, with account-visible activity history.
What we do not claim
PipTradeBot does not currently hold third-party security certifications or financial registrations, and we will not imply otherwise.
Specifically, PipTradeBot does not claim:
If that changes, this page will say so with verifiable details. To report a security concern, use the contact page and choose “Security”.
Next
Pricing is being finalised. Review the planned plan structure and what each tier is designed for.