01
Scope & acceptance
These terms describe the conditions for using the p402 website and its project-preparation, wallet-connection, public-chain inspection, and related interfaces. “p402” refers to this service; “you” includes individual visitors and anyone acting for a project or organization.
By using the service, you agree to these terms to the extent permitted by applicable law. If you do not agree, stop using it. If you represent an organization, you must have authority to act for it. These terms do not override rights that cannot lawfully be excluded.
Publication notice: this document is a proposed terms framework. The operator’s legal identity, formal notice address, governing law, and dispute venue have not been supplied. Those details and legal review must be completed before commercial launch; this page does not invent them.
02
Eligibility & lawful use
Use the service only if you can legally enter a binding agreement where you live and are permitted to use the relevant digital-asset services. You are responsible for assessing local restrictions, sanctions obligations, consumer rules, securities rules, and tax requirements applicable to your activities.
Do not use p402 where doing so would violate law, a binding restriction, or another party’s rights. Access to a website or wallet is not evidence that a token issuance, offer, sale, or purchase is lawful in your jurisdiction.
03
Service scope & availability
Launch and simple migration relaunch can create real tokens on Solana mainnet. Public metadata approval and token creation are separate wallet requests. Token creation is simulated before signing; a simulation or returned signature is not a completed launch. Confirmation includes verification of mint and launch-pool accounts. Initial purchases and holder-continuity allocations are not supported.
Public blockchain data can be incomplete, delayed, unavailable, or affected by RPC limits. Indexing, integrated trading, migration record publishing, snapshots, claims, distributions, and bridging are not currently implemented. Features may change, be limited, or be unavailable without guaranteed uptime.
p402 is an interface, not a bank, broker, investment adviser, custodian, or guarantee of a creator’s performance. References to a chain, protocol, wallet, or provider do not imply endorsement or affiliation.
04
Wallets & transaction responsibility
Your wallet remains under your control. You are responsible for its security, backups, selected network, addresses, permissions, and every request you approve. Never provide a seed phrase or private key to p402 or anyone claiming to represent it.
Verify the complete wallet request before signing. Blockchain transactions can be irreversible; p402 cannot recover lost keys, reverse a confirmed transfer, or guarantee recovery of funds sent to a wrong address. A wallet connection is not itself a token launch or transfer authorization.
05
Creator responsibilities
You must have the necessary rights and authority to use submitted names, symbols, artwork, descriptions, trademarks, links, and project information. You remain responsible for token disclosures, promises, utility delivery, community communications, and compliance.
- Do not misrepresent ownership, affiliations, product availability, audits, revenue, token rights, or expected returns.
- Do not upload infringing, unlawful, deceptive, malicious, or privacy-invasive content.
- Do not claim that p402, Raydium, Robinhood, Solana, or a wallet provider has approved your project without explicit authorization.
- Creator-selected badges and x402 fields are not certifications, audits, payment integrations, or verified guarantees.
You retain your rights in your submitted material. You permit the service to process and display it as needed for the functionality you request, subject to applicable rights and any future publishing settings. Drafts are not onchain records. After metadata approval, artwork and project descriptions are hosted publicly, including when token creation is cancelled. Confirmed token metadata points to that public content.
06
Migration & holder continuity
Migration Studio prepares a successor project; it does not transfer an existing contract or balances between chains. An ERC-20 inspection establishes only that public contract calls returned data. It does not establish deployer ownership, community approval, authority to migrate, or any holder entitlement.
Descriptions of retirement, continuity, snapshots, allocations, and claim windows are creator-provided planning notes unless expressly verified through implemented infrastructure. No original token is burned or disabled by entering a draft. No automatic swap, bridge, redemption, distribution, or claim is provided.
A creator is responsible for obtaining authorization, disclosing the treatment of existing holders, and distinguishing a new issuance from the original asset. Robinhood origin inspection uses mainnet chain ID 4663; it is not a testnet-to-mainnet conversion.
07
Digital asset & protocol risks
Digital assets may lose all value. Risks include extreme volatility, inadequate liquidity, price manipulation, malicious creators, smart-contract defects, authority abuse, validator or network failures, RPC outages, compromised frontends, irreversible mistakes, and changes in law.
Bonding curves and graduation mechanisms do not guarantee demand, liquidity, price stability, listing, or a successful project. An initial buy does not guarantee protection from bots or sniping. External product links, project descriptions, and future token utility may fail or be fraudulent. Conduct your own assessment; nothing here is personalized investment, tax, or legal advice.
08
Fees, taxes & refunds
No fixed launch fee or numerical platform fee is promised in the current interface. Before signing, review decoded protocol and platform fees and the simulated wallet-cost estimate. Estimates may differ from final charges. A platform-account check is not a fee quotation.
Blockchain network fees and third-party charges may be incurred even for failed transactions and may not be refundable by p402. Any refund rights required by law remain intact. You are responsible for your own tax analysis and reporting. p402 does not promise profits, buybacks, burns, revenue distributions, or reimbursement of trading losses.
09
Prohibited conduct
- Fraud, impersonation, market manipulation, wash trading, deceptive fundraising, or knowingly false migration claims.
- Theft, phishing, wallet-draining behavior, malware, unauthorized access, or attempts to obtain other users’ private keys.
- Abusing public RPCs, bypassing safeguards, disrupting the service, or exploiting vulnerabilities against other users.
- Infringing intellectual property, exposing personal information without authority, or unlawful harassment.
Access may be restricted to protect users, comply with law, or respond to abuse. Restricting this interface does not remove independent blockchain records or transfer control of user wallets.
10
Public data & local drafts
Blockchain addresses, balances, transactions, and submitted contract addresses can be public. Chain reads are processed by external infrastructure, including Helius for Solana and public RPC providers for supported EVM networks. Your browser and hosting infrastructure may process technical request information. Do not assume a wallet address is anonymous.
The normal launch form exists in the current tab. Migration drafts and artwork are stored locally in the browser; wallet selection is also remembered locally. Shared-device users may see saved drafts. Clearing site data removes local drafts. A saved draft is not published. Approving metadata publishes artwork, descriptions, public links and creator-declared utility or migration context in Lovable Cloud storage. Content-addressed paths are not overwritten; blockchain metadata and independent copies may persist indefinitely.
No statement here guarantees that no other technical information is processed. A complete privacy notice, retention policy, and operator contact details must be finalized for commercial operation. Avoid entering sensitive personal information into project fields or public messages.
11
Third-party services
Wallets, blockchains, Raydium, Helius, public RPC providers, explorers, social platforms, and creator websites are independently operated. Their own terms and availability apply. p402 does not control their security, fees, content, or decisions.
External links are references, not warranties. Check the destination and official domain before connecting a wallet or following instructions. No partnership or endorsement is implied solely by an integration or a brand reference.
12
Disclaimers & liability
To the extent permitted by law, the service is provided “as is” and “as available,” without warranties of uninterrupted access, accuracy, fitness for a particular purpose, or successful execution. There is no assurance that a preview will become an operational launch.
To the extent permitted by law, p402’s operator is not responsible for indirect or consequential losses, lost profits, price changes, third-party misconduct, blockchain failures, or losses caused by your wallet approvals. Nothing excludes liability or rights that cannot lawfully be limited, including applicable consumer protections, fraud, or other non-excludable obligations.
No invented liability cap, mandatory arbitration provision, governing jurisdiction, or legal-entity representation is established by this draft.
13
Changes & contact
Terms may be revised as functionality or legal requirements change. Material revisions should be identified with an updated date and appropriate notice. Changes do not rewrite confirmed blockchain transactions or remove mandatory statutory rights.
Current public project contact: @p402chain on X. Do not send wallet secrets or sensitive legal documents through public replies. This public channel is not a substitute for the formal operator notice address, which remains to be supplied.
