Last updated 5 October 2026

Privacy

Who we are

The company that operates WeBall (weball.fun) is responsible for the personal data described here. Its legal name and address are available on request. Questions or requests: [email protected].

The short version

  • There are no WeBall accounts. We don't ask for your name, email, phone number or ID.
  • We don't use advertising or analytics cookies, and we never sell or rent personal data. If we switch on paid API access, it sells access to data read from the public blockchain, not anything private.
  • Our usage records never include your IP address, browser or device details.
  • Your wallet address and everything it does on Solana are public, and always will be.

Your wallet is public

Wallet addresses, balances and transactions on Solana are public and permanent: anyone can read them, and nobody, including us, can change or delete them. Holder lists, payout rounds and the ledger show wallet addresses because they're already public on-chain and because payouts are checked against a public snapshot. Public on-chain data can sometimes be linked to a person by others, for example through an exchange account.

How the site is used

We record a few actions on the site so we can see how it's used and what to build next: connecting a wallet; starting, submitting, completing or failing a launch (and its optional lock); starting a launch by chat and using its draft; a trade going through, staying pending, partly completing or failing; accepting or declining the terms; signing a basket change or a perp change, or one failing; signing a vote, or one failing; opening or copying a referral link; and opening or posting a share card. Our server also records the outcomes it confirms itself: a terms acceptance saved, a launch or a trade through our site recorded from the chain, a vote relayed and confirmed, a referral link made and a wallet linked to a referrer. Each record holds the action, the time, the wallet address if one is connected, the coin involved and a short detail such as buy or sell, or the error shown. It never includes your IP address, browser or device details, and no cookie is used for it.

Calls to our read API and MCP server are counted the same way: which endpoint or tool, the coin asked about, whether it was free or paid, whether it worked and how long it took. Once paid access is on, a paid call also records the wallet that paid, which is public on-chain in the payment. We don't record who called, or any wallet address the request asked about. Paid calls also appear on the public ledger with the paying wallet.

If we ever distribute $BALL, WeBall's platform token, to wallets, we may use wallets' trading on WeBall coins and these usage records to decide who receives it and how much. We don't publish those calculations.

Vote to burn

A vote for a WeBall coin is a transaction from your wallet, so it's public and permanent on Solana, like any other. We record each vote we see (the wallet, the coin, vote or take back, and when) to count them, and we read voting wallets' balances of $BALL at the slot of each count. Counts are published.

Launching a coin

When you launch, the coin's name, ticker, image, description and links are written into its on-chain metadata and, on mainnet, to permanent public storage (Arweave, through Irys). They can't be deleted afterwards; we can only stop showing them on WeBall. On test networks they're kept on our own servers instead. Don't put personal information in them.

Accepting the terms

Before your first launch, trade, vote or basket change, your wallet signs a message accepting the terms. We keep that wallet address, the terms version, the message, its signature and the time, as proof of acceptance. No IP address or device details are kept with it.

AI launch help

If you press “Generate with AI” on the launch form, the coin name and ticker you typed (and the token it's paired with, if any) are sent to our AI provider, OpenRouter, to draft a description. If you launch by chat, each message you type, the launch details filled in so far and the list of tokens you can pick from are sent the same way. OpenRouter passes the request to the company hosting the model it uses. Your wallet address and image are never sent, and replies come back only to you.

Cookies and storage on your device

  • While the site is in preview, a single cookie remembers that you entered the preview key. It holds no personal information.
  • Your wallet connector may remember which wallet you used last, in your browser's storage. It stays on your device.
  • For the length of a browser session, the site keeps a launch-by-chat draft on its way to the launch page, and a note that your wallet's connection was already counted. Both stay on your device and are cleared when the session ends.
  • If you open the site through a link with a referral code, your browser keeps that code (no expiry) so it can be sent once, with your wallet's first terms acceptance. It stays on your device until then; clearing the site's data removes it.

Server logs

Like any website, our hosting and network providers keep standard request logs (such as IP address, browser type and the page requested) to keep the site running and protect it from abuse. We don't combine them with wallet addresses or usage records. Our own request logs are kept for up to 90 days (30 for the website). Our signing services keep their own security logs, which include the wallets and amounts of the transactions they sign and of paid API payments, for up to 400 days.

Some things load straight from other services, which then see your IP address under their own policies: coin images kept in permanent storage can load from the Arweave gateway, and your wallet app talks to its own provider.

Who processes data for us

  • Amazon Web Services: hosting and our database, in the United States.
  • Cloudflare: network delivery and protection against attacks.
  • OpenRouter, and the company hosting the model it uses: AI description drafts and launch by chat, only when you use them.
  • Helius: reading and sending Solana transactions on our servers' behalf.
  • Jupiter: prices and token data, and routes for trades it handles, which include your wallet address.
  • Irys and Arweave: permanent storage of coin images and metadata.

We may also share data if the law requires it, to protect people or the service, or with a buyer if WeBall is ever sold, under this notice.

Why we use data

To run the interface and the services you ask for (performance of our agreement), to keep it secure, prevent abuse and understand how it's used so we can improve it (our legitimate interests), and to meet legal obligations.

How long we keep it

Usage records and terms acceptances: for as long as WeBall runs, since they're needed to understand how the product is used and to show who accepted which terms; we'll delete or aggregate usage records once they're no longer useful. Our own request logs: up to 90 days. Signing-service logs: up to 400 days. Our providers' logs: under their own policies. On-chain data and permanent storage can't be deleted by anyone.

Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict or object to our use of your personal data, to get a copy of it, and to complain to your data protection authority. Because we hold very little that identifies you, we may need you to prove you control a wallet (by signing a message) before acting on a request about it. We can't change or delete anything on-chain or in permanent storage.

International transfers

Our servers are in the United States. Where the law requires it, transfers from other countries rely on safeguards such as the European Commission's standard contractual clauses.

Security

We use encryption in transit, restricted access and keys kept in dedicated signing services. No system is completely secure, and you're responsible for keeping your own wallet safe.

Children

WeBall is not for anyone under 18, and we don't knowingly collect data about children.

Changes

We'll update this notice when what we do changes, and date every change at the top of this page.