Privacy Policy
This policy explains what information OptionsLive collects, how we use and share it, and the choices you have. It forms part of our Terms of Service.
This English version is authoritative.
1. Who we are
OptionsLive (the "service", "we", "us") is a non-custodial copy-trading tool operated at optionslive.trade. We are the controller of the personal information described here. Contact us about privacy at [email protected].
2. Information we collect
Information you give us:
- your email address or phone number, and a password. We store passwords only as a salted hash — we cannot see or recover your password;
- an optional display name and profile details you choose to add;
- the UID of your Bybit account, which you enter after signing up — it is kept with your account, also after you close it, and a key you connect later confirms it; and
- a referral code, if you arrive through one.
From connecting your exchange account:
- the API key and secret you provide for your exchange account. The secret is stored ENCRYPTED at rest and is used only to place copy orders and read the market and account data needed to run and report on your copying — never to withdraw;
- trading data from that account, such as orders, fills, positions, and balances, used to operate copying and show your performance.
When you pay profit-sharing fees:
- records of your prepaid profit-sharing fee balance — the funds you send to top it up, the fees deducted from it, any share of a fee credited to the master you copy, and related transaction references (for example a crypto transaction hash). These fee payments are non-refundable and non-withdrawable.
If you are a KOL in the referral program:
- the Bybit UID, or the wallet address and network, you give for withdrawals, and the device and IP address each withdrawal request comes from (to protect your balance).
A master who withdraws their share of fees gives the same details, and we record the same device and IP address, as a KOL does.
From third-party sign-in (only if you use it):
- from Google: a Google account identifier and your email address;
- from Telegram: your Telegram ID and username, which we also use to send notifications if you opt in.
Automatically:
- your IP address and basic device/browser information, used for security, abuse prevention, and rate limiting;
- the country your sign-in IP address points to, which our staff see on your account. We work it out on our own servers from an offline database; your IP address is not sent to anyone for this;
- a session cookie to keep you signed in, and usage information about how you interact with the service.
We do not collect government-ID or KYC documents. We do not hold or have withdrawal access to your trading capital, which stays in your own exchange account — the only funds you send us are the non-withdrawable profit-sharing fees described above.
3. How we use your information
- to create and operate your account and place the orders of the masters you copy in your connected exchange account according to your settings;
- to send you trade, security, and account notifications (by push or Telegram, where you have enabled them);
- to show your copying activity and performance;
- to calculate and charge profit-sharing fees, to credit the master you copy any share of a fee, and to maintain your prepaid fee balance;
- to secure the service, prevent fraud and abuse, and enforce our Terms;
- to attribute referrals, to credit and pay referral rewards, and to pay out the share of fees credited to a master; and
- to provide support and to comply with legal obligations.
Where the law requires a legal basis (for example under the GDPR), we rely on performance of our contract with you, our legitimate interests in operating and securing the service, your consent (for optional notifications), and compliance with legal obligations.
4. Cookies and similar technologies
We use only what the service needs to work. We use no analytics, advertising or tracking cookies, and no session-recording or analytics scripts. What we store:
- a signed session cookie that keeps you signed in and carries short-lived sign-in steps, such as an invitation code; it expires after 14 days without activity;
- a language cookie, only if you choose a language, kept for one year; and
- in your browser's own storage: your theme, whether you dismissed the install banner or a tip, whether you chose to load the TradingView calendar, and, for one visit, whether the app's opening animation has played.
Cloudflare, which sits in front of the site, may also set its own security cookie (such as __cf_bm) in your browser to tell people from bots.
The Calendar tab on the Markets page can show TradingView's economic calendar. It loads only after you choose "Load calendar": your browser then connects to TradingView, which may set its own cookies under its own privacy policy. Your browser remembers that choice until you select "Stop loading the calendar" under the calendar; cookies TradingView already set stay until you clear them in your browser. Nothing from TradingView loads anywhere else.
5. How we share information
We do NOT sell your personal information. We share it only:
- with your exchange (Bybit, Coincall or Binance), through the API keys you provide, in order to place and manage orders in your own account;
- with Google or Telegram, if you choose to use them to sign in or receive notifications;
- with the person who invited you, if you signed up through their link: your nickname or a masked email or phone number, your UID, the date you signed up, whether you have connected Bybit or are copying, and the rewards they earn from your gas deposits;
- with the master you copy: your nickname (or a masked email or phone number), your copy size, whether you are copying or paused, your funds while you copy, your profit after fees on their program (in total and per UTC day), and the fee shares they receive from you;
- with service providers that host and support the service, under confidentiality obligations — each one, and what it receives, is listed in section 12; and
- with authorities when required by law, or to protect the service, our users, or others.
We never disclose your API secret to other users, and we never withdraw or move your funds.
6. Notifications
If you enable them, we send trade and account notifications by web push and/or Telegram. You can turn these off at any time in the app, in your browser, or in Telegram.
7. Data retention
We keep your information for as long as your account is active and as needed to provide the service, then for any period required by law. When you disconnect your exchange keys, the stored secret is removed. You can ask us to delete your account and associated data, subject to legal retention requirements.
8. How we protect your information
We encrypt API secrets at rest, store passwords only as salted hashes, serve the site over encrypted connections, and restrict access to data. No method of storage or transmission is completely secure, so we cannot guarantee absolute security. Keep your credentials safe, and do not grant withdrawal permission on the API keys you connect.
9. Your rights and choices
Depending on where you live, you may have rights to access, correct, delete, or port your personal information, to object to or restrict certain processing, and to withdraw consent. You can disconnect your exchange keys or close your account at any time, and you can contact us to exercise your rights at [email protected]. [OPERATOR / counsel: add any GDPR / UK GDPR / CCPA-specific disclosures and supervisory-authority contacts that apply.]
10. International transfers
We and our providers may process your information in countries other than yours. Where required, we use appropriate safeguards for such transfers. [OPERATOR: state the hosting region and the transfer safeguards used.]
11. Children
The service is not intended for anyone under 18, and we do not knowingly collect information from children.
12. Third-party services
These are the third parties the service sends your information to, and what each one receives:
- Bybit, your exchange: we call its API with the keys you connect, to place and manage orders and to read your balances, positions, fills and transfers. On the Markets and Assets pages your browser also receives public prices straight from Bybit, which sees your IP address.
- Coincall, if it is your exchange: we call its API with the keys you connect, to place and manage orders and to read your balances, positions and fills.
- Binance, if it is your exchange: we call its API with the keys you connect, to place and manage orders and to read your balances, positions and fills.
- Google, if you sign in with Google: we receive your Google account ID, email address and name, and whether the email is verified.
- Telegram, if you sign in with or link Telegram: we receive your Telegram ID, name and username, and send your trade alerts, daily summaries, password-reset links and withdrawal updates through Telegram's bot service. Our staff also receive alerts through Telegram that can include your account number or account ID, amounts, and a withdrawal destination.
- Your browser's push service (Google, Apple, Mozilla or Microsoft, depending on your browser), if you turn on push notifications: it delivers each encrypted notification to your device.
- Cloudflare, which sits in front of the site: every request to optionslive.trade passes through its network, which handles the encrypted connection, filters attacks and caches public files, so it sees your IP address, browser details and the pages you request. When something looks abnormal on sign-in, sign-up or password reset, it also runs its Turnstile bot check in your browser.
- Cloudflare, as our email service: it delivers our emails to your address — sign-up, sign-in and security codes, password-reset links, account notices (for example that an account already exists, or that an AI agent or Telegram was linked) and, for KOLs and masters, withdrawal codes and payout notices. Cloudflare also forwards mail you send to [email protected] to our mailbox at Google (Gmail).
- Our hosting provider: it stores and runs the service.
- TradingView, only if you choose to load the calendar on the Markets page: your browser loads its calendar, and TradingView receives your IP address and browser details and may set cookies.
Each of them handles your information under its own privacy policy, which we do not control.
13. Changes to this policy
We may update this policy from time to time. If we make material changes, we will take reasonable steps to let you know.
14. Contact
Questions about your privacy: [email protected].