This notice describes the intended privacy model for Veeval’s website, client onboarding, private Telegram access, licences and bot-fleet telemetry. It is a launch foundation and should receive jurisdiction-specific legal review before broad commercial release.
Depending on the product and onboarding flow, Veeval may process contact details, broker/account reference information used for eligibility, Telegram identifiers, product entitlements, licence/device identifiers, bot version and health telemetry, and trading-system lifecycle data needed to operate and audit the service.
Veeval’s central services should not request or store a client’s MT5 trading password or unrestricted broker credentials. Broker login secrets remain inside the client-controlled terminal/environment.
Information is used to verify eligibility, provide private client access, bind licences and devices, maintain fleet health, deliver product updates, prevent abuse, support customers and preserve operational/audit records.
Owner/admin interfaces are protected separately from the public website. Veeval’s architecture uses restricted service accounts, protected secrets, signed/versioned control messages and audit logging as the production system is completed.
Operational and trading audit records may need different retention periods from contact/onboarding data. Veeval should document final retention schedules before commercial launch and delete or anonymize data when it is no longer needed or legally required.
Privacy questions can currently be directed to contact@veeval.com. Additional controller/legal identity details and applicable rights should be added after jurisdiction-specific review.