1. Scope and operator
This policy describes information associated with the Marketlab website, documentation, and locally installed CLI and daemon. You can contact Marketlab through @gurtcrypto on Telegram.
The website and locally running software have different data flows. A connection to an exchange, market-data provider, or other external service is also subject to that service’s own practices.
2. Website information
Website hosting and delivery services may receive request information such as IP addresses, requested URLs, browser details, and timestamps.
This website includes optional Databuddy analytics, activated when the deployment has an analytics client ID. Its configured features cover page interactions, outgoing links, errors, attributes, performance, and web vitals.
The Contact page links to @gurtcrypto on Telegram. There is no contact form on this website. If you send a message, its contents and the profile information you share are available to the recipient through Telegram. Telegram’s own privacy practices also apply.
3. Data on your machine
Marketlab maintains local state, including configuration, market snapshots, job records, logs, and strategy artifacts, on the installation running the software. An SSH connection can direct commands to a different installation; its state and credentials belong to that machine.
Delegated trading-agent credentials are stored locally with owner-only file permissions. They are not encrypted at rest so unattended jobs can restart. A person or process with sufficient operating-system access may read them. Main-wallet approval keys are not retained by the documented authorization workflow. These facts do not mean that no keys are stored.
Python scripts run with the permissions available to their runtime. Process isolation provides reliability safeguards, not a security sandbox. Run only scripts and dependencies you trust, and avoid including secrets in code, logs, or support messages.
4. Connected services
When you request data, query an account, or authorize execution, the selected providers receive the information needed to handle those requests. This can include market identifiers, account identifiers, signed instructions, and order details. Blockchains and venue systems may make transaction information publicly observable.
Marketlab does not control the retention or publication rules of exchanges, data providers, package registries, or third-party websites. Review the providers you choose before connecting them.
5. Purpose, sharing, and retention
Website information is used to deliver pages, understand aggregate usage, diagnose failures, and respond to requested support.
Local records remain under the control of the installation operator, subject to the software’s storage behavior and any backups you maintain. Removing local files does not remove exchange records, blockchain history, or copies already supplied to other services.
For questions about website or support-message retention, service providers, or processing locations, contact Marketlab through the Contact page.
6. Your choices
You can choose which services to connect, remove locally configured provider credentials, and manage files and backups on machines you control. Revoke an agent at the relevant venue when appropriate; deleting a local file alone may not revoke a remote authorization.
Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to certain processing. To ask about your information or exercise applicable rights, contact @gurtcrypto on Telegram. Do not include private keys or trading credentials in your request.
7. Updates and contact
This policy is effective September 16, 2026. Updates will be published on this page with a revised date. For questions about this policy, contact @gurtcrypto on Telegram.