Clear about what is real.

Profiles, communities, posts, replies, images, and discovery are working beta features.

• Public content can be moderated, removed from the interface, copied, or reshared.
• Trending and recommended content is a discovery signal—not an endorsement or safety rating.

Token, pair, holder, price, volume, and payout context comes from OTC, public Solana data, and market-data providers.

• Source data can be delayed, incomplete, unavailable, or corrected after display.
• Where available, SEND.DO links to the matching OTC coin page so users can inspect the source.

SEND.DO requests routes through Jupiter and prepares a Solana transaction for the user to review and sign.

• The connected wallet—not SEND.DO—authorizes an external-wallet transaction.
• The selected liquidity venue and Solana execute the transaction. SEND.DO cannot reverse it.

SEND.DO uses one 1% app fee across supported trading routes, disclosed before wallet signature.

• Jupiter receives 0.2%; 0.6% funds later SENDO buybacks and 0.2% supports company operations. These portions add up to the 1% app fee.
• Pool or venue fees and Solana network fees are additional. The app fee is the same across Pump, Raydium, Meteora, and other supported routes.
• Collection remains disabled unless the reviewed preview gates and fixed referral fields are present.

The ledger below counts confirmed Jupiter V2 records only and starts honestly at zero.

• Demo, estimated, or third-party figures are not counted as SEND.DO revenue.
• A public ledger should separate collected fees, company allocation, buyback allocation, completed buys, and transaction signatures.

Users can connect a supported external wallet or create a user-owned embedded wallet.

• External wallet keys stay with the wallet provider and user.
• Embedded-wallet material is stored encrypted, but the beta implementation remains under security review and should not hold funds a user cannot afford to lose.

Solana transactions, wallet addresses, token balances, and contract activity are public and independently inspectable.

• SEND.DO may add labels or profile context, but it cannot alter completed onchain records.
• Displayed identities are social account links and do not prove legal identity.

The changelog records major public product changes without publishing sensitive implementation details.

• Alpha versions remain in the 0.x line.
• Current Beta builds use the 1.0.0-beta version line.