What MarketMind is
MarketMind is a portfolio-side project that lets users place virtual-credit predictions on a fixed universe of 50 US stocks. There is no real money involved, no advertising, no commerce, and no third-party tracking beyond what is documented on this page. Source code is public at github.com/neelesh1206/market-mind. You can audit every line of code that touches your data.
What Google shares with MarketMind when you sign in
When you click “Sign in with Google,” Google shares:
- Your email address
- Your display name
- Your profile picture URL — displayed as your avatar in the app header dropdown and on your profile page. The image itself stays on Google's CDN; we don't copy it, proxy it, or store it. If the URL expires or you revoke OAuth access, the avatar falls back to a single-letter chip.
- An anonymous Google user ID we use to recognize you on return visits
That is the entire list. We do not request, and Google does not share:
- Anything from Gmail, Drive, Calendar, Contacts, Photos, or any other Google service
- Permission to post, send, or modify anything on your behalf
- Your phone number, physical address, date of birth, or any sensitive personal data
The OAuth scopes we request are openid, email, and profile — non-sensitive scopes for sign-in only.
Purpose of use
The Google user data listed above is used solely to identify your MarketMind account across visits and to personalize the in-app header (your display name and avatar). Specifically:
- Email — used as your unique account identifier and to contact you if you request a data deletion. Not used for marketing, newsletters, or any other outbound communication.
- Display name— shown in the header greeting (“Welcome back, <name>”) and on the public leaderboard if you opt in.
- Profile picture URL — rendered as your avatar in the header dropdown and on your profile page. Read on each render, never stored.
- Google user ID — internal foreign key tying your sign-in token to your account row. Never displayed to other users.
Google user data is not used for advertising, sold to third parties, shared with data brokers, or used to train AI/ML models.
What MarketMind stores about you
- The email, display name, and Google user ID from the previous section
- The 50-stock watchlist you build during onboarding
- Each daily prediction you place (stock, direction, stake) and its resolved outcome
- Your virtual-credit balance and the ledger of credit transactions
- Daily-login streak counters and any badges you have earned
- Thumbs-up/thumbs-down feedback you leave on MarketMind's own daily verdicts
All of this data lives in Supabase Postgres (US-East region), with row-level security policies enforced at the database — meaning only your own account session can read your bets, balance, and feedback. Even a bug in our server code cannot return another user's data; the database itself refuses.
What we deliberately don't store:your Google profile picture URL. It travels with your sign-in token and is read on every page render to display the avatar — never copied into our database. When you sign out (or revoke OAuth access via your Google account), it's gone from our side immediately with no cleanup required.
Vendors that touch your data
We use a small number of standard infrastructure vendors. Each one's role is listed below.
- Supabase — primary database, authentication, and row-level-security enforcement. Stores everything in the previous section.
- Vercel — web hosting. Serves the pages and the OG share images. Sees standard HTTP request logs (URL, user agent, IP). Does not see the contents of database queries.
- Cloudflare — DNS for the custom domain and scheduled triggers for the nightly pipeline. Does not see your account data.
- Upstash — short-lived cache (rate-limit counters and a 5-minute live-price cache). Sees keys like
mm:rl:placeBet:<your-uuid>but not the content of your predictions. - Vercel Analytics — anonymous pageview + Core Web Vitals tracking. First-party, no cookies, no cross-site tracking. We see counts and routes, never individuals.
We do not use Google Analytics, Facebook Pixel, advertising trackers, third-party session replay, or any data broker.
Data we do not collect
- Real financial information — there is no money flow in this app
- Payment details, bank info, or any commercial data
- Location data beyond the IP-derived approximation in standard HTTP logs
- Biometric, health, or sensitive personal data
- Browsing history outside MarketMind
How to revoke access
You can disconnect MarketMind from your Google account at any time:
- Open myaccount.google.com/permissions
- Find “MarketMind” in the list of connected apps
- Click “Remove access”
That stops the OAuth connection effective immediately. Google will no longer share new sign-in tokens with us.
Data retention
We retain your Google sign-in identity (email, display name, Google user ID) and your MarketMind game state (watchlist, predictions, credit balance, badges, feedback) for as long as your account exists. We do not have a fixed expiry — the data is what makes the app work for you on return visits.
When you request deletion (see next section), every row tied to your account is removed from Supabase within 24 hours. Vercel and Cloudflare HTTP request logs roll off on their standard vendor schedules (~30 days). Upstash cache entries auto-expire within minutes.
Your Google profile picture URL is never stored, so no retention applies — it disappears from our side the moment you sign out or revoke OAuth access.
How to delete your stored data
Revoking OAuth access stops new data from flowing in, but does not delete what we already have. To permanently wipe your account, predictions, watchlist, and credit history, email neelesh1206@gmail.com with the email address tied to your MarketMind account. We will confirm deletion within 24 hours.
Changes to this policy
If we materially change how data is collected or shared, the Last updated date at the top of this page changes, and the same commit appears in the public git history at github.com/neelesh1206/market-mind. You can subscribe to the repo to be notified.
Contact
Anything unclear, or want to verify a specific claim against the source? neelesh1206@gmail.com.