Privacy
Most of what Gachamon holds is already public, and almost none of it was collected from the people it names. This policy sets out what there is, where it came from, and what happens to it.
- Effective
- 25 September 2026
- Version
- 1.1
- Applies to
- The Gachamon site
1 Scope
This policy covers the Gachamon site and the ledger behind it. It does not cover Pump.fun, Stonk.fun, or any other service you use to create a coin.
2 What we hold
The ledger holds launched tokens: address, name, ticker, image, chain, launchpad, reported market data, selected pack, public wallet addresses and ordinary server logs. Visitors connect a wallet; operator access uses a separate server-managed secret.
Launch and pack-opening records include signed transaction bytes for recovery, payment status, public receipts and the saved card recipient. Random-holder delivery also stores the public holder snapshot and selected winner. Your browser keeps pending launch recovery details. Token artwork and metadata are uploaded to public hosting. OpenRouter receives selected public coin, pack, wallet-balance and opening facts to write agent updates.
Opening captures and results
Automatic pack agents stream and record an isolated Collector Crypt browser, including the pack animation and revealed card. Gachamon publicly displays this stream, saved videos, screenshots, timestamps, selected pack, public recipient addresses and result receipts. Videos and screenshots are retained for up to seven days, subject to storage capacity. Opening metadata and result records remain after media expires. Operator-shared captures start after the operator publishes a preview; automatic captures start with the configured agent workflow.
3 Where it comes from
Launch records come from confirmed launch transactions, and market caps are read from the public pad. On-chain records stay public.
4–13
Nothing is used for advertising. We never request the private key or seed phrase of your connected creator wallet, or government IDs. The server holds separate Gachamon operating-wallet credentials and agent-wallet derivation secrets to execute the configured workflow; these are not included in public API responses. Ledger records are kept for as long as the ledger exists. On-chain records cannot be deleted.
