Privacy Policy
Effective November 20, 2026
This page explains what information StreetAI collects, how it is used and shared, which records are retained, and the choices available to you. We do not sell your personal information.
- Signing in with Google gives us your email address, name and profile picture. That is how an account exists.
- Preferences, game calls, assistant conversations and any investor profile you submit are stored for the features you use. Profile and advisory records have different retention requirements from ordinary account preferences.
- Service providers process information for hosting, sign-in, analytics, email and AI responses. We do not sell it, and there are no ad networks on the site.
- If you connect Alpaca or Robinhood, we store encrypted brokerage credentials and read account information to operate your strategies. Our software does not request withdrawals or transfers; review the permissions you grant at your broker.
- Letters have an unsubscribe link; profile visibility and account deletion requests are available in settings. Deletion does not erase records we retain for legal, regulatory, security or dispute purposes.
1. What we collect
- Your Google account
- When you sign in with Google we receive your email address, your name and your profile picture. We never receive or store your Google password. The email address is the key for everything below.
- Your preferences
- Your watchlist (the tickers you follow), the sectors you follow, your timezone if you set one so the letter reads in local time, whether the game recap rides in your email, and whether you are subscribed to the morning letter.
- The game
- Your player handle, each of your calls (ticker, direction, time placed), how each call graded against the market and against the AI analysts, your points and streaks, and whether your profile is public.
- Feedback
- If you use the feedback pill, we store the feedback text, the page you sent it from, your email if you were signed in (or the one you typed), and your browser's user-agent string.
- A connected brokerage account
- Only if you connect one. For Alpaca, we store the API key ID, and the secret encrypted with a key held in Google Cloud KMS. For Robinhood, you sign in at Robinhood, and we store the sign-in tokens Robinhood issues, encrypted using Google Cloud KMS, never your Robinhood password. Only our own servers decrypt them: the worker that runs your strategy, to trade, and the website, to read your Alpaca account's balance for your portfolio page and to renew your Robinhood sign-in. We store the account number, whether it is a paper or live account, the nickname you gave it, and the state you provide. We read the account's balance, buying power, positions and open orders when connecting and while a strategy runs, and retain orders, execution events and account observations. We keep which strategy you started, when it started, paused and stopped, the loss limits you set, and equity history. StreetAI uses Alpaca credentials for account reads and strategy orders; our software does not request withdrawals or transfers. StreetAI uses the Robinhood sign-in for account reads and strategy orders; our software does not request withdrawals or transfers. Broker permissions determine credential capabilities, and you can review or revoke access at the broker.
- Your investor profile and advisory records
- If you complete an investor profile, we collect your age band, state, investment objectives, experience, risk tolerance, time horizon, liquidity needs, income, expenses, assets, debt, emergency reserves, loss capacity, intended allocation, tax context, restrictions and any additional information you submit. We retain profile versions, strategy eligibility assessments, the policy used for each assessment, document versions and delivery receipts, agreement acceptances, check-ins and related support records. Risk acknowledgements have a separate acceptance history, including the version and date of the terms, time of acceptance, paper or live scope, IP address and browser user-agent. Completing a form does not itself establish that an advisory service is available or that a strategy is appropriate.
- Ducky conversations and AI strategy search
- For Ducky, we store messages, replies, preferences and proposed or confirmed actions to continue your conversation. Your messages and relevant service context, such as strategies, account status, balances, holdings and trading activity, may be sent to the AI model provider that generates the reply. AI strategy search sends your query and descriptive catalog context to the model provider. Saved investor-profile answers are not included in AI chat or search context. Information you type into a chat is itself part of the conversation, so do not enter brokerage credentials, passwords or sensitive financial profile answers there; use the designated account and profile forms.
- Subscription records
- The beta is free. If you later affirmatively subscribe to a paid service, payment processing may use Stripe, and we will keep subscription consent, billing status and transaction references. The provider handles payment details under the checkout terms and its own privacy policy.
- Member referrals
- If you use an invite, we keep the invite code, account identifiers, email address, signup date, first subscription payment status and any credits awarded. We use these records to administer the reward and keep a record of the disclosure you received.
- How you found us
- The first page you landed on, any campaign tags in its address (utm_source, utm_medium, utm_campaign), the referring site's hostname and when you arrived. This note is kept in your browser; we attach it to your account once, when you first sign in, and also when you subscribe to the letter or save a watchlist.
- Visit counts
- Only if you accept analytics cookies in the cookie banner: when you first visit after accepting, and once a day after that, your browser sends us that note and we add one to a daily tally by source, campaign, referring site and landing page. The tallies are counts only: we store no IP address, no user-agent and no identifier for your browser or device, and a tally cannot be linked to you or to your account. When you first sign in, your account also notes a yes/no of whether your browser's visit was counted, so we compare signups with the visitors we counted; it says nothing about which tally or when.
- Account setup
- Which steps of the setup screens you reached after signing up, and whether you completed or skipped each one, so we can see where setup gets in the way.
- Usage analytics
- We use Google Analytics to understand which pages get read: pages viewed, clicks on a few named controls, device type and approximate region. Its cookies are off until you allow them in the cookie banner; without cookies, it still receives page and consent signals. See Cookies.
- Server logs
- Like every website, our servers keep server logs of requests — the address requested, the time, your IP address and browser user-agent. Your IP address is also used for short-lived rate limiting on the feedback form.
2. How we use it
- To run your account: sign you in, keep a session, show your watchlist and settings across devices.
- To send you the morning letter, if you subscribed, and to personalise it with the names you follow.
- To run the game: grade your calls, keep your record, and — if your profile is public — show your handle and record on the board and on share pages.
- To keep a public track record: the AI analysts' calls are logged and graded in public; your game calls are logged so your record is reproducible.
- To run a strategy you started: check that a key works before saving it, read the account so the strategy can size and manage its positions, place and close its orders at your broker, apply the loss limits you set, and email you when the account was connected, when something will limit it, and when a strategy halts.
- To assess service availability and strategy eligibility using your profile, account permissions and the applicable reviewed policy, and to record disclosures, consent and ongoing reviews.
- To answer Ducky and strategy-search requests, display account updates, present proposed changes and carry out actions you confirm through the service controls.
- To maintain records, handle disputes, investigate security incidents and meet applicable legal and regulatory obligations.
- To understand how the site is used and to fix it when it breaks.
- To answer you when you write to us.
Automated assessments can affect which strategies you may use, and a strategy you authorize can make securities decisions in your account. Contact support if your information is wrong or you need an assessment explained. We do not sell your information or use it for cross-context behavioural advertising.
3. Who processes it
We run on third-party infrastructure. These companies process data on our behalf under their own terms and security commitments:
- Google Cloud — hosting, server logs, and the databases behind the site. Firebase Authentication handles Google sign-in; Firestore stores account, brokerage, investor-profile, assessment, document, consent and service records. Redis stores operational state and assistant conversations.
- Google Analytics — usage analytics (see Cookies).
- Resend — delivery of the morning letter and of account emails, which means Resend receives your email address and the content of each letter sent to you.
- BigQuery (Google Cloud) — the analytical store for game records and the AI analysts' rating logs, which is how the public track record is computed.
- Alpaca (Alpaca Securities LLC) and Robinhood — your broker, if you connect an account. Your broker receives every request our software makes with your trading key or sign-in token: reads of your balance and positions, and the orders a strategy places. Your relationship with your broker is under their own agreement and privacy policy; we are a third party using the trading key or sign-in you gave us.
- Google Cloud KMS — holds the encryption key for brokerage secrets. Decryption happens only on our own servers: the worker that runs strategies, and the website, which reads your Alpaca balance and renews your Robinhood sign-in.
- AI model providers — Ducky uses Google Gemini to generate replies from the conversation and limited service context described above. Our public research also uses models from providers including Google, Anthropic, OpenAI and Meta, with some requests routed through model infrastructure providers. Public research inputs and member chat context serve different purposes; saved investor-profile answers are excluded from member chat context.
- Stripe — subscription and payment processing if you affirmatively enroll in a future paid service. Beta registration and connecting a broker do not authorize billing.
4. How long we keep it
- Account data (your Google profile fields, preferences, watchlist, subscriptions) — while needed to operate your account, then removed or de-identified through the deletion process, subject to the retained records described below.
- Sessions — a sign-in session lasts 30 days and is renewed each time you use the site, so it ends 30 days after your last visit; signing out deletes it immediately.
- Game records and rating logs — kept for the life of the public track record, because a record that can be quietly edited is not a record. When an account is deleted, your handle is removed from public surfaces; graded call rows may be kept in de-identified form so historical leaderboards still add up.
- Feedback and support — while needed to resolve the issue and preserve the service, security or dispute record.
- Brokerage credentials and history — active credentials are removed from the connection record when disconnect completes. Disconnection requests a stop first; open positions may remain. Account identifiers and strategy history can remain as records of what our software did in your account. Revoke authorization at the broker to control further access.
- Investor profiles, assessments, documents and consent — including risk-acknowledgement history, retained separately from ordinary account data for legal, regulatory, service and dispute purposes, including after an account deletion request. The ordinary deletion process does not erase these records. Retention periods depend on the record, applicable requirements and any legal hold.
- Ducky conversations — the recent-history store has a 30-day expiration from its last save. Related action, support and compliance records can be retained longer, including under a legal hold; model providers' processing and retention are governed by the applicable service arrangements.
- Server logs and analytics — on our providers' standard retention schedules.
5. Sharing
We never sell your personal information, and we do not share it with anyone for their own marketing. We share it only:
- with the processors listed above, to run the Service;
- with your broker, if you connect an account: the reads and orders described above go to Alpaca or Robinhood under your key or sign-in. Relevant brokerage context can also be processed by our infrastructure and the AI provider for member chat as described above;
- publicly, only the parts you have chosen to make public: your handle and game record appear on the public board and on share pages only while your profile is set to public. Your email address is never shown publicly;
- if the law requires it, or to protect the rights, safety or property of StreetAI, its readers or others;
- with a successor if StreetAI is ever acquired or reorganised, under this same policy.
If you join through a member’s invite link, that member may earn membership credit when you first pay. We show the member only the credit they earn. We keep your identity, signup and payment status private in the referral program. If you are the only person they invited, they may be able to tell from their credit that you subscribed.
6. Your choices
- Email. There is an unsubscribe link in every letter we send, and a morning-letter switch on your settings page. Either one stops the letter.
- Profile visibility. A switch on your settings page makes your handle and record private, which removes you from the public board and share pages.
- Watchlist and preferences. Edit or clear them on your settings page at any time.
- Brokerage accounts. Disconnect an account from your portfolio or your settings page; the process requests a strategy stop and removes stored credentials from the active connection. You can also revoke our access at your broker (the key at Alpaca, the sign-in at Robinhood). Check your broker for remaining orders and positions: revoking access does not itself close them.
- Deletion. Press "Request deletion" on your settings page or email support@street.ai. We process the request after account wind-down and the deletion waiting period, with support review where needed, and notify you when it is completed. Some records remain for the purposes described under retention; backups and provider copies may take additional time to expire.
- Access and correction. Email support@street.ai and we will tell you what we hold about you and fix anything that is wrong.
7. Cookies and local storage
- Session cookie. Signing in sets one cookie that identifies your session. It is needed for the account to work.
- Google Analytics cookies. These are off until you allow them. The cookie banner asks once; "Allow" lets Google Analytics set its own cookies to tell returning visits apart, "No thanks" keeps them off, and either way the site works the same. Without cookies, Google Analytics still receives cookieless page and consent signals under its Consent Mode. Your answer is remembered in your browser's local storage; to change it, Reset cookie choice and the banner asks again. Blocking the cookies in your browser also works.
- Invite cookie. Opening an invite link sets a cookie holding the invite code for up to 30 days, so the invite can be credited when you sign in; it is deleted at sign-in.
- Local storage. Your cookie choice, dismissed banners, display preferences, the how-you-found-us note and the date of your last visit (so a day's visit is counted once) live in your browser's local storage. The note is attached to your account as described above; the rest stay on your device.
There are no ad networks or advertising cookies on StreetAI. Information is still shared with the service providers described above to operate and measure the Service.
8. Children
StreetAI is not for anyone under 18. We do not knowingly collect personal information from anyone under 18; if you believe we have, email support@street.ai so we can investigate and address it, including deletion where appropriate.
9. California privacy rights
If you live in California, you may have rights under the California Consumer Privacy Act (CCPA, as amended), depending on its applicability and exemptions, to know how information is used, access or correct it, request deletion, and exercise those rights without discrimination. We do not sell or share personal information for cross-context behavioural advertising. Use settings or email support@street.ai to make a request. We verify requests and apply any legally required retention or other exceptions; this policy does not limit rights available under applicable privacy law.
10. Where your data lives
StreetAI is operated from the United States and hosted on Google Cloud in the United States. The Service is for US residents; if you use it from elsewhere, your data will be transferred to and processed in the United States, where privacy law may differ from your own country's.
11. Security
Sign-in is delegated to Google, so we do not receive your Google password. We use encryption in transit, KMS encryption for brokerage credentials, and access controls for stored data. No system is perfectly secure. We investigate security incidents and provide notices required by applicable law.
12. Changes
We will update this policy as the Service changes. The effective date at the top tells you which version you are reading; for a material change we will post a notice on the site or email subscribers before it takes effect.
13. Contact
The Service is operated by Hey AI, Inc., doing business as StreetAI · 430 Montague Expy, Milpitas, CA 95035 · support@street.ai — or reply to any morning letter.
Terms of Service → · How StreetAI works → · ← Back to StreetAI