Privacy policy
The short version: we collect what the product needs to work — your account email, what you ask the copilot, first-party usage analytics — and nothing built for advertising. Your broker credentials never touch our servers, payment cards are handled by our payment processor, and you can have your data deleted by emailing us.
What we collect
- Account details — the email address and name you sign in with, via Google sign-in or an emailed one-time code. Sign-up is self-serve, and your email is what the account is keyed to.
- Product content — your watchlists, screens, alerts, chart setups, and research conversations with the copilot. Conversation content is sent to the large-language-model provider that generates the response; it isn't used to train models we control, and we don't sell it.
- Usage analytics — product events (pages, feature usage) collected with PostHog through our own first-party endpoint and stored in the EU. We run no third-party advertising trackers and no ad pixels. You can turn this off under Settings → Workspace behavior → Product analytics; it then stops in the app on every device you sign in on, along with the usage events our servers record for you.
- Error reports — when the app hits an unexpected error, a report goes to PostHog with details such as the error message and stack trace, the app version, your operating system and browser, and the page the error happened on. Errors in the app's interface — on the web, in the desktop window, or in the mobile app — are linked to your account like usage events. Errors on our servers, for example while running a research turn, a screen, or an order, are reported the same way, with the error and the feature it happened in (such as the symbol or order type). Errors from the desktop app's background process carry no account identifier, and file paths in them have your home folder removed. Turning product analytics off stops the interface reports; server and desktop background-process reports continue, because we need them to fix problems.
What we never see
- Broker credentials — broker connections (Interactive Brokers TWS, Futu/moomoo OpenD) run through the desktop app on your own machine. Logins stay local and orders execute locally; our servers never hold them.
- Card numbers — payments are processed by Stripe. We see subscription status, never your card details.
- Bring-your-own API keys — on the free plan, the LLM and market-data keys you supply are stored in your device's keychain and passed through per request to the provider you chose. Credentials you explicitly save in account settings are stored encrypted.
How it's used and shared
Data is used to operate and improve Arcanan: authenticating you, running the research and alerts you set up, sending transactional email (sign-in codes, account notices) through our email provider, understanding which features get used, and diagnosing errors. We share data only with the processors named above — LLM providers, Stripe, PostHog, and our email and hosting providers — each bound to processing it on our behalf. We do not sell personal data and we do not run advertising.
Retention and deletion
Account data is kept while your account is active. To delete your account and its data, or to ask what we hold about you, email support@arcanan.com from your account's address — deletion requests are honored, not argued with.
Changes and contact
If this policy changes materially, the change is announced on this page with an updated date. Questions about anything here: contact us. Last updated: October 1, 2026.
Start your next trade with evidence, not vibes.
The free plan runs on your own market-data and LLM keys — or on your broker's feed through the desktop app. No card, no invite.