Trust & Security

What data we collect, and why

To run your account, license, signals subscription and support requests, we collect the information you give us directly: your name, email and phone number; your orders, payment references and license/MT5 account details; messages you send us; and — only if you request identity verification or a payment partner requires it — KYC identity documents. We use this strictly to provide the service you signed up for: activating and renewing products, delivering signals, processing payments, verifying identity where a partner requires it, and responding to support requests. We don't sell your data to third parties. This page is a short, honest summary — for the full legal detail (retention periods, sub-processors, your rights) see our complete Privacy Policy.

Security measures already in place

• 🔐 The site is served over HTTPS, so data you submit (login, payment details, messages) is encrypted in transit.
• ☁️ Traffic passes through Cloudflare's network in front of our servers for network-level protection.
• 🔑 Passwords are never stored in plain text — they're hashed with a one-way algorithm we can't reverse.
• 📱 Optional two-factor authentication (an authenticator-app TOTP code, with backup recovery codes) is available on every client account.
• 🕵️ Admin access is session-controlled, and every sensitive admin action (price changes, license changes, approvals) is written to an internal activity log.
• 🗂️ Identity-verification documents you upload are only accessible to authorized staff, and only for verification purposes.

We're a small team and treat this as ongoing work, not a finished checklist. If you ever spot a security issue, please tell us at support@vexriano.com — we take reports seriously.

🔐 Encryption across the platform

Security isn't limited to this site's own account protections above — it's how we've built two other things you may already use. Direct messages and group chats are end-to-end encrypted: your messages are unreadable to us in transit or at rest, decryptable only by the people in that conversation.

Uptime & incident history

Not enough history yet — this tracker starts filling in as our health-check endpoint gets polled over time. Check back soon.

This section reflects our own logged health checks, not a third-party monitor. It updates automatically — no manual editing.