This page covers predge.io, the Predge API and the Predge Telegram bot. It is run by Predge (entity being incorporated). It describes what the code does today, including what it does not do yet. The detailed version, with evidence for each point, is on our Trust page.
What we collect
Site and signup
- Signup: your email, company and use case, the id of the API key we issue, and a hash of your IP address (used to limit abuse of the signup form). The hash uses a fixed prefix, not a secret salt, so it could be reversed. We plan to replace it with a keyed hash (target 13 November 2026).
- API keys: stored only as hashes.
- Sign-in: your email or wallet address, via Privy.
- Web analytics and errors: page events (PostHog) and error reports (Sentry), when those services are configured; Vercel Analytics.
Desk and Telegram bot
- Desk accounts: the wallet addresses you watch, your Telegram chat id, your webhook URL and the webhook signing secret. The secret is stored unencrypted today, because we need it to sign your alerts. Encryption is planned (target 13 November 2026).
- Bot: your Telegram user id and username, and the wallets you add to a watchlist.
API verdicts
- The job spec you send, including the endpoint URL; the delivery status, content type, body hash, body size and latency; the payment reference (payer, payee, transaction); agent identity fields; the signed record.
- Optional
buyer_idandmerchant_idthat you supply (up to 128 characters each). Do not put personal data in them. - We do not store the raw delivered body, only its SHA-256 hash.
Payments
- x402 (USDC): payer address, route, price, network, settlement transaction, user agent and referer.
- Paddle and NOWPayments: they handle card and crypto checkout. We receive a payment confirmation, never your card number.
Public data
Most of what Predge shows is public on-chain and Polymarket data. It is not about you unless you are the holder of a wallet we display.
What we do with it
Run the service (alerts, verdicts, the dashboard, payments), keep abusers out, fix bugs and answer support. We do not sell your data, run ads or share it with marketers.
Who processes it
"Conditional" means the service is used only when its key is set in our production settings.
| Provider | What for |
|---|---|
| Railway | Hosts the API, database (Postgres), Redis and bot services |
| Vercel | Hosts predge.io; Vercel Analytics and Speed Insights |
| Zoho Mail | The hello@predge.io mailbox |
| Name.com | DNS |
| Privy | Sign-in (email, wallet) |
| Paddle | Card checkout |
| NOWPayments | Crypto checkout |
| Telegram | The bot and Desk alert delivery |
| x402 facilitators | Verify and settle paid API calls in USDC (for example x402.org, PayAI, Circle, GoPlausible, the Monad facilitator) |
| Public blockchain RPC providers | Read public chain data for settlement-risk checks |
| PostHog (conditional) | Web analytics, only when configured |
| Sentry (conditional) | Error reports from the site and API, only when configured |
| Cloudflare Turnstile (conditional) | Bot check on the signup form, only when configured |
| Anthropic (conditional) | Writes an optional one-sentence AI comment on Pro whale alerts, only when configured. It receives the trade, wallet and market context of that alert, which is public on-chain data. |
How long we keep things
Today there is no automated deletion, except where noted below. Data stays until we delete it by hand or you ask us to.
| What | Today | Planned |
|---|---|---|
| Signups | Kept until deleted on request | Deleted after 30 days (target date 30 November 2026) |
| Desk alert events | Kept until deleted on request | Deleted after 180 days (target date 30 November 2026) |
| Database backups (Railway) | Daily backups kept 6 days, weekly backups kept 27 days, then removed automatically | No change |
| Everything else (accounts, verdicts, payments, bot data) | Kept until deleted on request | No date set yet |
Data you ask us to delete can remain in backups until those backups expire (at most 27 days).
Your rights
You can ask what we hold about you, ask us to correct it, export it or delete it, and object to its use. You can also complain to your local data protection authority. Email hello@predge.io. There is no self-serve deletion yet; we handle requests by hand within 30 days.
Where your data lives
With the providers listed above, mainly Railway and Vercel. We have not yet verified and pinned the hosting regions, so we make no residency promise. We plan to publish verified regions (target 27 October 2026).
Security
HTTPS, hashed API keys, and access to production limited to one person. Known gaps, such as the IP hash and unencrypted webhook secrets above, are listed with target dates on the Trust page. If a breach affects you, we will tell you by email and on X @PredgeAI.
Kids
Predge is for adults. We do not knowingly collect data from anyone under 18. If you think we have, email hello@predge.io.
Changes
We will update this page when what we collect or keep changes, and change the date at the top.
Contact
Predge (entity being incorporated): hello@predge.io. See also our Terms of Service and Trust page.