Privacy Policy

Last updated: August 21, 2026

Your Privacy on a Public Chain

§

Betable.fun uses Internet Identity passkeys — not email/password accounts. This Policy describes what we process (principals, optional profile fields, device-local storage, public on-chain activity, and optional off-chain mirrors/analytics), what we do not collect (II recovery phrases and Betable passwords), and the hard limits of deletion on an immutable ledger. Please read it together with the User Agreement.

1. Scope & Model

§

This Privacy Policy explains how Betable.fun operators ("we", "us") handle information when you use Betable.fun — a decentralized prediction-market interface on the Internet Computer (ICP), authenticated with Internet Identity (II) passkeys.

• Betable is not a traditional email/password web app. We do not ask you to create a password for Betable, and we do not custody Internet Identity recovery phrases or passkey private keys.

• Much of what you do on-chain (principals, transfers, orders, category/XFT links, market text stored in canisters) is public by design on ICP. Off-chain mirrors and analytics are additional layers described below.

• Related documents: User Agreement at /agreement; security tips at /security.

2. Identifiers & Information We Process

§

Depending on how you use the Service, we may process:

• Internet Identity principal(s) and related canister session/delegation metadata needed to authenticate calls.

• Optional profile fields you choose to set (for example display labels, avatars, or public bio-style text) where the product supports them.

• Device-local storage on your browser/device (preferences, UI state, welcome/terms acceptance flags, cached principals, optional linked Afta principal hints).

• Transaction and market activity visible to our interfaces: deposits/withdrawals references, orders, positions, claims, fees, category claims, and similar — largely derived from public chain state or mirrors of it.

• Technical logs that may include IP address, user agent, referrer, approximate location derived from IP, timestamps, and error diagnostics when you hit our web endpoints, APIs, or analytics tooling.

• Support communications you send to privacy@betable.fun or support@betable.fun (email content and headers).

• Optional integrations you connect (for example device sync mappings, trading/API keys you generate, or third-party oracle/partner flows).

3. What We Do NOT Collect

§

• Internet Identity recovery phrases / seed-style backup words, passkey private keys, or device biometrics. Those stay with you and II / your authenticator.

• A Betable account "password" — authentication is II-based, not password signup.

• We do not require your legal name or government ID to browse public markets; if a future compliance flow ever requests identity documents, that will be disclosed separately at the point of collection.

• We do not sell your personal information.

4. On-Chain Public Data vs Off-Chain Mirrors

§

• On-chain: ICP ledgers, Betable canisters, Afta Cash XFTs/labels, bags, and similar public state can be read by anyone with network access. Principals are pseudonymous but linkable across activity.

• Off-chain mirrors: we may use databases such as Supabase (or similar) to index markets, categories, articles, API-XFT links, or stats for faster UI and search. Mirrors aim to reflect chain state but can lag or be incomplete.

• Articles and UGC may be stored on-chain and/or mirrored off-chain for delivery.

• Analytics and operational telemetry may run off-chain to understand performance and abuse.

5. How We Use Information

§

• Provide, operate, secure, and improve the Service (trading UI, category ownership views, market creation, resolution displays, peri markets, embeds).

• Authenticate II sessions, enforce rate limits, detect fraud, wash trading, scraping abuse, and security incidents.

• Sync or repair off-chain mirrors with canister state.

• Display public profiles, leaderboards, category stats, and market metadata you make available through the product.

• Respond to support and privacy requests.

• Comply with law, enforce the User Agreement, and protect users and infrastructure.

• Communicate service notices when we have a channel to reach you (for example in-app banners or reply to an email you initiated).

6. Sharing & Recipients

§

• Public chain participants: anyone can observe public canister and ledger data; Betable cannot make public chain history private.

• Afta Cash / XFT / bag / operator infrastructure when you claim categories, renew labels, or use licenses — those interactions are with third-party canisters and apps.

• Processors that help run the Service (hosting, CDN, analytics, error tracking, email, Supabase-style mirrors) under contractual or technical constraints appropriate to the data.

• Professional advisors or authorities when required by law, legal process, or to protect rights, safety, and integrity.

• A successor operator if the Service is transferred, subject to this Policy’s spirit and applicable law.

• We do not sell personal information. Aggregated or de-identified metrics may be shared publicly (for example volume stats).

7. Cookies, Local Storage & Similar Tech

§

• Essential: II session/delegation material and app state required to keep you signed in and to submit canister calls from your browser.

• Preferences: theme, dismissed banners, locale-like settings, and similar UX choices.

• Welcome / terms acceptance: flags recording that you acknowledged Terms or onboarding prompts.

• Analytics cookies or similar identifiers if enabled, to understand traffic and reliability.

• You can clear site data in your browser; doing so may sign you out or reset preferences but will not erase public chain history.

8. Retention

§

• Blockchain / canister data is generally permanent or controlled by protocol rules, not by a simple "delete account" button. Betable cannot erase ICP ledger history or immutable canister records.

• Off-chain mirrors, logs, and support tickets are retained as long as needed for operations, security, disputes, and legal duties, then deleted or aggregated when reasonably practicable.

• Device-local data remains until you clear it or uninstall/clear site storage.

• Backup and disaster-recovery copies of off-chain systems may persist for a limited period after deletion from primary stores.

9. Your Rights & Limits

§

Depending on your jurisdiction, you may have rights to access, correct, delete, port, or restrict certain personal data, or to object to certain processing.

• Practical limits: we cannot delete public on-chain activity or XFTs you control; we may only delete or correct off-chain copies we control (profile mirrors, support mailboxes, analytics identifiers) where feasible.

• To exercise requests, email privacy@betable.fun from a context that helps us locate your principal or ticket (we may ask you to prove control of a principal).

• We may deny requests that are unlawful, impossible on-chain, frivolous, or that would compromise security or others’ rights.

• You can stop using the Service and clear local storage at any time.

10. Children

§

• Betable.fun is not directed to individuals under 18 (or the higher age of majority where you live).

• We do not knowingly collect personal information from children. If you believe a minor has used the Service, contact privacy@betable.fun and we will take reasonable steps to remove off-chain data we control.

11. International & Decentralized Processing

§

• ICP and II are globally distributed. Canister state and node operators may process data in many countries.

• Off-chain processors may likewise be located outside your country. By using the Service you understand that decentralized and cross-border processing is inherent to the architecture.

• Where required, we use appropriate safeguards for off-chain transfers we control; public chain publication is a separate, user-driven disclosure.

12. Security

§

• We apply reasonable technical and organizational measures for systems we operate (HTTPS, access controls on off-chain stores, least-privilege practices).

• No method of transmission or storage is 100% secure. You must protect your II devices, recovery methods, approvals, and category XFTs — see /security and User Agreement Section 5.

• Report suspected vulnerabilities or account compromise via support@betable.fun.

13. Third-Party Services

§

• Internet Identity, ICP ledgers/subnets, Afta Cash, price providers (for example CoinGecko or similar), analytics, hosting, and oracle/partner tools have their own privacy practices.

• Following links or signing canister calls to third parties is at your direction; review their policies.

14. Changes

§

• We may update this Privacy Policy periodically. The "Last updated" date will change when we do. Material changes may be highlighted in-product. Continued use after the effective date means you accept the updated Policy where permitted by law.

15. Contact

§

• Privacy requests: privacy@betable.fun

• General support: support@betable.fun

• Pages: /privacy, /agreement, /security, /support

Questions About Privacy?

§

Contact our privacy inbox at privacy@betable.fun. For account security and category XFT custody tips, see /security. Terms: /agreement.

Passkeys stay with you — chain data stays public

We design Betable so we never need your Internet Identity recovery material. Treat on-chain activity as public, renew category XFTs on time, and write privacy@betable.fun if you need help with off-chain data we control.

Betable

Global prediction markets — own categories, create, earn.

Own categories · create markets · earn on ICP

Platform

MarketsCategoriesTopsCreatePendingArticlesWatchingWallet

Legal

AgreementPrivacySecurity tipsSupport@betabledotfun

© 2026 Betable · Own the category. Create the market.

ICP

NAV