Privacy Policy
Effective 2026-07-25
What the interface processes
Titan's interfaces are designed to work without accounts, sign-ups, or tracking. There are no analytics scripts and the interfaces set no cookies. What is processed falls into four clearly different buckets:
- Public on-chain data — token launches, trades, locks, balances, and fee claims are public blockchain records. Titan's indexer reads and republishes them (that is what the charts and feeds are).
- Data stored only in your browser — preferences the interface saves in localStorage on your device (listed below). It never leaves your browser.
- Data sent to Titan infrastructure — ordinary web requests to our hosting and data services, and token logos you choose to upload at launch.
- Data handled by third parties — your wallet, the RPC endpoints it talks to, and bridge routing providers, each under their own policies.
Wallet addresses and public blockchain data
Connecting a wallet happens in your browser through the wallet you choose; the interface reads your address and balances to render the UI and to prepare transactions you sign. Wallet addresses are public blockchain identifiers, and anything you do on-chain (launching, trading, locking, claiming) is permanently public by the nature of blockchains — independent of Titan.
Local storage and the acknowledgement record
The interface stores small preference records in your browser's localStorage only. They are not transmitted to Titan. Currently: your watchlist, selected chain, sound on/off, seen market-cap milestones, recent searches, a dismissed-banner flag, and your titan.fun acknowledgement (the accepted version and a timestamp — no wallet address). Clearing browser storage removes them, and the acknowledgement will be requested again.
Technical logs
Our web hosting (Netlify) and data services (the Titan indexer/API) receive standard web-request metadata such as IP address and user agent, used for operation, rate-limiting, and abuse prevention. We run no analytics or advertising trackers on top of this.
Token logos and IPFS
When you launch a token, the logo you upload is pinned to IPFS through Titan's gateway and referenced on-chain. IPFS content is public and effectively permanent — do not upload anything you would not want public forever.
Third-party services
Your wallet provider, the RPC endpoints used to read and broadcast transactions, bridge routing providers (LI.FI, Relay), and block explorers each process the requests you send them under their own privacy policies. Titan does not control them.
How information is used and kept
Request metadata is used only to operate and protect the services and is retained on the short schedules of our hosting providers. Indexed blockchain data is public by nature and retained as part of the market-data service. Browser-stored preferences persist until you clear them.
Security
The interfaces never hold your keys or funds. Transport is encrypted (HTTPS/WSS). The most important security boundary is your own wallet — review every prompt before signing.
Your choices
Use the interfaces without connecting a wallet to browse read-only. Disconnect your wallet at any time. Clear localStorage to remove stored preferences. Use your own RPC endpoints in your wallet if you prefer not to use the defaults.
Changes to this policy
If our actual data practices change, this page changes with them, with a new effective date. We will not claim less collection than the code performs.
Contact
Privacy questions: t.me/TitanDeployerSupport or x.com/TitanDeployer.