Privacy Policy

Runitup has no accounts, no email addresses and no passwords for users. There is very little about you for us to hold, and that is by design.

What we never collect

• Your private keys or recovery phrase — we have no way to receive them
• Your name, email address or phone number
• Any identity documents

What we store

Public blockchain data. Launches, trades and balances are already public on the blockchain. We index them so pages load quickly. This is not private information and we did not obtain it from you.

Things you choose to submit. A token's image, description and social links, and a display name on your profile. These are published on the site — that is their purpose.

Your wallet address. Used to show your portfolio, launches and rewards. It is a public identifier, and connecting a wallet does not tell us who you are.

Your wallet address is pseudonymous, not anonymous

Worth being straight about: a wallet address is permanent and every transaction it makes is public forever. If your address is linked to your identity anywhere — an exchange withdrawal, a social post, an ENS name — that link can be followed to everything else it has done. This is true of all public blockchains and is not something Runitup can change.

Third parties

• RPC providers relay your requests to the blockchain and will see your IP address and wallet address, as they would with any web3 site.
• Our hosting provider keeps standard server logs, including IP addresses, for security and reliability.
• Google Analytics counts visits so we can see which parts of the site get used. It receives your IP address and the address of each page you open. See below.
• Your wallet has its own privacy policy that we neither control nor see.

Google Analytics

We use Google Analytics 4 to count visits and see which parts of the site get used. That is the whole purpose. We are not trying to work out who you are, and there is nothing here that would let us — we hold no account, no email address and no name to attach a visit to.

What Google receives

Rather than describe this in general terms, here is what actually leaves your browser. We read it off a real page load rather than from documentation.

• A random visitor id stored in a cookie, so a second visit is recognised as the same browser rather than counted twice. It is a number Google generates. It is not derived from anything about you.
• The full address of each page you open, and its title.
• Your IP address, which every site you visit necessarily receives. Google uses it to work out an approximate location and does not show it to us.
• Your browser, operating system, language and screen size, and the page you arrived from.

Wallet addresses reach Google through page addresses

This is the part nobody would work out on their own, so we would rather say it than have you discover it. Some pages here have a wallet address in the address of the page itself — a profile is /profile/0x…. Google receives the address of every page you open, so opening one of those sends that wallet address to Google as part of the page it is recording.

It is public information either way, and we do not connect it to anything. But it means a wallet address can end up in a third party's records because of how our URLs are built, which is not obvious from the outside.

What we do not do with it

• We do not use it for advertising, and personalised advertising is switched off.
• We do not sell it, and we do not share it with anyone besides Google.
• We do not use it to identify individuals or to follow you to other sites.
• The operator console is excluded from analytics entirely.

Cookies it sets

Two, both first-party and both lasting 400 days: _ga and _ga_YD3F38J6Q2. They exist to recognise a returning browser and to group page views into a single visit. Deleting them resets you to a new visitor as far as Google is concerned, and costs you nothing here.

How to turn it off

Any content blocker or privacy extension stops it, as does Google's own opt-out add-on, and so does clearing the two cookies above. The site works exactly the same either way — nothing about launching, trading or reading a page depends on analytics working, and we do not detect or care whether you have blocked it.

Google's own handling of this data is covered by its privacy policy and its page on data collected through partner sites, neither of which we control.

Consent

We do not currently show a cookie consent banner. If you are in the EU or the UK, the law there generally expects analytics cookies to be set only after you agree — so treat this as something we have not implemented yet rather than something we are claiming is covered. Blocking analytics with an extension has the same practical effect in the meantime.

Cookies

Beyond the two analytics cookies above, we use local storage to remember interface preferences such as your theme, and a cookie to remember that you have entered an invitation code while the site is invitation-only. We run no advertising cookies of our own.

Deleting your data

We can remove content you submitted to us — a token image, a description, a display name. We cannot delete anything from the blockchain, because nobody can. On-chain records are permanent and outside our control.

Contact

Questions about this policy can go through the channels linked in the footer.

This policy is a plain-language starting point, not legal advice, and it has not been reviewed by a lawyer. If you have users in the EU, UK or California, specific obligations (GDPR, CCPA) may apply that this does not cover — have a qualified lawyer review it before relying on it.