Privacy Policy

What ubi.fun receives when you use it, what it keeps, and what is public by design.

Last updated: October 22, 2026

This policy covers the ubi.fun website, its API and its MCP server: wallet connections, what your browser stores, what our servers receive, and what is public on chain by design.

The short version

The points that matter most. The full text below is what applies.

No accounts. You can browse without connecting a wallet. Connecting goes through your own wallet. There is no email sign-up, and ubi.fun never creates or holds a wallet for you.
No analytics or ad tracking. The site loads no analytics, advertising or session-recording tools.
A few settings stay in your browser, such as theme, language, pending transactions and a referral link for 90 days.
Our servers and providers see technical request details, such as your IP address, your browser and the wallet address you look up.
Chain records are public. Addresses, balances, trades, launches, payouts and X handle bindings can be read by anyone, and nobody can remove them.
Launch images and details become public when you upload them, before the launch transaction is sent.
We store very little ourselves: referral names you claim, token metadata edits, and data indexed from the chain.
We do not sell, rent or trade personal data.

1. Wallet connections, no accounts

Public pages work without a wallet. When you connect, the site reads your wallet address and network so it can build the transactions you ask for. You can connect a browser-extension wallet, or use WalletConnect (by Reown), Coinbase Wallet, Binance Wallet or Safe. There is no account and no password. Connecting a mobile wallet through WalletConnect sends encrypted session traffic through Reown’s relay servers, which can see connection metadata such as your IP address.

Some features ask you to sign a message, which proves you control a wallet without sending a transaction: claiming a referral name, and editing a token’s description, image or links as its creator. What you sign for is stored with your wallet address, see section 5.

2. No analytics or ad tracking

ubi.fun does not run analytics, advertising, session-recording or error-reporting tools. The site’s security policy only lets it connect to the services it needs, listed in section 8.

3. Browser storage and cookies

The site keeps your settings in your browser’s local storage: theme, language, dismissed banners, recent searches, your transaction history, pending bridge transfers, your quick-buy amount, and the referral link you last opened (applied for 90 days). Your wallet and its connector may also store session data so a connection can be restored. Their own policies cover it.

We set one cookie ourselves, during X sign-in: a short-lived cookie on api.ubi.fun ties the sign-in to your browser, expires after 10 minutes and is cleared when the sign-in ends. Cloudflare may set its own security cookies when it protects our API.

You can disconnect from the wallet menu and clear site data in your browser at any time. Clearing browser data does not remove anything from the chain.

4. Requests to our servers

The website is hosted on Vercel. Our API (api.ubi.fun, which also serves the MCP server) runs on our own servers behind Cloudflare, and the site loads Cloudflare’s bot-check script. Each request carries technical information such as the page or endpoint, your IP address, the time and your browser details. Requests for a wallet’s balances, earnings or activity also include the wallet address being looked up.

Our API uses your IP address to rate-limit requests. Its server logs are kept only briefly and rotate out automatically as they fill.

5. What we store

Our database holds data indexed from the public chain (tokens, trades, holders, payout rounds), plus two things you choose to give us:

Referral names. When you claim a referral name, we store the name and the wallet that signed for it. Anyone can open your link and see which wallet the name points to.
Token metadata edits. When a creator edits a token’s details, we store the new document’s address and keep the previous one so every change can be traced.

We do not collect names, email addresses or phone numbers through the site.

6. Uploads and launches

When you prepare a launch, the image and the token’s details (name, symbol, description and links) are sent through our API to Filebase and pinned on IPFS, before the launch transaction is sent. They are public from that moment, even if you never launch, and content on IPFS cannot reliably be deleted. Metadata edits work the same way. Do not upload anything private.

Token images are loaded from IPFS gateways, and the gateway serving an image can see the request.

If you name an X handle as a recipient, our server looks up that handle’s public name and avatar through twitterapi.io so you can confirm it, and caches the answer for a day.

X sign-in is only used to claim earnings paid to an X handle. You sign in on X, which gives us read access to your X username. We do not store your X access token. Our signer then confirms which wallet the handle belongs to, and you submit that binding from your wallet. The binding is a public on-chain record.

8. Third-party services

Wallets and connectors: your wallet, WalletConnect (Reown), Coinbase Wallet, Binance Wallet and Safe handle connections, signing and sending.
Arc RPC providers, including Circle’s public RPC and QuickNode, answer the reads your browser makes, which can include your wallet address.
Circle: the bridge talks to Circle’s CCTP services from your browser and reads balances on the source chain through its public RPC.
Uniswap: buys paid with a token other than USDC are quoted through our API by Uniswap’s API, which receives the trade and your wallet address.
Filebase and IPFS gateways host and serve launch images and metadata.
X and twitterapi.io for sign-in and handle previews.
Cloudflare and Vercel carry requests to our API and the website.
External links, such as block explorers, MoonPay, Relay, bridge.usdc.com and token websites, send you to services whose own terms and policies apply.

9. Public blockchain information

Arc is a public ledger. Wallet addresses, balances, trades, launches, payouts, referral earnings and X handle bindings can be read by anyone, and ubi.fun displays them on token pages, holder lists, activity feeds and the leaderboard. ubi.fun cannot remove these records or make them private. A wallet address is pseudonymous, not anonymous: anyone who links an address to you can see its public activity.

10. No sale of personal data

We do not sell, rent or trade personal data. Public chain records stay public whether or not ubi.fun exists.

11. Contact and changes

Questions about this policy: contact@ubi.fun. Updates are published on this page, with the date at the top. The Terms of Service cover the rest of what using ubi.fun means.