This notice describes the intended privacy model for Veeval’s website, client onboarding, private Google Drive integration, 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, trading-system lifecycle data, and owner-authorized Google Drive files needed to operate and audit the service.
When the Veeval owner explicitly connects Google Drive, Veeval uses the authorized access only for the stated Veeval file-transfer and development workflow. With read-only Drive access, Veeval may view and download files available to the connected account but does not use that permission to edit or delete Drive content. Google user data is not used for advertising, sale, unrelated profiling or unrelated marketing.
Veeval's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. More detail is available on the Google Drive Integration page.
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, transfer owner-authorized development files, 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. OAuth credentials must remain in protected server-side configuration and must not be committed to public source code.
Operational and trading audit records may need different retention periods from contact/onboarding data. Google Drive files synchronized into Veeval infrastructure should be retained only as needed for the owner-authorized workflow. Veeval should document final retention schedules before broad commercial launch and delete or anonymize data when it is no longer needed or legally required.
The connected Google account can revoke Veeval's access through Google Account security controls at any time. Veeval can also disconnect the integration from its server-side configuration.
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.