Privacy Policy

Account Information

If you sign in with Google or Apple, we receive your email address, display name, and profile photo URL from your identity provider. We store this information in our database to create and identify your account, sync your predictions across devices, and optionally notify you about bug reports you submit. We do not access your contacts, calendar, files, or any other data from your Google or Apple account.

Prediction Activity

When you play the Higher/Lower prediction game, we save your guesses, prediction accuracy, and streaks. This data is linked to your account if you are signed in, or to an anonymous session identifier if you are not. We use this data to display your personal stats, leaderboard position, and prediction history.

Analytics

We use Google Analytics 4 (via Firebase) to understand how people use Bain Luck and to improve the product. This includes page views, scroll depth, engagement time, screen tracking, and prediction submission events. All analytics data is anonymous by default. We do not send any personally identifiable information (PII) to Google. Analytics data is used in aggregate to guide product decisions, not to build individual user profiles.

Device Information (Bug Reports Only)

When you initiate a bug report by shaking your device or using the keyboard shortcut, we collect your device model, operating system version, app version, network connection type, and the page you were viewing. A screenshot is also captured. This information is sent only when you explicitly trigger a bug report and is used solely to diagnose and fix issues. It is never collected in the background.

Push Notification Tokens

If you enable push notifications on iOS or macOS, we store your Apple Push Notification service (APNS) device token to send you notifications. You can disable push notifications at any time in your device Settings, which will stop all notifications from Bain Luck.

Category Preferences

You can select sport and topic interests to personalize your Discover feed. For signed-in users, these preferences are stored on our servers so they sync across devices. For anonymous users, preferences are stored locally in your browser (localStorage) and are not transmitted to our servers.

Services That Receive User Data

• Firebase Authentication (Google) — handles Google and Apple Sign-In. Receives authentication credentials during sign-in only.
• Google Analytics 4 / Firebase Analytics (Google) — receives anonymous usage events (page views, engagement time, interaction events). No PII is transmitted.
• Firebase Crashlytics (Google) — collects crash reports and diagnostics data from the iOS app to help us identify and fix stability issues. May include device model, OS version, and crash stack traces. User ID is attached only when signed in, to help diagnose account-specific issues.
• Sentry — collects error reports and performance data from the web application and API. Includes request metadata (URL, status code, timing) but no PII.
• Vercel — hosts the web application. Processes standard HTTP requests.
• Heroku (Salesforce) — hosts the API server and database.

Services We Read From (No User Data Sent)

• Kalshi — prediction market data. We read publicly available market prices. No user data is sent to Kalshi.
• Polymarket — prediction market data. We read publicly available market prices. No user data is sent to Polymarket.
• Pexels — stock photography for feed cards. No user data is sent to Pexels.
• OpenAI — generates market description text. No user data, personal information, or prediction activity is sent to OpenAI. Only market metadata (event names, odds) is processed.
• TMDB — movie and TV metadata. No user data is sent to TMDB.