Privacy Policy

FakeBet (the "Service", accessible at https://fakebet.fun) is a free sports betting simulator. No real money is wagered, no real money is paid out, and no real betting takes place. The Service exists for entertainment and education. This Privacy Policy explains what data we process when you use the Service and what rights you have over that data.

The Service is operated by an independent maintainer based in the European Union. We deliberately do not publish a personal identity or contact email so the project can keep its hobby/portfolio character. You can reach us at any time via the in-app feedback widget (the bug icon in the bottom-left corner of the home page), which is the canonical privacy contact channel for the purposes of GDPR Article 13(1)(b).

• Account data. Email address (email signup) or Google profile data (Google sign-in: email, display name, profile picture URL) — only what Google shares with the app. A unique user ID issued by our auth provider (Supabase).
• Profile. The username you pick (3–20 lowercase characters, public on the leaderboard if you bet in ranked mode), and your two virtual balances (ranked $1,000, casual $10,000 starters).
• Betting history. Virtual bets you place — event, market, stake, odds, outcome, and whether the bet was placed in ranked or casual mode. None of this represents real money.
• Technical data. IP address, user-agent, and request logs handled by our hosting provider (Vercel) and our auth provider (Supabase) for security, abuse prevention, and routine operation. Retained briefly per their respective policies.
• Cookies. Strictly essential authentication cookies set by Supabase Auth (chunked sb-...-auth-token) and a small number of functional flags in localStorage (e.g. your preferred mode, dismissed banners). No advertising or cross-site tracking cookies.

• Authenticate you and keep you signed in.
• Show your bet history, your stats, your achievements, and (if you opt into ranked mode) your standing on the public leaderboard. Only your username is visible to other users; email, profile picture, and balances are never published.
• Operate the Service — settle bets when sport scores come in, credit balances, refund stale pending bets, send Realtime updates to your own session.
• Investigate abuse, security incidents, and bug reports you submit via the feedback widget.

Legal basis under GDPR Article 6: performance of contract (running the account) and legitimate interest (security, abuse prevention, service improvement).

We do not sell your data and we do not share it with advertisers. The Service is built on a small number of sub-processors who handle data on our behalf under their own terms:

• Supabase (auth + database hosting) — stores your account, profile, and bet history. Supabase privacy policy.
• Vercel (web hosting) — handles request logs, CDN, and edge functions. Vercel privacy policy.
• Google (only if you sign in with Google) — performs the OAuth handshake and shares your email + display name with us. No data flows back to Google beyond the standard OAuth callback.
• The Odds API — provides sports schedules + odds. We send no user-identifying data to them; they only see our server's API key.
• Web3Forms — receives messages you submit via the feedback widget so we can read your report. Subject to Web3Forms privacy policy.
• Cloudflare (cron workers) — runs scheduled background jobs (odds polling, settlement, leaderboard recompute). No per-user data flows through Cloudflare beyond what Supabase has already stored.

The Service displays a single outbound affiliate link to a real sportsbook (Rainbet). Clicking it does not transmit any of your data; we never share your email, IP, or browsing activity with the partner site. Full details on the affiliate arrangement live on our Affiliate Disclosure page.

If you are in the European Economic Area, the UK, or any jurisdiction with comparable rules, you have:

• Right of access — you can request a copy of the data we hold about you.
• Right to erasure — you can ask us to delete your account and associated data. Your entire row in the auth users table and the cascaded profile + bets rows can be removed on request.
• Right to rectification — you can correct inaccurate data (your username via /account settings, anything else via feedback).
• Right to data portability — you can request a machine-readable export of your data.
• Right to object to processing based on legitimate interest.
• Right to lodge a complaint with your local supervisory authority (in Poland this is UODO).

To exercise any of these rights, use the feedback widget on the home page. We aim to respond within 30 days.

We use the minimum cookies needed to run an authenticated web app:

• Essential auth cookies (Supabase Auth session). Without these you cannot stay signed in.
• Functional preferences stored in localStorage — your active mode toggle, dismissed-banner flags, and bet slip selections so they survive a page refresh.

We do not set any third-party tracking, advertising, or analytics cookies. The cookie consent banner on first visit lets you accept or decline; declining still allows the essential auth cookies to function (you can continue to sign in), but the functional preferences will fall back to session-only memory.

Account, profile, and bet-history data is retained as long as your account is active. On deletion request, the row is removed and the cascade deletes your bets too. Request logs at Vercel/Supabase follow each provider's own retention windows (typically weeks, not years). We do not maintain any independent long-term analytics store.

The Service is intended for users aged 18 or older. We do not knowingly collect data from anyone under 18. If you believe a minor has registered, contact us via the feedback widget and we will delete the account.

Supabase hosts the database in the AWS us-east-1 region (North Virginia, USA). Vercel hosts serverless functions globally. By using the Service you acknowledge that your data may be transferred outside the EEA; both providers maintain Standard Contractual Clauses for such transfers.

We may update this policy when the Service changes or when the law changes. Material changes will be flagged in a banner on the home page; the "Last updated" date at the top of this page always reflects the most recent revision.

For any privacy question, data request, or complaint, please use the feedback widget on the home page. Submissions are routed through Web3Forms to a private inbox the operator monitors. Include "privacy" in your message so it can be prioritised.