Privacy and hosted-content notice

This draft documents the implemented data flows. Final controller identity, lawful bases, retention periods, regional rights, subprocessors, and contact details must be approved and published before mainnet.

Public chain data

Wallet addresses, transactions, balances, launches, pool events, and creator fee destinations are public blockchain records. pumpinhood.fun indexes them to provide search, rankings, portfolios, risk signals, and realtime views; it cannot delete the underlying chain records.

Hosted service data

The API may process IP address, request identifiers, timestamps, rate-limit state, errors, wallet-scoped actions, reports, moderation decisions, and service-security logs. Wallet connection does not grant custody or expose a private key.

Uploads and reports

Images enter quarantine, undergo signature and dimension checks, malware/content scanning, metadata stripping, canonical re-encoding, and durable pinning only after acceptance. Reports may contain contact details supplied voluntarily and are visible to authorized moderators.

Sharing and retention

Infrastructure providers may process data to host the API, database, cache, object storage, IPFS pins, RPC traffic, monitoring, and security scans. Production must define least-privilege access, deletion schedules, backup retention, subprocessors, and legal preservation rules.

Your choices

You may browse without connecting a wallet. Do not put personal or confidential data onchain or in immutable metadata. Hosted-content correction, removal, access, objection, and appeal requests will follow the final regional policy; onchain data remains public.

Security boundary

No production deployer key belongs in the frontend or API. pumpinhood.fun cannot guarantee absolute security. Suspected abuse or data exposure should be submitted through the reporting channel and handled under the incident-response plan.

See the draft terms, protocol transparency, or submit a report or appeal.