After Bell Investing

Legal

Privacy policy

How After Bell Investing collects, uses, and shares information when you use the website and related apps.

Information we collect

  • Account: email and profile data from Google sign-in (or local/dev auth where enabled).
  • Billing: Stripe customer and subscription identifiers; card numbers stay with Stripe.
  • Optional security: phone number for SMS MFA (encrypted at rest; logs may show a masked number).
  • Optional tools: sealed LLM API keys you paste for personal book checks; IBKR gateway session cookies you connect (never your IBKR password).
  • Usage: pages viewed, a long-lived visitor cookie (ab_vid), and basic server logs.
  • Content you submit: feedback, desk notes (staff), and similar inputs.

How we use it

To operate the research desk, authenticate you, bill memberships, send digests or notes you opt into, provide optional MFA and broker assist, improve reliability, prevent abuse, and meet legal duties.

Processors

Depending on configuration we use service providers such as Google (sign-in), Stripe (payments), Twilio (SMS MFA), cloud hosting (for example AWS), and model providers when staff or you enable LLM features. They process data under their terms to provide those services.

Cookies

  • session — signed login session (HttpOnly; Secure on HTTPS).
  • ab_vid — anonymous visitor id for traffic analytics on this server.

We do not sell personal information. Brokerage ads are labeled when shown.

Retention

Account and billing records last while the account is active and as needed for tax, fraud, and legal holds. You may close the account by contacting staff; residual backups may persist for a limited period.

Your choices

Update email preferences on the subscription page. Manage or cancel billing in the Stripe portal. Disable MFA or disconnect IBKR when you no longer want those features. Residents of some U.S. states may request access or deletion of personal information we hold — email the staff address on your account for requests. If you are in the EEA/UK, contact us before relying on the service; we do not currently operate as an EU-established controller for a local offering.

Security

We use encryption in transit (HTTPS in production), sealed secrets for sensitive fields, and access controls for staff tools. No method of transmission or storage is perfectly secure.

Related: Terms of use · Disclaimer. This page is a privacy notice, not legal advice.