perppadPrivacy Policy
What perppad processes, what becomes public, and how to manage your local data.
This page describes the service and its current practices. Operator identification and jurisdiction-specific legal review remain outstanding; publication is not a claim of regulatory approval.
1 / Service and contact
This notice describes data processing by the perppad interface at perppad.fund. Our published contact is @perppadfund on X. Use it to request a private contact route for data questions; do not post identity documents or other sensitive information publicly.
The legal identity of the data controller has not yet been published. This notice does not assert that operator-identification requirements have been completed.
2 / Data the app processes
| Category | Current use |
|---|---|
| Public wallet address | Sent to the application server to retrieve balances, positions and lender records and prepare requested transactions. |
| Transaction information | Wallet-approved transaction payloads, signatures, public account addresses and on-chain activity used for execution and status checks. |
| Token submissions | Names, tickers, descriptions, images, optional covers/videos and social links uploaded for token creation. |
| Market and chain data | Public token metadata, trades, reserves and holder information cached to display markets and charts. |
| Technical request information | Hosting and network services necessarily receive request information such as IP address and browser/network headers. Specific provider log retention requires confirmation. |
| Browser session values | Launch recovery mint, public lookup-table addresses and motion preferences in sessionStorage; wallet reconnect preferences and pending launch records in localStorage. |
The application does not ask for a seed phrase or private key. Wallet software handles signing. A public wallet address can still be personal data when associated with an identifiable person. Do not place personal or confidential information in public token fields.
3 / Purposes and legal bases
Data is used to provide requested wallet and token functions, display market information, recover interrupted launch setup, diagnose failures and protect the service. We have not added advertising analytics or first-party tracking-cookie code to the current application.
Pending legal review: the operator must confirm a lawful basis for each purpose. Depending on the circumstances, requested service processing may rely on performance of a contract, proportionate security processing on legitimate interests, required records on legal obligations, and optional nonessential processing on consent. These are proposed categories, not a claim that every basis already applies.
Refusing to connect a wallet still permits reading docs and browsing public information. Wallet-dependent actions need the public address and transaction data necessary to perform them.
4 / Providers and public disclosure
| Recipient or system | How data reaches it |
|---|---|
| Railway hosting | Receives requests to the deployed application and runs its server. Hosting infrastructure may process technical logs. |
| Configured Solana RPC provider | Receives blockchain queries and transaction submissions forwarded by the server. The application uses a configured Solana RPC service, including Helius. Its network matches the application’s network status. |
| Solana network | Confirmed transactions, accounts, addresses and related activity become publicly accessible. |
| perppad storage and IPFS upload providers | Token media is stored on persistent application hosting. Metadata may also be submitted to an IPFS upload provider and become publicly retrievable and replicated. |
| Wallet provider | Handles the connection and signing request under its own terms and privacy practices. |
| DexScreener / GeckoTerminal | May receive server-side market-data queries. An embedded DexScreener chart, when used, is loaded directly by your browser and may receive IP/device data and apply its own storage practices. |
| IPFS gateway | Your browser requests public token images or media through ipfs.io; that gateway receives the request and associated network information. |
Opening external social links or explorers sends you to third-party services governed by their own policies. Providers and public distributed networks may process data in other countries. The operator must confirm provider locations, contractual arrangements and any legally required international-transfer safeguards; this notice does not claim those checks are complete.
5 / Cookies, storage and retention
The current application uses browser sessionStorage for lastLaunchMint , perppad.launchTable.<wallet> and gravity-motion. These values normally last for the tab session, subject to browser restoration behavior. Clear site data to remove them; clearing the recovery mint does not delete a created token.
Creation form drafts and the active wallet connection are held in page memory. To recover an interrupted launch without repeating a purchase, perppad.pendingLaunch in localStorage stores the creator wallet address, mint, selected amounts, stage and already-signed transaction records. These records contain transaction signatures, not wallet private keys or recovery phrases. They are removed when the flow completes or an expired first stage is discarded. Clearing browser storage removes this recovery record; check on-chain confirmations before retrying. The browser also stores a perppad.wallet preference in localStorage to request trusted reconnection on return visits; it stores no private key or wallet signature. Uploaded token images, banners, videos and launch metadata are stored in persistent server storage. Metadata may also be copied to IPFS. Server files additionally cache resolved token metadata and observed trade history. Observed trade history is capped at 2,000 entries per market; the current metadata cache has no automatic time-based deletion policy.
No blanket “we store nothing” promise is made. Hosting, wallet and embedded third-party services may maintain their own logs or storage. The operator must establish and disclose retention periods for operational records and any support communications. Those periods are not yet confirmed.
Public blockchain records cannot ordinarily be erased by the operator. Removing a local cache or interface reference cannot ensure deletion from IPFS, gateways, indexers or other copies.
6 / Your choices and rights
Depending on applicable law, you may have rights to access, correct or erase personal data, restrict processing, object to certain processing, obtain portability and withdraw consent where processing relies on consent. These rights have conditions and exceptions; they do not promise deletion of immutable blockchain records.
Contact @perppadfund on X to initiate a request and arrange an appropriate private channel. Verification of a request should be proportionate and should never require your wallet seed phrase or private key. You may also have the right to complain to the relevant data-protection authority.
You can avoid optional public media and social-link submissions, disconnect your wallet, clear local site data and choose not to open third-party charts or links. Disconnecting does not remove earlier on-chain activity.
7 / Security and children
The app uses wallet signing and limits its server transaction/RPC interfaces. No system can guarantee absolute security. Public media and metadata must be treated as public information. Never send recovery phrases, private keys or confidential documents through token creation fields.
The service is for adults aged 18 or older and is not intended for children. Report suspected child data or other privacy concerns through the published contact.
8 / Changes
This notice was updated on 24 September 2026. Changes to hosting, embedded providers, analytics or data handling will be reflected here. Provider retention, international-transfer arrangements, lawful bases and operator identification remain subject to completion and legal review.