Privacy, in plain language.

• Account and session data. Your email address is used by Supabase Auth for passwordless sign-in. Essential Supabase session and PKCE cookies keep the sign-in flow secure and the browser signed in.
• Alerts. oddsUp stores the market, outcome, crossing direction, threshold, status, observation baseline, and timestamps needed to evaluate and manage your alerts.
• Telegram connection data. If you connect Telegram, oddsUp stores the Telegram user ID, chat ID, username when supplied by Telegram, and connection time. Connection links use a hashed, single-use token that expires after ten minutes.
• Radar data. The database can store Radar follows and delivery events. Radar is currently marked Coming Soon and public Radar configuration is disabled.
• Market data. Public HIP-4 metadata, prices, and sampled probability history come from Hyperliquid. This market history is not linked to a user account.
• Operational data. Hosting and worker logs may contain request metadata, timestamps, and errors needed to operate and troubleshoot the service.

oddsUp processes this information to authenticate users, display saved alerts, evaluate probability crossings, connect or disconnect Telegram, deliver requested notifications, prevent duplicate delivery, enforce rate limits, and investigate service failures.

oddsUp does not use advertising SDKs, cross-site tracking pixels, or product-analytics SDKs. Infrastructure providers may still process ordinary request and security logs under their own terms.

• Supabase provides authentication and the database.
• Resend delivers passwordless sign-in email configured through Supabase Auth.
• Vercel hosts the web application.
• Railway runs the market-monitoring worker.
• Telegram processes the chat identifier and alert message needed to deliver notifications you request.
• Hyperliquid supplies public market information. oddsUp does not send it your oddsUp account profile to read that data.

Account, profile, alert, and subscription records remain until they are removed or the associated account is deleted. You can delete individual alerts, and disconnecting Telegram clears its identity fields from your profile.

Telegram connection links expire after ten minutes. Public market-probability samples are configured for roughly 48 hours. If Radar delivery launches, its delivery events are configured for a 30-day cleanup window. Infrastructure providers may retain operational logs under their own policies and settings.

There is no in-product account-deletion button. Account or data deletion requires an operator request; deleting the authentication account is designed to remove its related profile, alerts, delivery claims, and Radar records.

You may delete alerts from Alerts, disconnect Telegram from Settings, and sign out to clear the local oddsUp session.

For privacy questions or an account/data deletion request, contact @whizzkee on X. Do not include passwords, magic links, or other credentials in your message.

oddsUp uses authenticated sessions, row-level database policies, and caller-scoped operations to limit access to user-owned records. No online service can promise absolute security or uninterrupted availability.

This page should be updated when the data handled by oddsUp, its providers, or its retention practices materially change.