Privacy Policy

Account information

When you create an account with email and password, we store your email address, an optional display name, a bcrypt password hash (cost factor 12 — your actual password is never stored), and the date the account was created. If you sign in with Google instead, we store the same record shape (email and name from your Google account) with no password hash. We do not collect phone number, physical address, or date of birth.

Billing information

If you subscribe to Prop Wizard Pro, you enter your payment details directly on Stripe's own hosted Checkout and Billing Portal pages — Prop Wizard's servers never see or store your card number, CVV, or billing address. What we do store, tied to your Stripe customer ID, is: your Stripe customer ID, email, subscription ID, subscription status, the price plan you're on, your current billing-period end date, and whether your subscription is set to cancel at period end. We do not store your card brand or last four digits — Stripe holds that.

Biometric data (Face ID / Touch ID)

If you enable biometric app-resume on iOS, the on-device biometric check (Face ID or Touch ID) runs entirely on your device through Apple's own biometric APIs. Prop Wizard never receives, transmits, or stores any biometric data, template, or scan — the result is used purely as a local yes/no gate before resuming your existing session on that device. The only thing sent to our servers around sign-in is a coarse device-type label ("iOS App," "Android App," or "Web"), never anything biometric.

Session and device data

On the iOS app, your refresh token and a cached copy of your profile are stored in Apple's Keychain via secure on-device storage — not in plain app storage. Your short-lived access token (valid 15 minutes) is kept only in memory on your device and is never written to disk. On our servers, we keep a session record containing your user ID, email, a session ID, a one-way hash of your refresh token's secret (never the raw secret itself), the same coarse device-type label described above, and timestamps for when the session was created, last used, and expires. We do not collect device fingerprints, IP addresses, or OS version as part of this record. Server-side sessions expire after 60 days of inactivity.

Community features

Community Picks(aggregate "most-picked player" counts) stores only the prop subject, the prop type, the line, a running count, and a last-updated timestamp — no user identity is stored or shown with these counts.

Community Chatis different: each message you post stores your account ID, your display name, your message text, and a timestamp, and is visible to any signed-in user. If you have not set a display name on your account, the chat shows your email address in its place. If you don't want your email visible to other users in Community Chat, set a display name in Settings before posting, or avoid using that feature.

• To create and maintain your account and let you sign in on web and iOS.
• To gate app-resume behind biometric confirmation on your own device — this use is entirely local and never leaves your device.
• To process your Pro subscription — starting a trial, billing, renewals, and cancellation — through Stripe.
• To keep you signed in across sessions and devices via session/refresh tokens.
• To display community features (aggregate pick counts, and chat messages with your name/email as described above) to other signed-in users.

Stripe — processes your subscription payment. Stripe receives whatever you enter directly on its own hosted Checkout and Billing Portal pages (email, payment method, billing address); this is not proxied through our servers, and we never see your raw card data.

ParlayAPI — this is a market-data source, not a data-sharing relationship. Our servers make scheduled, outbound-only calls to pull sports betting odds; no user data of any kind is sent to ParlayAPI, and page loads on the site never call it directly.

MLB Stats API and ESPN — outbound-only public sports data (schedules, lineups, scores, injuries) pulled server-side with sport/game parameters only. No user-identifying data is sent to either.

Google— if you choose "Sign in with Google," standard OAuth sign-in data is exchanged with Google to authenticate you.

Analytics and tracking — none are active.Prop Wizard does not run Google Analytics, Mixpanel, Segment, Sentry, PostHog, Amplitude, Facebook Pixel, or any comparable analytics/tracking tool in production, and the live site and iOS app load no third-party tracking scripts. (One analytics package exists in our dependency list but is only wired into an internal, unused reference project that is never built or served to real users — we're noting it here for completeness, not because it collects anything from you.)

We use a small number of first-party cookies, all set by our own servers — no third-party ad or tracking cookies.

All of these cookies are set with httpOnly, secure (in production), and sameSite=lax, so they can't be read by page scripts and aren't sent cross-site. The iOS app does not use cookies — it uses the on-device secure token storage described in Section 1.

• Account records are kept for as long as your account exists.
• Billing records are kept for as long as you have (or had) a subscription, so we can honor renewals, cancellations, and support requests.
• Server-side mobile sessions expire automatically after 60 days of inactivity.
• Cookie lifetimes are listed in the table above (30 days for your login session, up to 400 days for the Stripe-customer link cookie).
• Community Chat messages persist until deleted — you can delete your own messages at any time from the chat itself.

You can delete your own profile picture and your own individual Community Chat messages directly in the app at any time. For everything else — deleting your account, your stored account/billing records, or your session data entirely — email us at privacy@propwizard.it.com from the email address on your account and we will delete your data. We do not currently offer an automated, self-serve "delete my account" button in the app — we handle deletion requests manually to make sure the right account is removed.

• Passwords are hashed with bcrypt (cost factor 12) — we never store or can recover your raw password.
• Refresh token secrets are stored server-side only as a one-way SHA-256 hash, never in raw form.
• On iOS, your refresh token and cached profile live in the device Keychain via secure on-device storage; your access token is kept in memory only and cleared when the app closes.
• Session cookies are httpOnly and marked secure in production, so they aren't exposed to page scripts or sent over plain HTTP.
• Card data is handled entirely by Stripe on Stripe's own infrastructure — it never touches our servers.

Prop Wizard is not directed at children, and we do not knowingly collect personal information from anyone under 18. If you believe a child has provided us with personal information, email us at privacy@propwizard.it.com and we will delete it.

If we change what data we collect or how we use it, we'll update this page and change the "Last updated" date above. Material changes affecting active subscribers will be communicated by email where practical.

Questions about this policy or how your data is handled? Email privacy@propwizard.it.com.