Privacy and security

What we keep

• Your account. Your email address, and your password only as a scrypt hash with its own salt: we cannot read it, only check it. Your settings (edition, language, currency, theme, alerts), the people and stocks you follow, your portfolio and your alerts.
• If you sign in with Google. Google tells us your email address, that Google has verified it, and the number Google gives your Google account; we keep those two and nothing else from Google, not your name, photo or contacts. An account made with Google has no password at all. You can disconnect Google under Account → Security once the account has a password.
• Your sign-ins. For each browser signed in: a short label from the browser (for example “Chrome on Mac”) and the first part of its network address, never the full address. You see them under Account → Devices and can sign any of them out. An account is open on up to three devices; a new one is confirmed with a code sent to your email.
• How you use the site. The pages you open, what you search for, the columns and reports you read to the end, how many questions you ask the AI assistant (the kind, the model and the size, not the questions), and how many requests your account makes in an hour. It helps us see what readers find useful and stop misuse; only the site’s administrators see it, and it is kept 180 days.
• Traffic statistics. For every visitor, signed in or not: the pages opened and the links and buttons clicked in a visit, the site or campaign link that sent you there, your browser and operating system, the kind of device, the language your browser asks for, and your country, looked up from your network address on our own server with DB-IP’s free database (db-ip.com, CC BY 4.0). The address itself is not kept, only a scrambled form of it made with a code that is replaced every day. Only the site’s administrators see these statistics, and their own signed-in visits are not counted. They are kept 90 days; after that only daily totals remain, for two years.
• A cookie to recognise you. To recognise a returning visitor, the site sets a cookie of its own, hl_vid: a random code with nothing about you in it, which the page’s scripts cannot read and which lasts 400 days. It ties together the visits made in that browser, signed in or out; we keep only a scrambled form of it, and no one else receives it. A visit made while you are signed in, or in which you sign in or create an account, is linked to your account from its first page.
• Global Privacy Control. If your browser sends this signal, no cookie is set and you are not followed: a visit is counted once, by its first page, and each page our server sends is counted on its own, with no code that links them to each other or to your account; clicks and later screens in the app are not recorded.
• If you pay for a plan. The name, address, country, tax number and billing email printed on your invoices, the invoices themselves, and Stripe’s references for your subscription and receipts. Plans are paid by card through Stripe, or by bank transfer against our invoice.
• If you add your own AI key. It is encrypted on our server (AES-256-GCM), used only for your own questions and never shown again or written to logs; we keep its last few characters so you can recognise it. Keys for the data API are kept only as hashes.
• What you send us. Your messages from Help and feedback, and, when you cancel a plan or close your account, the reason you choose. The reason for closing an account is kept without your email.

What we never do

• No selling, no ads. We do not sell, rent or trade personal data, and there is no advertising on the site.
• No trackers. There are no analytics or advertising scripts from anyone else: the site runs only its own code, and it does not follow you to other sites.
• Not your card. Card details are typed into Stripe’s own pages and stay with Stripe; they never reach our server.

Who else handles it

Only the companies that run a part of the service, each for that part:

• Amazon Web Services. The servers and the database, in the United States (Ohio).
• Stripe. Card payments, receipts and card changes, under Stripe’s own privacy policy.
• Our email service. It delivers your sign-in codes, alerts, invoices and our answers.
• AI providers, when you ask the assistant. Your question, with the figures on the page, goes to Google Gemini (the site’s own assistant) or to the provider of your own key (Anthropic, Google or OpenAI), under their terms for API use.
• Google Fonts. Your browser downloads the site’s typefaces from Google, which sees your network address when it does.
• Google, when you sign in with it. Google confirms it is you under its own privacy policy; we ask it only for your email address.
• Backups. Encrypted copies of the database are kept off the server, on GitHub; they cannot be read without our key.

How it is protected

• Encrypted connections. The site is served only over HTTPS; plain HTTP is redirected, and browsers are told to use HTTPS every time.
• Sign-in. Sign-in tokens are random and kept only as hashes, in a cookie the page’s scripts cannot read; changes sent from any other site are refused. After a few wrong passwords or codes, further tries are refused for a while.
• Two-factor sign-in. Optional for every account and recommended: with an authenticator app on, a password alone cannot open your account. Administrators must use it.
• New devices. A browser the account has not used before needs a code sent to your email, and signing in on a fourth device signs out the one used longest ago.
• Signing in with Google. Each sign-in with Google is checked end to end: a one-time secret ties Google’s answer to the browser that asked, and the answer must be for this site, fresh, and for an email address Google has verified. Two-factor still asks for its code when it is on.
• Locked-down pages. A strict content security policy lets only the site’s own scripts run, and no other site can frame its pages.

Your choices

• Stop emails. Turn alerts off under Account, or use the unsubscribe link in any alert.
• Cancel a plan. Billing → Cancel the plan. It stays open until the end of the period you paid for, and nothing more is charged.
• Delete your account. Account → Delete my account removes your sign-in, settings, follows, portfolio, alerts, AI keys, billing details, messages to us, record of use and the traffic statistics recorded while you were signed in, all at once. Those recorded while you were signed out carry no account, so once it is gone nothing in them leads back to it, though the cookie still ties them to that browser; they are deleted 90 days after they were recorded. The site’s security log keeps its entries for the account (what was done and when) without your email. Invoices already issued are kept, as tax and accounting law requires.
• Ask. For a copy of what we hold about you, or anything on this page: Help and feedback, once signed in.