Terms & privacy
Plain-language terms for using PaidIn. By launching a token, connecting LinkedIn or GitHub or claiming fees you agree to them.
1. What PaidIn is
PaidIn is software that helps you launch tokens on third-party protocols (pump.fun on Solana, Four.meme for new BNB Chain launches when enabled, and the existing Clanker and Flap integrations) with creator fees, token tax or LP rewards routed according to the displayed allocation to one recipient named by a LinkedIn or GitHub profile. PaidIn is not a broker, exchange, custodian of your wallet, or investment adviser, and is not affiliated with LinkedIn, GitHub, pump.fun, Four.meme, Clanker or Flap. Nothing on PaidIn is financial advice.
2. Launching
- You launch from your own wallet and pay the network fees and any first buy. Transactions on public blockchains are final.
- The recipient and revenue allocation shown before approval is locked on chain at launch and cannot be changed by you or by PaidIn.
- You may only name people you believe would not object, you must not imply that a named person endorses, created or promotes your token, and you must not use PaidIn for fraud, market manipulation, impersonation, harassment or anything unlawful where you or the people involved are.
- Tokens are highly speculative and can lose all value. You are responsible for what you launch and for complying with the laws that apply to you.
3. Being named
- Being named as a fee recipient does not mean endorsement, affiliation or participation in a token, and PaidIn says so on every token.
- If you own a named profile you can hide it from discovery and stop new launches from naming it. Fees already allocated to you stay yours.
- To receive fees you must prove you own the profile. PaidIn may refuse or reverse a match it has reason to believe is wrong, and may pause payouts while a dispute is reviewed.
4. Fees and payouts
- PaidIn receives 10% of each token's creator fee, set in the same locked allocation.
- Payouts only go to the wallet you bound on each network. Solana changes wait 24 hours; EVM changes follow the delay set in that network's registry, shown before binding and in the change notification. Keep your wallet and LinkedIn or GitHub account secure: PaidIn cannot recover funds sent to a wallet you bound.
- On Solana, unclaimed revenue is held in an escrow address whose key PaidIn's server manages for distributions and claims. On EVM networks it is held by the token's vault contract.
- PaidIn pays the gas for binding and payouts and may wait until an amount is worth more than its gas before paying it.
- You are responsible for any taxes on what you receive.
5. Privacy
- When you connect LinkedIn, PaidIn receives your LinkedIn member id, name, profile photo and email address (OpenID Connect). It uses them to recognise you and contact you about your fees, and never shows your email publicly.
- When you connect GitHub, PaidIn confirms your public account id, username, name and avatar. It does not request private repository or private email access and does not retain the OAuth access token after checking your account. GitHub and LinkedIn identities are not automatically merged.
- PaidIn stores the profile slugs that launchers name, which identity owns which profile, the wallets you bind, launches and payouts, and an audit log of sensitive actions.
- Only a one-way reference (a hash) of a recipient goes on chain — never your name or email. Wallet addresses and transactions on public blockchains are public by nature.
- PaidIn uses a session cookie to keep you signed in. It does not sell personal data or use advertising trackers.
- You can ask for your account data to be exported or deleted; on-chain records cannot be deleted.
6. No warranty
PaidIn is provided as is. Smart contracts, launchpads, RPC providers and blockchains can fail or change. To the extent the law allows, PaidIn is not liable for losses from using it, from third-party protocols, or from market movements.
7. Changes
These terms may change; the date above shows the latest version. Changes never alter a revenue allocation already locked on chain. Questions: see the docs.