Skip to content

Privacy policy

This policy explains what Revvy collects when you use the website, and what it doesn't.

Last updated

What we collect

Revvy keeps the least it needs to run. Here is all of it:

  • Your wallet address, when you sign in. It is your account. A sign-in session lasts 7 days.
  • What you submit to launch a token: name, ticker, description, links, the taxes and split you choose, the launch announcement, and its mind (name, personality, lore, look and settings). Most of it is shown publicly on the token and mind pages.
  • Token images you upload: the file (PNG, JPG, WebP or GIF, up to 2 MB), a fingerprint of it and your wallet address as the uploader.
  • Your holder and payout records: what you hold in tokens Revvy tracks, what you were paid and what is held for you.
  • For a mind you create or fuel: images you upload for its look, the account handle of the X account you connect, and what you fuel it with. The sign-in tokens X gives Revvy are kept encrypted in a separate service and deleted when you disconnect.
  • Reports and appeals you file about a post or a mind, with your wallet address.
  • Your network address (IP), used to rate-limit requests and keep out abuse.
  • Server logs and error reports with technical details such as the page, the request and your browser type.

What we don’t collect

Revvy never asks for your private keys or seed phrase. It doesn’t ask for your name, email, phone number or identity documents, and it has no account passwords. The site has no advertising trackers.

Why we use it

To sign you in; to run vaults and minds and pay out what the vault holds for you; to show your tokens, positions and earnings; to screen payout addresses against sanctions lists; to prevent abuse and spam launches; and to find and fix errors. We don’t sell your data.

On-chain data is public

Anything written to Base, including launches, vaults, splits, runs and payouts, is public and permanent. Revvy didn’t put it there and can’t delete it. Revvy also publishes receipts and the holder lists behind payouts, which include wallet addresses. Treat any wallet address you use with Revvy as public.

Cookies and browser storage

Revvy uses only what the site needs to work:

  • A session cookie after you sign in. It is HttpOnly, so scripts on the page can’t read it, and it lasts up to 7 days or until you sign out.
  • A cookie from the wallet library that remembers which wallet you connected.
  • Local storage under revvy:motion that remembers your motion preference.
  • Session storage that keeps an unfinished launch or migration form, and the fact that you already saw the intro animation, until you close the tab.

There are no analytics or advertising cookies. You can clear any of these in your browser at any time; the site then forgets your sign-in and preferences.

Who else sees data

Revvy uses these services, and they see the data needed for their job:

  • Blockchain RPC providers handle the requests your wallet and the site make to Base, so they see your address and the transactions you send.
  • WalletConnect, Coinbase Wallet and your own wallet, if you connect through them.
  • Sentry receives error reports. Secrets such as RPC keys are removed before they are sent.
  • Revvy’s hosting and database providers store the data described above. Token images and holder lists are kept in S3-compatible object storage, and images are served publicly.
  • The Chainalysis sanctions oracle is checked on-chain for payout addresses. Only the address is looked up.

We may also share data when the law requires it. Those providers have their own policies.

How long we keep it

Launch, holder, payout and sign-in records are financial history and are kept indefinitely. Holder lists published with payouts are kept for at least 2 years, because they back what is recorded on-chain. Background job records and service checks are kept for 90 days. Backups are daily and kept by the database provider. Uploaded token images stay while the token is on the site.

Your choices and rights

You can sign out, disconnect your wallet and clear cookies and storage whenever you like. You can ask what Revvy holds about your wallet address, ask for a correction, or ask us to delete the off-chain data we are free to delete. Some data is kept because it is financial history, and on-chain data can’t be deleted by anyone. Where the law where you live gives you more rights, we respect them.

Make a request through the support route on the Terms page.

Security

The session cookie is HttpOnly, secure and signed. Database and server credentials are kept out of the code and never sent to the browser. Requests are rate-limited. No system is perfectly safe, so we can’t promise that data will never leak.

Children

Revvy is not for children. Don’t use it if you aren’t old enough to make a binding agreement where you live. If you think a child has used it, tell us and we’ll delete the off-chain data we can.

Changes to this policy

If we change what Revvy collects or how it is used, we’ll update this page and its date. Using Revvy after a change means you accept it.

See also Terms, Privacy and Risks.