Privacy

GoLaunchMe operates this site and the ledger behind it, and is responsible for the data described in this policy. “GoLaunchMe”, “we” and “us” below mean GoLaunchMe.

This policy covers the GoLaunchMe site and the ledger behind it. It does not cover X, GoFundMe's own site, GoFundMe, pump.fun, pons.family, Robinhood or any other service GoLaunchMe reads from or pays through. Those services have their own policies, and what they do with your data is governed by them.

The ledger holds registered tokens, the fees claimed against them, what is owed to whom, and every attempt to pay it. In full:

Tokens

Mint address, name, symbol, image, description, and the fee sharing configuration read from the chain.

Recipients

The GoFundMe campaign link taken from the token description, and the campaign's public title, organiser name and image.

Fees

Amount claimed, the claim's transaction signature, and when it settled.

Payouts

Amount owed, current status, and each attempt's transaction id and receipt.

Site requests

Ordinary server and CDN logs, including IP address and user agent, kept for security and debugging.

There is no account system, so there is no profile, no password, no email address and no contact record. Nothing on this list was typed into a form by the person it concerns.

Almost all of it is read from public sources. Token data comes from the chain and from the token's own metadata. The recipient campaign comes from the description the deployer wrote, and its title, organiser name and image come from the campaign's public GoFundMe page.

This is the part worth being direct about. If a token names you, GoLaunchMe holds a record about you that you did not give it and were not asked about. That is how the product works. It is also why a donation is announced publicly rather than quietly: the person it concerns should be able to find out that it happened.

Each field exists because a payment cannot be made or evidenced without it. The campaign link identifies who is owed. The claim signature ties an obligation to the on-chain event that created it. The payout record is the receipt, and it is what makes the ledger auditable rather than merely asserted.

None of it is used to build a profile, to target advertising, or to make any automated decision about a person. There are no advertising or analytics trackers on this site.

No private keys and no seed phrases. No password or credential for your GoFundMe campaign. No card, bank or payment instrument details: money moves through GoFundMe, and GoLaunchMe never sees the instrument behind it. No government identity documents. No browsing profile, and no cross-site tracking.

The donation itself passes through GoFundMe, since that is the rail. What reaches GoFundMe is what a donation needs: the campaign, the amount, and the token's name as the donor.

Infrastructure providers necessarily handle data in passing, including the hosting and database provider and the RPC provider the chain is read through. They act on GoLaunchMe's instructions and for no other purpose.

Data may be disclosed where the law requires it. Beyond that, nothing is sold, rented or shared. There is no data brokerage here, and nothing on the list in clause 2 that anyone would buy.

Registered tokens, amounts routed, and payout confirmations are meant to be seen. The transparency of the ledger is a feature of the product rather than an oversight, and the confirmation post is published on purpose.

None of that includes anything you gave GoLaunchMe privately, because you did not give it anything privately.

Ledger records are kept for as long as the ledger exists. They are the record of what was owed and what was paid, and deleting them would remove the evidence that a payment was made to the person it was made to.

Donations are tracked until they are made, or until the hold window ends and they pass to the protocol treasury. Server and CDN logs are kept for a short operational period and then discarded.

On-chain records are permanent and are outside anyone's control, including ours.

Access to the ledger is restricted, traffic is encrypted in transit, and treasury signing keys are held separately from the application. No system is perfectly secure, and GoLaunchMe does not claim otherwise. What limits the damage here is the shape of the data: there are no credentials, no payment instruments and no identity documents to lose.

Whether a campaign accepts donations at all is a setting on GoFundMe. GoLaunchMe honours it, and also keeps a do-not-fund list for organisers who ask.

You can ask GoLaunchMe to stop funding a campaign you organise and to remove it from the site's surfaces. You can also ask for a copy of what the ledger holds about a campaign, or for a correction if something is wrong. On-chain records cannot be deleted by GoLaunchMe or by anyone else, and a donation already made on GoFundMe remains recorded by GoFundMe.

Depending on where you live you may have further rights over personal data, and you may complain to your local data protection authority.

GoLaunchMe is not directed at children and is not intended for anyone under 18. Campaigns raised for a child are run by an adult organiser; a campaign will be removed from the site's surfaces at the request of its organiser or the child's parent or guardian.

This policy may change as the product does. The version in force is the one published here, identified by the effective date and version at the top of the page. Material changes will be noted on the site.

GoLaunchMe is contactable at @gofundme_fun on X and at admin@golaunchme.fun. A message sent anywhere else does not reach us.

Privacy questions, access requests, corrections and removal requests go to either.