VectorBT PRO v2026.9.5 includes native Rust simulators, streaming indicators, and portfolio continuation. Explore features

Privacy Policy

How VectorBT PRO handles personal data on this website

Last updated: September 3, 2026

This Privacy Policy explains how personal data is handled when you visit vectorbt.pro or members.vectorbt.pro (together, the Site), contact us, or start a VectorBT PRO membership purchase from the Site.

1. Who is responsible for your data?

Oleg Polakow, established in Ukraine, is the data controller for the processing described in this policy.

For privacy questions or requests, email olegpolakow@vectorbt.pro.

Postal address: Henerala Chuprynky St, 6, L'viv, L'vivs'ka oblast, Ukraine, 79000.

2. What data do we process?

Site delivery and security

When you access the Site, the systems used to deliver it may process technical request data such as your IP address, date and time of access, requested URL, referring page, browser and device information, and error or security events. This data is needed to deliver the Site, maintain its reliability, diagnose problems, and prevent abuse.

Necessary browser storage

The Site stores your cookie-consent choice in the vectorbt-pro-cookie-consent cookie for 180 days. The Site may also store interface preferences, such as your selected theme, dismissed notices, or tab choices, in your browser. This preference data remains on your device and is used to provide the interface you requested.

Documentation search runs in your browser. Search terms are not sent to a search service or included in analytics events.

Member website access

The member website at members.vectorbt.pro requires you to sign in with GitHub. When you sign in, we process your GitHub user ID and username and check whether your account has access to the private VectorBT PRO repository. GitHub handles the sign-in interaction under its Privacy Statement.

The member website uses the following strictly necessary cookies:

CookiePurposeDuration
__Host-vbt_members_oauth_state_*Secures the GitHub sign-in flow and prevents request forgeryUp to 10 minutes
__Host-vbt_members_sessionKeeps you signed in and allows the Site to periodically verify your accessUp to 30 days

These cookies are marked HttpOnly, Secure, and SameSite=Lax. They are required to provide and secure access to the member website, so they are not controlled by Cookie settings.

Optional analytics

With your consent, the Site uses Google Analytics 4, provided by Google Ireland Limited, to understand visits and improve the Site and its documentation. It may receive a pseudonymous browser identifier, pages viewed, links and other Site interactions, referrer information, browser and device information, approximate location derived from your IP address, and documentation search activity without the search terms.

Analytics is off unless you accept it. Advertising storage, Google Signals, and ad personalization are disabled. The Site does not use analytics data for targeted advertising.

Google Analytics uses these first-party cookies:

CookiePurposeDuration
_gaDistinguishes visits for aggregate analyticsUp to 180 days
_ga_0C5VNYCFHLMaintains the current analytics session stateUp to 180 days

You can withdraw consent at any time through Cookie settings in the Site footer. Withdrawing consent stops future analytics collection and removes the analytics cookies covered by the consent tool. It does not affect processing that took place before withdrawal.

See Google's privacy policy and information about Google Analytics data safeguards for more information.

Memberships and payments

The Site offers payment choices through GitHub Sponsors, Ko-fi, Patreon, Stripe, Paddle, and Gumroad. If you follow a payment link, you leave the Site and the selected provider processes data under its own privacy policy. Paddle checkout can instead open on the Site; the Paddle script is loaded only when you prepare to use or request that checkout.

Depending on the provider and payment method, the provider may collect your name, contact and billing details, account identifiers, payment details, IP address, and information about the product and transaction. We do not receive your full payment-card number. We may receive the details needed to confirm the purchase and provide membership access, such as your name or username, email address, plan, transaction identifier, payment status, and subscription dates.

The payment providers act under their own terms and privacy notices for their payment, fraud-prevention, legal, and compliance activities:

If you contact us about a cryptocurrency payment, we process the information you provide and the transaction details needed to arrange the payment, confirm it, and provide access.

Communications

If you email us or otherwise contact us, we process your contact details, the content of your message, related records, and any information you choose to provide so that we can respond, support you, and keep an appropriate record of the communication.

3. Why can we process this data?

Where the GDPR or similar law applies, we rely on the following legal bases:

PurposeLegal basis
Delivering, securing, and troubleshooting the SiteLegitimate interests in operating a reliable and secure Site
Remembering consent and requested interface settingsLegitimate interests in providing the Site and, where applicable, compliance with legal obligations
Providing and securing access to the member websitePerformance of a contract and legitimate interests in restricting member content to authorized members
Optional analyticsConsent
Processing purchases and providing membership accessSteps requested before entering a contract and performance of a contract
Tax, accounting, fraud prevention, disputes, and complianceLegal obligations and legitimate interests in protecting the Services and legal rights
Responding to messages and support requestsSteps requested before entering a contract, performance of a contract, or legitimate interests in communicating about the Services

When we rely on legitimate interests, we consider whether those interests are outweighed by your rights and interests.

4. Who receives your data?

Personal data may be disclosed only as needed to:

  • providers that host and deliver the Site or help maintain its security;
  • Google Ireland Limited, if you consent to analytics;
  • the payment or membership provider you choose, and providers involved in completing that transaction;
  • professional advisers, auditors, insurers, or public authorities where reasonably necessary to comply with law or establish, exercise, or defend legal claims; and
  • a successor in connection with a sale, merger, or reorganization, subject to appropriate safeguards.

We do not sell personal data or share it for cross-context behavioral advertising.

5. International transfers

Some recipients may process personal data outside your country, including outside the European Economic Area. Where required, transfers are based on a valid legal mechanism, such as an adequacy decision or standard contractual clauses, together with supplementary safeguards where appropriate. The linked provider privacy notices explain their locations and transfer safeguards.

You may contact us for more information about safeguards relevant to your personal data.

6. How long do we keep data?

We keep personal data only for as long as needed for the purposes described above, including legal, tax, accounting, security, and dispute-resolution requirements.

  • The consent cookie and Google Analytics cookies last for up to 180 days unless you remove them sooner.
  • The member website's GitHub sign-in state cookies last for up to 10 minutes, and its member session cookie lasts for up to 30 days unless you sign out or remove it sooner.
  • Google Analytics user-level and event-level data is retained for no longer than 14 months and may then be deleted or kept only in aggregated form.
  • Purchase, membership, and transaction records are kept for the duration of the membership and afterward for the period required by applicable tax, accounting, consumer-protection, and legal-claims rules.
  • Correspondence is kept until the request is resolved and afterward only as long as reasonably needed for support continuity, compliance, or legal claims.
  • Technical logs are kept for the period reasonably necessary for delivery, security, troubleshooting, and abuse prevention.

Data may be kept longer when required by law, a dispute, or a valid legal hold.

7. Your choices and rights

Depending on where you live, you may have the right to request access to, correction of, deletion of, or restriction of your personal data; object to certain processing; receive portable data; and withdraw consent at any time. You may also have the right to appeal a decision about your request.

To exercise a right, email olegpolakow@vectorbt.pro. We may need to verify your identity before completing a request. Rights can be subject to legal conditions and exceptions.

If you are in the European Economic Area, you may lodge a complaint with the data protection authority where you live, work, or believe an infringement occurred. The European Data Protection Board provides a directory of national authorities. You are welcome to contact us first, but you do not have to do so.

The Site does not make decisions about you based solely on automated processing that produce legal or similarly significant effects.

8. Children

The Site is not directed to children under 13, and we do not knowingly collect personal data from them. If you believe a child under 13 has provided personal data, contact us so that we can investigate and delete it where appropriate.

9. Security

We use reasonable technical and organizational measures intended to protect personal data. No method of transmission or storage is completely secure, so absolute security cannot be guaranteed.

The Site links to third-party websites. Those third parties are responsible for their own privacy practices, and this policy does not cover data they collect when you visit their services, except for personal data they provide to us in connection with a membership or transaction.

11. Changes to this policy

We may update this policy when the Site, our practices, or legal requirements change. The date at the top shows the latest revision. If a change materially affects how we rely on consent, we will request consent again where required.