Privacy Policy

Last updated: 2026-04-18 · Plain English, not legalese

The principle

We collect data that helps the product. We never collect data that puts you at risk.

Concretely: your Kalshi credentials never touch our servers (we can't steal them, we can't subpoena them, we can't sell them). Your trade history and match queue ARE stored, because the dashboard is useless without them and we need them to calculate your referral commissions.

How your data helps improve the product

When your bot trades, it sends us the prediction it made (e.g. "model says 73% KKR wins at over 12") plus the outcome when the match ends. Aggregated across all users, that's how we know if the model is calibrated or drifting.

Three things we use aggregate data for:

· Catching model drift — if predictions stop matching outcomes, we retrain
· Fixing bugs — if 10 users hit the same error, we see it on our end, not just theirs
· Building the right features — if nobody uses a mode, we stop maintaining it

None of this links back to you personally. A row in our calibration table is just: (prediction %, actual outcome, match total, venue, model version). No user ID.

What we store on our servers

Your email + password hashRequired for login. Password is hashed with bcrypt — we cannot see the plaintext.
Subscription + billing statusManaged through Stripe. We get a Stripe customer ID — not your full card details.
Trade history your bot posts to our dashboardEach trade: ticker, contracts, price, edge, team, timestamp. Used for your dashboard view + referral commission calculation. No Kalshi credentials.
Your match queueWhat matches you've scheduled for the bot to trade. Synced every 60s from your laptop for dashboard display.
Referral relationshipsWho referred whom, so commissions work.

What we NEVER store or have access to

Your Kalshi API private keyLives only on your laptop, in your OS keychain (macOS Keychain, Windows Credential Manager, Linux keyring) or in a file with owner-only permissions.
Your Kalshi password or session cookiesWe don't ask for these. The bot uses API keys only.
Your credit card detailsStripe handles everything. We only get customer + subscription IDs.
Your browsing / app telemetryNo third-party analytics that identify individuals. No Google Analytics, no Facebook pixel, no session replay.

Architecture (nerdy but useful)

YOUR LAPTOP                    OUR SERVERS
-----------                    ------------
kalshi private key    ❌ NEVER  (not transmitted)
config defaults       ❌ NEVER
local trade log       mirror →  trades table (dashboard)
match queue           mirror →  match_queue (dashboard)
                                user account + billing
                                referral graph

KALSHI (third party)
--------------------
authoritative orders + positions
actual account balance

Your rights

Export: Email help@freshloop.ai and we'll send you all your data as JSON within 72 hours. (Self-service endpoint coming.)
Delete: Same email. We permanently delete your account, trade history, queue, and referral graph. Your Kalshi account is untouched (that's with Kalshi, not us).
Correct: Edit profile settings or email us if something's wrong.

Do we share your data?

No, except with Stripe (for payment processing) and Kalshi (which you authorize when you set up the bot). We do not sell, rent, or barter user data. If we were ever acquired, any new owner would be bound by this policy as of the date of acquisition.

Questions?

We'd rather you ask than guess. help@freshloop.ai