PUBLIC BETA
Privacy notice
Last updated August 14, 2026
Data CREDREP processes
CREDREP indexes public Bradbury data for connected wallet addresses, including public X handles and proof URLs recorded by the contract, REP balances, forecasts, confidence, and outcomes. The app also stores sourced market metadata and short-lived wallet authorization challenges.
Wallet authorization
Index refreshes use a human-readable wallet signature. It cannot move funds, submit a transaction, or spend REP. A signed, HTTP-only session cookie keeps the refresh active for up to seven days. CREDREP never asks for or receives your wallet seed phrase or private key.
Security and service data
Requests may generate operational logs, approximate network and device information, performance measurements, and keyed hashes used to enforce rate limits. Vercel Analytics and Speed Insights provide aggregate traffic and performance information. Do not include a seed phrase, private key, or other secret in a support report.
Why data is used
Data is used to operate the feed, public prediction record, leaderboard, abuse prevention, debugging, security, and product performance. The database is a convenience index; GenLayer remains the source of truth for onchain state.
Providers and retention
Processing involves GenLayer, X, Polymarket, Vercel, and Neon. Public blockchain records may be permanent. Cache, challenge, rate-limit, log, and analytics retention follows operational need and provider settings. Expired authorization challenges and rate-limit entries may be deleted routinely.
Your choices
You can disconnect your wallet, decline the index signature, or stop using the beta. This does not erase public blockchain records or data already published on X. Use the beta support channel for privacy or data-index questions and include only your public wallet address.