Using your terminal

Create your Ticklab username and separate Ticklab password first. Do not enter your Deriv password into Ticklab. Then connect your own Deriv login, choose strategies and review settings before trading.

1. Select Connect Deriv and sign in on Deriv. Approve trading permission, then choose an available USD account. Choose Demo to test your settings.
2. Turn each bot on or off. Open its panel to set its entry, stake, TP1 and recovery. Each bot retains its own progression. Set the shared take profit, loss budget and contract limit.
3. Select Start. Check the account, bot lineup and every displayed setting. Confirm and start begins scanning; cancel leaves trading stopped.
4. The first fresh qualifying signal gives that bot control until its own TP1 or stop loss. Other bots continue observing. After its submitted contracts settle, the next fresh signal can select another bot.
5. Pause stops new entries and keeps the active progression. After submitted contracts resolve, Start lets you review and resume. Emergency stop blocks new purchases immediately and remains visible while scrolling.
6. Reset stops entry, requests closure of an open accumulator and waits for submitted receipts. It then clears this session's history, counters and progression while keeping your settings.

Save, import and choose settings

The settings library saves named complete setups to your own Ticklab account. Generate a settings code to share parameters, or paste an exported TL1 code and load it. Loading and importing never start a trade. Check the parameters and confirm Start separately.

Quick setup filters the owner’s examples into Low risk and High risk categories. There can be several named choices per strategy. The owner can publish a bot’s individual parameters from the terminal or dashboard. Selecting “enable only that strategy” switches other standalone bots off. Shared session limits remain yours.

High risk requires a current USD balance of $200 by default. The owner can change this for each client. Custom settings are not automatically classified as high risk. The minimum applies to selected High risk quick setups. Labels do not guarantee safety. The server verifies the current classification and selected account balance before Start; live balance checks pause new purchases below the minimum. A restored balance never starts trading by itself.

Accumulator entries and exits

Entry counts describe completed barrier runs. Choose consecutive qualifying runs, a qualifying count within a period of completed runs, or exact zero runs with either consecutive or period counting. A threshold of 10, count 3 in period 4 accepts 6 → 18 → 3 → 8. Two consecutive zeros accepts 0 → 0.

The accumulator opens one contract for a fresh qualifying entry. The bot requests a sell when its configured profit target is observed. Recovery uses that bot's own selected recovery settings and verified previous loss. Shared session limits also apply.

Keep your session connected

Keep this browser open and connected for trading and accumulator exits. Phone background restrictions, network delays and broker limits can interrupt execution. Separate paired purchases may receive different broker entry or exit ticks. Targets can differ from final proceeds after submitted contracts settle.

One active browser may trade an account at a time. Other visitors connect their own accounts independently. Voice announcements can be muted without changing trading. To sign out, pause and let submitted contracts resolve, then open the account panel.

Public data and rate-limit recovery

Market data starts publicly when this page opens. Your separate authenticated connection handles purchases, sells, balances and receipts. Public data also has rate limits; completed checks are retained during retry delays.

Each bot has its own stop loss in its panel. The limit uses the current run’s trading results. Reaching it ends that run while other eligible strategies keep scanning. The same strategy may qualify again in a later cycle.

Under Session limits, expand Rate-limit recovery. Choose Over/Under, Even/Odd, fixed Over 5 + Under 4, Both (Over/Under and Even/Odd), or All three. Recovery waits for confirmed receipts, the cooldown and a fresh configured entry. It uses separate progression, contributes to shared TP2 and returns to fresh-entry scanning after its current-loss target is confirmed. Start never bypasses the settings review.

Choose the next strategy

Option 1 allows the same strategy on consecutive cycles. Option 2 requires a different strategy after a completed TP1 or stop-loss run. A later run starts from a fresh entry and its own loss baseline. If only the previous strategy is enabled under Option 2, the terminal waits; pause to change this setting.

Your account and devices

Use Account & devices to view signed-in sessions, sign out a device and change your Ticklab password. Your first successful Deriv connection links your Ticklab account to that Deriv identity; its Demo and Real accounts are allowed. A different Deriv login is refused until the owner resets the link.

For help with your Ticklab access, contact support. Forgot your Ticklab password? Request help on the login page; the owner can provide a private one-time reset link after verifying you. You choose the replacement password yourself.

Authenticator and owner recovery

Open the hamburger menu, then Account settings. Enable two-factor authentication with your Ticklab password and an authenticator app. Save the one-use 2FA backup codes offline. Once enabled, login requires both your password and a fresh code or unused backup code.

Owners also have separate emergency recovery codes and a verified recovery email. Configure a TLS SMTP sender privately, then open the verification email’s link. Recovery email is not ready until verified. Email password recovery keeps 2FA enabled; an owner emergency code can restore access when the authenticator is lost. Generate and store recovery codes before you need them. The owner recovery page is linked from login and the side menu.

Owners publish phone, TikTok, Telegram and WhatsApp support links from the dashboard. Clients see those details in the side menu.

Device privacy and account deletion

Client account IDs are hidden in account summaries, account choices and Start review. Each new Ticklab sign-in needs a separate Deriv OAuth connection on that device before trading. Sign in on Deriv’s own page using the same linked Deriv login; a different identity is refused. Your Ticklab password alone cannot connect Deriv from another device.

To request deletion, open Account settings and expand Request account deletion. Confirm your current password and your second factor when enabled. The owner reviews the request; you can cancel it while pending. The owner can permanently delete a client from their expanded dashboard row after confirming the exact username and owner password/factor. The owner account is protected. Deletion removes live Ticklab account data and saved connections; your Deriv account and broker-held history remain with Deriv.

Reset and account tabs

Press Use this tab to deliberately take trading control. Switching tabs and ordinary clicks do not transfer it. A countdown shows any wait for the previous permission, and Cancel transfer stops the attempt. Press Reset session to clear the settled account session in this tab. New purchases stop in the previous account tab. A notice shows any running activity and open or unconfirmed trades. Reset keeps tracking those trades until final broker receipts arrive; it never repeats an uncertain purchase.

After settlement, previous session profit, orders, progression, recovery and activity are cleared across the account’s browser tabs. Returning tabs cannot restore the old session. Your sign-in and saved settings are kept. Review Start and wait for a fresh entry to begin again. A frozen tab may require the execution lease to expire before control can move. Cloud sessions remain separate: reset or stop them in Cloud mode.

Log out all tabs

Use the trading-tab controls, the side menu, or Account → Signed-in devices. This signs out all your Ticklab tabs and devices, stops new buys and requires fresh sign-in and Deriv OAuth. Idle tabs go to sign-in. A connected trading tab keeps tracking submitted or uncertain trades until final receipts are saved, then signs out. Saved settings and the linked Deriv identity are kept. A sleeping cloud run with unresolved contracts retains its journal for recovery.

If the worker stops or an operation times out, trading remains paused. Reload terminal recovers saved records; Start always requires a fresh review and verified ownership. An unresolved purchase is never automatically retried.