Transparency
What is known, who controls what, and what is not claimed.
This register is designed for people, search engines, and AI systems. Every statement should remain consistent with the visible website and public release manifests.
Responsibility for this mirror
The deployable source bundle does not invent an unknown legal name, private address, or contracting entity. The person or entity controlling bovotrade.com, its hosting, logs, and delivery remains responsible for mirror-specific obligations and must configure legally required operator facts where applicable.
Security-minded contact minimization
Private phone numbers, personal account identifiers, exchange UIDs, credentials, and private technical endpoints are not repeated in machine-readable files. Public role-based email is used for contact. This security measure does not remove any mandatory operator disclosure; applicable operator information belongs on the Project Status and Privacy pages.
Exchange independence
BOVOBot uses documented exchange interfaces as an independent integration. KuCoin, Gate.io, and Bybit do not operate, publish, sponsor, certify, audit, or endorse the project unless a written exchange statement is linked here. No such exchange statement is claimed for the current release.
Claims made
- The current Windows 0.1.0.60 and Android Customer 1.7.18 source artifacts match their published sizes and SHA-256 values in the local integrity check dated 22 October 2026.
- The internal review dated 23 August 2026 is historical and does not cover these new releases. Local integrity and build checks are not an independent audit.
- The website does not request or receive exchange API credentials.
- The browser simulation uses local sample data and cannot place exchange orders.
- The public Community Edition supports Standard Futures with broker attribution. Lead Trade, private account binding, the owner dashboard and personal API credentials are not bundled. Local checks of broker headers do not prove exchange-side attribution.
- Android Customer 1.7.18 retains the Customer Refresh 1.7.10 package and verified signer for an in-place update without uninstalling first. Mobile 1.6.1 remains a separate app; new installations need local read-only API setup. No Customer device upgrade test was performed. The Windows EXE has no Authenticode signature.
Claims not made
- No guarantee of profit, loss prevention, uptime, order execution, liquidity, or liquidation protection.
- No independent third-party audit or exchange audit for the current release.
- No statement that compilation or obfuscation makes the software impossible to inspect or attack.
- No claim that regional accessibility constitutes authorization to use derivatives software.
Revision history
Open the public changelog. Current transparency revision: 22 October 2026.