LegalPrivacy
Cookie and Local Storage Policy
Technical inventory of cookies, localStorage, sessionStorage, chrome.storage, and IndexedDB artifacts used by copyx.trade and the CopyX Chrome Extension, strict-necessity exemptions, and purge instructions.
This Cookie and Local Storage Policy (“Storage Policy”) supplements and forms part of our Privacy Policy, explaining every browser storage artifact set or read by copyx.trade and the CopyX Google Chrome extension (the “Extension”). Capitalized terms have the meanings defined in the Terms of Service and Privacy Policy.
STRICT-NECESSITY & ZERO-TRACKING SUMMARY. Neither
copyx.tradenor the Extension uses any advertising, behavioral-profiling, cross-site tracking, or third-party analytics cookies. Every storage item listed below is strictly necessary to deliver a user-requested interface preference, protect the Website against automated abuse, or execute local client-side trading and Order Replication in your browser. Under EEA/UK ePrivacy rules (Directive 2002/58/EC Art. 5(3) and UK PECR Reg. 6), strictly necessary storage does not require a consent banner.
1. Storage Technologies Used
This Storage Policy covers four browser technologies:
- HTTP Cookies: Small text files set by a domain (such as Cloudflare on
copyx.trade) and transmitted back to that domain with subsequent HTTP requests. - Web Storage (
localStorageandsessionStorage): Key-value storage isolated to a specific website origin and never automatically transmitted in HTTP headers (localStoragepersists until cleared;sessionStorageis wiped when the browser tab closes). - Chrome Extension Storage (
chrome.storage.localandchrome.storage.session): Sandboxed storage accessible exclusively to the CopyX Extension (chrome.storage.localpersists until the Extension is uninstalled;chrome.storage.sessionis held in memory only and wiped when Chrome closes;chrome.storage.syncis never used by CopyX). - Browser
IndexedDB: Origin-isolated structured database storage inside Google Chrome, used by the Extension for three purposes only: the local order log (retaining the history of completed orders for 30 days), the random salt used to hash account identifiers in that log, and the non-exportable WebCrypto key that encrypts saved Platform logins.
2. Storage Artifacts on copyx.trade
| Artifact Name / Key | Storage Mechanism & Origin | Strict Technical Purpose | Retention Duration |
|---|---|---|---|
copyx-lang |
localStorage (copyx.trade) |
Retains your selected display language (en or zh) across page loads |
Persistent until cleared by user |
copyx-intro |
sessionStorage (copyx.trade) |
Ensures the landing-page hero animation plays only once per tab session | Deleted when the browser tab closes |
copyx.account-tab |
localStorage (copyx.trade) |
Remembers the last active account tab in the interactive simulated chart demo | Persistent until cleared by user |
cf_clearance (only if Cloudflare presents a security challenge) |
HTTP Cookie (copyx.trade, set by Cloudflare) |
The Website’s own code sets no cookies, and no cookie is set during ordinary visits. Only when Cloudflare, our host, presents a security challenge to a visitor may it set this strictly necessary cookie to record that the challenge was passed | As configured by Cloudflare |
3. Storage Artifacts Inside the CopyX Extension (chrome-extension://)
All items in this Section 3 reside exclusively within the Extension’s sandboxed storage on your local computer, are never sent to CopyX, and are automatically and permanently deleted when you uninstall the Extension from Google Chrome. The Extension does not use chrome.storage.sync.
| Storage Area | Stored Data Elements | Encryption & Security Posture | Retention Duration |
|---|---|---|---|
chrome.storage.local |
(a) each saved Platform login, encrypted: your username and password, together with the session token issued by Tradovate or TopstepX or your Rithmic system name and chosen gateway, and, after you log out, the username and password kept for the login form; (b) the daily limits and personal locks you set on Rithmic accounts; and (c) markers containing no personal data (that you accepted the data notice, that the Extension’s databases have been set up, and when they were found cleared) | Saved logins are encrypted with AES-GCM under the non-exportable WebCrypto key held in the Extension’s IndexedDB |
Saved logins: logging out deletes the session token but keeps the username and password, and a saved password is deleted when the Platform rejects it (Section 2.1 of the Privacy Policy). Otherwise until the Extension is uninstalled |
Extension IndexedDB |
(a) Non-exportable Chrome WebCrypto AES-GCM key that encrypts saved Platform logins; (b) the local order log (your order instructions and their statuses, and your copy groups), divided into daily segments; and (c) the random salt used to hash account identifiers in that log | No code can read the key’s bytes; the order log contains zero credentials or tokens, and account identifiers in it are hashed | Key and salt: until the Extension is uninstalled. Order log: history of completed orders is retained for 30 days and then automatically deleted; a day’s entries stay longer while an order from that day is still unfinished (Section 2.2 of the Privacy Policy) |
chrome.storage.session |
Platform logins signed in with “Don’t remember me” (encrypted in the same way), the username and password kept after you log out of such a login, and a marker that this browser session has started | Held strictly in volatile RAM; never written to disk | Wiped immediately when Google Chrome closes or Extension reloads |
4. Host-Site Storage Written to tradingview.com
Because the Extension operates inside TradingView chart pages, it writes the following items within the tradingview.com origin storage in your browser. Uninstalling the Extension does NOT automatically clear host-site storage; see Section 6.2 for manual purge steps.
| Host Origin & Mechanism | Stored Data Elements | Purpose |
|---|---|---|
tradingview.com (localStorage) |
Keys prefixed copyx.card. (copyx.card.*): the account and sign-in method last used on each card, and the panel tab last opened |
Preserves your CopyX panel state across page reloads; if these items are lost, the panel simply returns to its defaults |
5. Third-Party Sites and Analytics Posture
- Third-Party Domains: When you navigate to the Chrome Web Store, TradingView, any Platform, or a Prop Firm dashboard opened from a link in the Extension, those domains set their own cookies governed by their respective policies.
- No Analytics Without Prior Notice and Consent: CopyX currently deploys zero web analytics tools. If we introduce a web analytics tool in the future, we will update this Storage Policy at least 30 days in advance and, where required by law (including in the EEA, UK, and Switzerland), obtain your affirmative opt-in consent before setting or reading any non-essential storage.
6. How to Control and Purge Browser Storage
6.1 Uninstalling the Extension (Purges Section 3 Data)
Open chrome://extensions in Google Chrome, locate CopyX, and click Remove. This immediately destroys all data stored in chrome.storage.local, chrome.storage.session, and the Extension’s IndexedDB.
6.2 Clearing Host-Site Data on TradingView and copyx.trade (Purges Sections 2 & 4 Data)
To delete host-site localStorage and cookies remaining in your browser:
- In Google Chrome, navigate to Settings > Privacy and security > Site settings > View permissions and data stored across sites (or
chrome://settings/content/all). - Search for
tradingview.comandcopyx.trade, and click the Delete (trash) icon next to each domain. (Clearing a domain’s site data will also sign you out of that website.)
7. Contact Information
Questions regarding this Storage Policy may be directed to privacy@copyx.trade.