Your information.
Pre-launch draft. Seller/controller address, provider agreements and retention schedule require review before sales open.
What we process
Name and email, password hash, verified network-code redemption and partner attribution, any previously recorded legacy membership details, invoices, claims and confirmed receipt records, licence dates, MT5 login/server, settings and operational activity. We do not request wallet seeds. MT5 trading credentials use the separate encrypted connection form described below.
Purpose and access
We use these records to secure your account, verify signup pricing, fulfil the subscription, reconcile payments and support execution. Network eligibility is established by approved IB/sub-IB code redemption. Existing legacy £25 eligibility is retained; later redemptions affect new subscription invoices, while existing invoices and attribution stay unchanged. Staff access is role-protected. The site uses Cloudflare; the backend/database is intended for OVHcloud; configured providers handle transactional email, the Telegram signal feed and payment receipt checking. Confirm actual contracts and international transfers before launch.
Account performance and IB billing
Authorised operators can review assigned account history and realised bot profit after recorded costs, excluding deposits, withdrawals, credit and floating profit. Complete reconciled history is required for partner billing under separate commercial agreements. An IB dashboard shows only that IB’s accepted agreements and liabilities. Any IB-to-client profit split is arranged separately. Monthly licence subscriptions use manual USDT transfers on Ethereum. The customer submits the transaction hash for staff to verify the actual credited funds and invoice ownership; a claim alone does not activate a licence. IB crypto settlements are verified manually, with an audit record. The first verified subscription payment validates the first paid period. Later renewals require verified IB settlement and manual staff approval under accepted service terms. Invoice notices and reminders use the IB’s verified account email: after 24 hours, then every two days while payment remains unconfirmed. Existing positions remain managed during new-entry holds.
Your rights
Contact leon@printersfx.com for access, correction, deletion or privacy enquiries. Some financial/security records require retention. The final lawful-basis assessment, retention periods, controller address and provider information must be completed before sales. No analytics or advertising tracking is installed.
MT5 connection credentials
The secure connection form encrypts your MT5 trading password in the browser for the assigned execution node. The node protects its private key and saved credentials with Windows DPAPI. Our API stores an encrypted handoff until the node confirms storage; unused handoffs expire after 24 hours and are cleared by scheduled cleanup. Encrypted historical backups follow the final retention policy. We never display a saved trading password in your dashboard. Authorised host administrators are trusted; this does not isolate secrets from an administrator who controls the execution machine.