AlgoRover Marketplace Privacy Policy
Effective date and version:
1. Scope
This Privacy Policy explains how Rivendell Holdings Investment Limited collects, uses, stores, and protects information when you use AlgoRover Research or the AlgoRover Live Marketplace.
AlgoRover Research can be used without an AlgoRover account. This Policy covers its catalog, recommendation, strategy-download, and historical-backtesting functions.
AlgoRover Live requires users to sign in to an AlgoRover account. Some Live features are available at no charge. For current information about access to other features, contact AlgoRover product support. This Policy covers the Marketplace catalog and strategy-download functions used through AlgoRover Live.
This Policy does not cover backtests, Paper trading, exchange Demo trading, live trading, order execution, or exchange-credential processing performed locally on your device.
2. Who we are
The AlgoRover Marketplace services covered by this Policy are provided by Rivendell Holdings Investment Limited, a company registered in the British Virgin Islands (“Rivendell,” “AlgoRover,” “we,” “us,” or “our”).
Company website: www.rivendell.capital
For product, privacy, security, installation, or compatibility questions, contact [email protected].
For corporate matters or formal legal notices, contact [email protected].
3. Information sent to AlgoRover
Research requests
You do not need an AlgoRover account to use AlgoRover Research.
Catalog requests may include:
- Search text
- Language and locale
- Asset, venue, category, and data-type selections
- Risk and capacity filters
- Sort order and result limit
- Requested strategy identifiers and versions.
Live Marketplace requests
You must sign in to an AlgoRover account to access the Live Marketplace.
We use your internal account identifier and feature-access settings to verify your sign-in and determine whether the requested feature is available to your account.
When you successfully download a Live strategy, the download is associated with your internal account identifier. Download records and related application logs do not store your email address, account cookie, bearer token, or refresh token.
Recommendation requests
A recommendation request may include information that you choose to provide, such as:
- Strategy concepts
- Assets and venues
- Categories and data types
- Profit style and holding period
- Risk, capacity, or drawdown preferences
- Trading mode
- Allocation range
- Instrument universe
- Language or locale.
We process recommendation requests and results only to return the requested response. The Research application does not store recommendation requests or results in its application database. It also does not write search text, filters, preferences, or recommendation content to application logs.
Recommendation requests do not contain AlgoRover account credentials or exchange credentials. Live account and feature-access checks are handled separately from recommendation content. AlgoRover Research rejects credentials submitted through its request fields.
Security and operational logs
Public requests generate limited security and operational logs. These logs may include:
- A keyed hash derived from the client IP address
- Request method and route
- Response status
- Request identifier
- Request time
- Relevant error or service information.
The AlgoRover Research application does not add the public request’s User-Agent to these application logs. However, ordinary HTTPS connections expose standard network information—including IP address, User-Agent, request time, and requested resource—to the service receiving the connection.
Strategy-download records
For each successful Research or Live strategy ZIP download, we record:
- Download channel
- Request identifier
- Strategy identifier and version
- Download time
- Delivery status
- Normalized complete client IP address
- Network quota key.
For IPv4 connections, the network quota key is the complete IPv4 address. For IPv6 connections, it is the normalized IPv6 /64.
A Live download record also contains the user’s internal AlgoRover account identifier. A Research download record does not.
Users who share a public IPv4 address, network-address translation service, or IPv6 /64 may also share the same source-network download allowance.
If a download request is rejected because the applicable allowance has been exhausted, no download record is created. Restricted application logs for that request may contain the network key, applicable quota category, route, strategy identifier and version, request identifier, and time.
These logs do not contain an email address, bearer token, refresh token, complete IPv6 client address, or strategy ZIP content.
4. Information not sent to AlgoRover
AlgoRover Research does not collect or send:
- AlgoRover account cookies
- Hardware or operating-system identifiers
- Browser fingerprints
- Persistent anonymous identifiers stored on your device
- Exchange credentials or API keys
- Local runtime-lock information
- Local datasets or imported CSV content
- Backtest inputs or results
- Local reports or charts.
The local Dashboard stores only non-identifying preferences, such as language and notice state.
Temporary local security tokens and process identifiers are not sent to the Marketplace.
5. Information stored on your device
The following information may be stored locally in the AlgoRover state directory on your device:
- Installed strategies and verification records
- Runtime files and virtual environments
- Wheel and catalog caches
- Downloaded or imported market data
- Processed instrument metadata
- Backtest inputs and runs
- Reports and charts
- Local Dashboard state.
You control this information. You may remove it through AlgoRover’s uninstall functions or your operating system’s file-management tools.
AlgoRover cannot remotely access, export, or delete information that remains only on your device.
6. How we use information
We use information received by AlgoRover Research and the Live Marketplace to:
- Provide catalog and recommendation responses
- Verify Live Marketplace sign-ins
- Determine which Live features are available to the user’s account
- Deliver requested strategy packages
- Apply source-network and account download limits
- Diagnose delivery failures
- Maintain service reliability and security
- Prevent fraud, misuse, and abuse
- Comply with applicable law.
The Marketplace services described in this Policy do not use personal information for advertising.
7. Service providers, third parties, and host platforms
Our cloud services and server-side storage are hosted in Singapore.
AlgoRover Research and AlgoRover Live connect to AlgoRover Marketplace services to access applicable features and strategy packages.
AlgoRover Research may also connect to:
- AlgoRover-hosted modified NautilusTrader packages
files.pythonhosted.orgfor public Python packages specified by the runtime lock- Public Binance Futures sources for historical market data when requested by a supported strategy preset.
Each third party processes information under its own terms and privacy practices.
The AI or coding platform hosting an AlgoRover plugin may independently process conversations, tool calls, and plugin-installation information. That processing is governed by the host platform’s policies, not this Policy.
We do not make privacy commitments on behalf of OpenAI, Anthropic, Binance, the Python Package Index, or any other third party.
Access conditions for some Live features have not yet been published. For current availability, contact AlgoRover product support at [email protected]. If AlgoRover introduces payment or billing processing, we will update this Policy before collecting payment or billing information through the Marketplace.
8. Retention
Successful strategy-download records are retained for 180 days. Backup copies may remain for up to 30 additional days before they are rotated out.
Application logs for requests rejected because a download allowance has been exhausted are retained for no more than 14 days under the current deployment configuration.
Other AlgoRover Research security and operational logs are retained for 14 days under the current deployment configuration and are then rotated out.
Expired daily and monthly download-counter records are deleted after the applicable UTC period ends.
Recommendation requests and results are not stored by the Research application.
Information stored only on your device remains there until you remove it.
Third parties may apply their own retention periods to information they receive.
9. Security
We use administrative and technical safeguards appropriate to the services we provide. These safeguards include:
- HTTPS encryption in transit
- Restricted application logging
- Keyed hashing of IP addresses used for ordinary public requests
- Trusted-proxy validation
- Access controls for download records containing complete IP addresses.
No system is completely secure.
Do not send passwords, account credentials, exchange credentials, API keys, or other secrets through Research or Marketplace request fields or by support email.
10. Your choices and rights
Depending on applicable law, you may have the right to ask whether we hold personal information about you and to request:
- Access
- Correction
- Deletion
- Restriction
- Objection
- A copy of your information.
For anonymous Research activity, we may need information such as the approximate client IP address, strategy, and download time to locate a download record. Identifiers used for ordinary public requests remain keyed hashes.
For Live Marketplace activity, we may use your signed-in AlgoRover account to locate applicable records.
Send privacy requests or complaints to [email protected].
We may need to verify your request. We may also retain information where required by law or where necessary for security, fraud prevention, dispute resolution, or legal claims.
You may also submit a complaint to a competent data-protection authority.
11. Age
The AlgoRover Marketplace services covered by this Policy are intended only for users aged 18 or older.
We do not knowingly offer these services to children.
12. International processing
When you use AlgoRover Research or the Live Marketplace, the information described in this Policy may be processed in Singapore and in other locations where applicable host platforms, package providers, or market-data providers operate.
Those locations may have data-protection laws different from the laws in your location.
13. Changes to this Policy
We may update this Policy when AlgoRover Research, the Live Marketplace, our data practices, or applicable legal requirements change.
We will publish the revised Policy at this URL and update its effective date and version.
Material changes will apply prospectively unless applicable law requires otherwise.
14. Contact
Product, privacy, and security enquiries: [email protected]
Corporate matters and formal legal notices: [email protected]
