Privacy

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

This policy covers the $olPaid site and the ledger behind it. It does not cover Cash App, Venmo, Coinflow, Stripe, pump.fun, Jupiter, Helius, Reown (WalletConnect), pons.family, or any other service $olPaid 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, Cash App $cashtag or Venmo @username, creator wallet, fee-lock configuration, and the on-chain signatures for create and fee lock.

Recipients

The $cashtag or Venmo @username named at launch or registration. After claim, the payout method. Last-four digits of a routing number, account number, or phone are kept only as a verification hint and are not published.

Claim destinations (not public)

Cash App routing number, account number, and account-holder name; a Venmo username and US phone number; or a Tremendous email, stored encrypted. The plaintext claim secret is shown once at launch, registration, or when the launch wallet replaces an unused link. It is never written to the database; only its hash is kept.

Fees

SOL accrued, USD settled, the swap signature, and how much of each fill was paid, burned, or reserved for the $olPaid liquidity pool.

Payouts

Amount owed, current status, and each attempt’s provider reference (Coinflow transfer).

Privacy requests

The action requested, the handle it concerned, how it was verified, and a short operator note if one was left. These are the audit record of requests fulfilled on this site.

Site requests

Ordinary server and CDN logs, including IP address and user agent. Hosting and CDN providers keep those logs for a short operational period, typically on the order of weeks, then discard them. We do not run a separate log warehouse.

Text sessions

If you text START, we hold your phone number, the launch fields you send, session status, and whether you have opted out. Photos you attach are stored as the token image the same way a site launch is. We do not use that number for marketing.

There is no password account on this site. A wallet signature launches a token. A secret claim link binds a destination. Nothing here is a Cash App or Venmo login.

Token data comes from the chain and from the metadata the deployer uploaded. The $cashtag or Venmo @username is typed at launch. Accrued SOL is read from treasury transfers. USD amounts come from the Jupiter fill. A phone number for text updates comes only from a message you send to us after opting in.

Routing, account, holder name, and Venmo phone are typed into the claim form by whoever holds the secret link. $olPaid does not scrape Cash App or Venmo for those numbers.

If a token names your $cashtag or Venmo, the public ledger will show that handle, the token, and payout amounts. Bank details and phone numbers stay off the public ledger.

Each field exists because a payment cannot be made or evidenced without it. The cashtag identifies who is owed. Routing and account tell Coinflow where to send RTP or same-day ACH. A Venmo phone tells Coinflow which account to pay. The claim signature and swap signature tie an obligation to the on-chain events 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 other than whether a payout can be sent. There are no advertising or analytics trackers on this site.

No private keys and no seed phrases. The treasury signer is held separately from the application and is never asked of you. No Cash App or Venmo password. No government identity documents on our servers: Coinflow runs payee KYC on its own systems if it requires verification before the first payout. No browsing profile, and no cross-site tracking.

Cash App and Venmo payouts pass through Coinflow. For Cash App, what reaches Coinflow is what a bank payout needs: cashtag as user id, routing number, account number, holder name, amount, and our Solana treasury wallet. For Venmo, Coinflow receives a namespaced user id, the US phone number on the account, amount, and the treasury wallet. Coinflow may then collect identity documents from the payee. That collection is Coinflow’s, not ours.

Buying SOL through the site opens Stripe’s hosted crypto onramp. Stripe receives the connected Solana wallet so it can send SOL there, plus whatever identity and card details Stripe collects on its own page. That collection is Stripe’s, not ours.

Infrastructure providers necessarily handle data in passing, including the hosting and database provider, Jupiter for the SOL to USDC swap, the RPC or webhook provider the chain is read through, and the messaging provider and carriers that deliver transactional texts. They act on $olPaid’s instructions and for no other purpose.

Data may be disclosed where the law requires it. Beyond that, destinations are not sold, rented or brokered.

Registered tokens, $cashtags, Venmo @usernames, amounts routed, burned $olPaid, and payout confirmations are meant to be seen. The transparency of the ledger is a feature of the product rather than an oversight.

Routing numbers, account numbers, holder names, Venmo phone numbers, and claim secrets are not published.

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.

Encrypted destinations are kept while a handle may still be paid. You can delete a destination on the request page; we then stop using it for new payouts. Coinflow keeps its own copies under its policies. On-chain records are permanent and are outside anyone’s control, including ours.

Hosting and CDN request logs are discarded by those providers after a short operational period.

Access to the ledger is restricted, traffic is encrypted in transit, payout destinations are encrypted at rest, and treasury signing keys are held separately from the application. No system is perfectly secure, and $olPaid does not claim otherwise.

If we become aware of unauthorized access to personal data (routing or account numbers, Venmo phones, or emails), we contain it by rotating credentials and encryption keys and revoking access; determine what was involved; notify affected people and, where the law requires it, regulators, without undue delay; notify Coinflow if Coinflow-related credentials or payout records may have been exposed; and document the cause and the fix. We do not store government identity documents, which limits what a breach of our systems can expose. Coinflow’s own systems and KYC documents are Coinflow’s to secure.

Do not open a claim link you do not control. Binding a Cash App or Venmo destination is how you become payable.

Requests are made and fulfilled on the request page. There is no support chat. You can stop paying a handle, delete a stored destination, remove a token from Explore, token pages, recipient pages, analytics and the payments list, or download a copy of what the ledger holds about a handle. We verify a request against the claim secret shown at launch, or against the destination that was bound (Cash App routing and account last four, Venmo phone last four, or the Tremendous email). If you cannot prove either, leave a note on that page for the operator.

Stopping payouts holds new payments to that handle. Amounts already paid stay paid. Deleting a destination erases the stored routing, account, phone or email so it cannot be used for new payouts. Removing a token hides it on the site; if you prove the destination and do not name a mint, every token that pays that handle is hidden. The ledger record is kept and is included in a copy we give you. We do not delete the payment ledger, on-chain records, or copies held by Coinflow, Cash App, Venmo or Tremendous.

Coinflow KYC, when required, is completed on Coinflow’s verification page, not on this site.

If you opted in to text updates, reply STOP to that number to unsubscribe. We then stop sending texts to that phone unless you text START again.

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

$olPaid is not directed at children and is not intended for anyone under 18, which is the age Cash App, Venmo, and payee KYC typically require. It does not knowingly hold payout destinations for children. A handle believed to belong to a child can be stopped from payouts and removed from the site’s surfaces on the request page.

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.

Texts from $olPaid are transactional only: replies you requested, a one-time wallet sign link, and a launch receipt. We do not send marketing, price alerts, or token promotions. Message and data rates may apply. Reply HELP for commands, STOP to opt out. The public keyword campaign is on the text messages page.

$olPaid is contactable through the request page. There is no support chat. Questions about this policy, requests to stop paying a handle, to delete a destination, to remove a token from the site, and to receive a copy of ledger data are completed there.

Note that on-chain records cannot be deleted, and that Coinflow, Cash App, Venmo and Tremendous each keep their own records of payments they processed.