Effective 2026-10-08 · English
Privacy notice
How browser-only chart use differs from optional accounts, account copies, payments and server-delivered features.
1. Browser chart data
You can use the chart without an account. Workspaces, drawings, local alerts, preferences and cached market history are stored on your device using browser storage. We do not automatically upload your saved setup. Clearing site data can erase it. Direct exchange connections disclose normal connection metadata, including your IP address, to the exchange; some requests instead use Klustra’s proxy or archive.
2. Optional account and security
Signing in requires an email address. You can sign in with a one-time code or link sent to it, a password, Google or a passkey; each opens the same account. We store the account ID, email, creation time, launch-coupon claims, subscription records, hashed login/session tokens and one-time codes, coarse device labels such as browser and operating system, and which way each session signed in. If you set a password, your browser turns it into a derived key before sending it, and we store only a salted, keyed hash of that key, never the password. If you sign in with Google, we receive your Google account’s email address and account identifier and keep both to recognise you; we do not receive your Google password, contacts or profile, and Google learns that you signed in to Klustra. If you add a passkey, we store its public key, credential ID, a coarse device label and when it was added and last used; its private key stays on your device or with your passkey provider. The klustra_session cookie is HttpOnly and SameSite=Lax, secure over HTTPS, with a 90-day lifetime that may be renewed during use; during a Google sign-in a klustra_oauth cookie holds the sign-in state for up to 10 minutes. Both are used for authentication, not advertising. Sign-in abuse controls store SHA-256-derived buckets for email and source IP; these hashes remain potentially identifying security data.
3. Account copies
Only an explicit save uploads a copy of saved workspaces, drawings and browser alerts. The copy can reveal instruments you follow, chart settings, drawn levels and alert thresholds. New saves replace the account copy; delete removes the live copy but leaves a revision tombstone. Restoring does not delete local items and newly imported alerts are disarmed. The account-copy limit is 256 KiB; deletion does not erase copies already restored to devices or exports you made.
4. Server alerts and archive usage
Creating an email or Telegram alert stores its instrument, condition, delivery channels, settings and revision under your account. We use your account email for email delivery and keep delivery/retry records. If you connect Telegram, you give us the token of a Telegram bot you created and the ID of the chat it should write to. We store the token encrypted, together with the chat ID and the bot and chat names Telegram reports, and use them only to send your alerts and the messages you ask for (a connection check and tests); to help you find the chat ID, we read your bot’s recent updates once when you ask, without keeping them. Alert messages, which name the market, level and price, pass through Telegram under its own privacy policy. Disconnecting in the Alerts panel deletes the stored token and chat; if your bot can no longer reach the chat (for example, its token was revoked in @BotFather or the bot was blocked), we delete them too. Deletion disables the saved server alert through a tombstone. Archive downloads record account, object/version, admitted byte count and UTC day to enforce allowances and single-use links. A previously downloaded market file cannot be revoked from your device.
5. Trading journal
If you use the journal (Pro), the trades you log (instrument, side, prices, size, fills, fees and times), your notes, setup, tags, mistakes and rating, and one screenshot of the chart per trade are stored under your account so they appear on every device you sign in on; bar replay backtest trades are stored the same way. Screenshots are kept in private storage and served only to your account. Each signed-in browser also keeps a working copy in browser storage. Deleting a trade or journal erases its content and screenshot and leaves a revision tombstone, so your other devices remove their copy when they next sync. Limits: 50 journals, 5,000 trades and one screenshot of up to 150 KB per trade.
6. Payments and service emails
We retain order/payment identifiers, quoted price, asset/network, provider status, settlement evidence, subscription grants and reminder records to deliver access and investigate disputes. NOWPayments separately processes transaction, wallet and network information and may require identity checks under its own policies. Blockchains are public; on-chain transfers cannot be erased by Klustra. Cloudflare’s email service processes recipients and message content for sign-in, security notices, alerts, renewal reminders and journal deletion notices; these are service emails you cannot opt out of while you hold an account.
7. Product announcements
We occasionally email account holders about the product itself, such as a closing launch offer. These are infrequent, are sent to your account address only, and are separate from the service emails above. If you open a Pro checkout and leave it unpaid, we may also send one reminder about that checkout, about an hour later and never more than one a week; it is an announcement in every respect below. Every one carries an unsubscribe link and one-click unsubscribe headers; unsubscribing stops announcements immediately and affects nothing else — sign-in links, security notices, alerts, renewal reminders and journal notices continue. We record that an announcement was sent to your account and that you unsubscribed, so it is not repeated; the opt-out is stored against your email address and is kept even if the account is deleted, so that a later account with the same address stays unsubscribed. We do not track opens or clicks, and announcement links carry no per-recipient identifier. We do not share or sell your address, and we do not use a third-party marketing platform: these are sent by the same Cloudflare email service as everything else.
8. Usage counters and infrastructure
First-party usage counters contain an allowlisted event name, a short label and sometimes a count. The analytics endpoint does not write IP addresses, user agents, referrers or account/session identifiers into those counters. Cloudflare hosts the site and account database, stores the archive and provides Turnstile abuse protection; normal network/security metadata is processed by the infrastructure provider. This is not a promise that no server ever receives connection information. Third-party advertising scripts are not used. Free users see affiliate links to trading partners (exchanges and a prop-trading firm); Klustra may earn a referral commission from them at no cost to you.
9. Retention
Local storage remains until you or your browser remove it. Account copies remain until replaced or deleted. Account, sign-in method, billing, grant, reminder, alert-configuration and Telegram-link records are kept while your account exists (a Telegram link, Google link or passkey until you remove it) and as long as needed to deliver access and resolve payment disputes. Expired login-token cleanup, security rate-limit cleanup, alert delivery cleanup after approximately seven days and archive-meter cleanup after approximately thirty days run in bounded maintenance batches; outages or backlog can delay removal. Expired session records may remain until revocation or maintenance. An announcement unsubscribe is kept indefinitely, including after account deletion, because deleting it would resubscribe you. Journal records remain until you delete them. If Pro ends, the journal stays readable, exportable and deletable for 12 months after Pro access ends; it is then deleted, after an email to your account address at least 30 days before, and renewing before that date keeps it. A browser removes its copy when it next syncs; exports you made are not affected. If your account is deleted, its journal records are deleted with it and its screenshots are removed by a maintenance sweep.
10. Controls and requests
Use the account page to delete the live account copy, revoke sessions, remove passkeys and disconnect Google, the alert controls to disable or delete server alerts and to disconnect Telegram, and the Journal to export or delete your trades and journals, with or without Pro. Use the unsubscribe link in any product announcement to stop announcements; support will also do it on request. Local storage and workspace exports are controlled by you. Account deletion, access/export requests and privacy questions are handled by support; there is no self-service account-deletion flow. Klustra is operated by Shabir Hussain Mirzayee; contact info@klustra.app for privacy requests.
Provider policies
Cloudflare privacy policy · NOWPayments privacy policy · NOWPayments terms of service · NOWPayments service eligibility · Telegram privacy policy · Google privacy policy