Privacy Policy
Effective: 2026-10-24
Chinese reference translation (non-binding): 中文参考译文 · Previous version: 2026-09-19 (Chinese text)
Scope and controller
This policy covers the hosts catalystdesk.ai, watchlist.catalystdesk.ai, subscribers.catalystdesk.ai and unsubscribe.catalystdesk.ai, and the brief e-mails we send. Data controller: BANFF MANAGEMENT DATA ANALYSIS LIMITED (班夫管理數據分析有限公司), Flat/Rm 1911, Lee Garden One, 33 Hysan Avenue, Causeway Bay, Hong Kong.
What we collect
We process email addresses for subscriptions and sign-in, access and consent records, and the security information needed to protect those functions. The proposal form collects a contact email and a short workflow description; name, service, scope tier, target users, product stage, available inputs, budget and timing are optional. Submitted briefs are stored in an access-controlled inquiry inbox. Submitting an inquiry also writes a security audit record with the email, time, action and request IP (see Security logs below), and the inquiry record keeps an unsalted hash of the request IP; the brief itself is not included in analytics or notification messages. Where product features are enabled, we also process the wallet, usage, receipt and payment-reference information needed for those specific functions. Do not submit private keys, credentials, trading secrets or personal financial information. Card details are handled by the payment provider, not by the inquiry form. A confirmed subscription creates one statistics row with no e-mail address or IP for aggregate measurement. Product checkout records can include the cd_src held when you started the checkout, alongside provider references and purchase status; this is separate from a service inquiry. If you buy Desk Alpha – Personal, you enter your card details on the payment provider's checkout page and we never see card numbers; the payment provider and Link receive what they need to process the transaction, and we keep only the subscription's status, its billing periods, the amounts paid or refunded and the provider's reference identifiers, linked to your e-mail address; of the notifications the payment provider sends us we keep only their identifier and type, and we do not store your name, billing address, phone number or card details. If you use the on-chain unlock, we keep the public wallet address you link yourself and the result of the one-time signature check, and read that address's public approval and fill facts on the decentralised exchange; if you arrived from a community's alert card and then unlock, we keep that community's identifier on the address's unlock record so the community owner's share of the builder fee can be settled; to decide whether the optional on-chain channel may be offered to you we read the country the network edge reports for your request (derived from your IP), use it for that decision only and do not otherwise store it. If you interact with the messenger bot, we keep your messenger user id, language and the community you came from. If you bind a community as its owner, we also keep the group id and title, the referral code or payout address you supply, and the rebate ledger held against that community. We never touch a private key or seed phrase and store no card number.
How we use it
We use account information to provide the requested product, protect access and respond to support or privacy requests. Inquiry information is used to assess fit, follow up and agree scope; it does not automatically enroll you in marketing emails or authorize payment. We do not sell personal information or use customer briefs, strategies, code or identifiable results for model training or cross-client reuse without written permission.
E-mail metrics
Brief e-mails carry no open- or click-tracking pixels; the upgrade link carries a source token with nothing personal in it (the same for every recipient of the issue), see cd_src below; a click on the unsubscribe link is recorded so that sending stops immediately.
Cookies
This site uses first-party cookies only and sets no third-party or advertising cookies; there is no third-party tracking through them. Sign-in: cd_desk_session keeps you signed in to the desk (12 hours by default) and cd_watch_session to the Live Watchlist (one day by default). Inquiry form: cd_contact holds a per-visitor nonce that the single-use form token is bound to, to prevent cross-site and duplicate submissions (1 hour). Language: cd_lang remembers a language you chose on this site or the desk, and cd_email_lang the language you chose on the subscription pages (1 year each). Two first-party measurement cookies: cd_exp keeps the version of a page you were shown the same on your next visit so page wordings can be compared in aggregate (90 days); cd_src remembers the non-personal campaign source or page that brought you to the site (7 days), and if you then start a checkout that source token is stored with the checkout on your subscription record so conversions can be counted by source. Optional acquisition analytics, only where it is enabled (its notice and preferences explain the consent controls): cd_growth_consent records your analytics choice (30 days); __Host-cd_growth holds a signed attribution token (up to 30 days); __Host-cd_growth_csrf protects the preferences form (10 minutes); __Host-cd_growth_pending carries an attribution hand-off between our hosts (5 minutes). None of these cookies contains a brief, e-mail address or account credentials.
Security logs
Rate-limit and access-audit entries (IP, time, action, the e-mail address concerned) are kept for 90 days to prevent abuse and diagnose faults, never for profiling.
Retention and deletion
Network traffic and access logs are kept for 90 days on a rolling basis; sign-in codes and session tokens themselves, with their validation state, for 30 days (the access-audit entry that one was issued or used follows the 90-day rolling rule above); financial, tax and subscription payment records for 7 years as required by accounting law. After unsubscribing, the address stays on a suppression list so we never send again; write to us to delete the other account records, except the minimum the suppression list and statutory retention require. Inquiry records are held for follow-up and scope discussions, with access restricted to authorized staff. You may request correction or deletion through the contact channel below, subject to applicable recordkeeping obligations. Inquiry records that do not lead to an engagement are deleted no later than two years after our last exchange; records of an engagement follow its SOW and statutory retention.
Service providers and security
Website hosting, email delivery and configured payment providers process the information necessary for their respective functions. Desk Alpha – Personal payments are processed by the payment provider, with Link as the seller of record. A service inquiry is accepted when it is saved in the authorized inbox; email notification delivery is separate. Any additional data, model or cloud provider for a professional engagement, its access and its spending cap are agreed before work starts. Access controls protect the inbox. Do not send confidential materials through the initial public brief.
Your rights
You may write at any time to access, correct or delete the records we hold about you, or unsubscribe at any time; we answer within a reasonable period.
Contact
Send privacy requests to alerts@catalystdesk.ai. Desk Alpha – Personal subscription, billing and refund questions: hello@catalystdesk.ai. Postal address of the data controller: see Scope and controller above.