Privacy Policy
How AudioPad handles data when you connect a wallet, launch a coin, or view public content.
Learn what information AudioPad processes, why it is needed, and what becomes public when you launch.
Controller and scope
This policy describes how data is processed when you use the AudioPad website and launch flow. For privacy questions, email audiopad.support@gmail.com.
Read this policy together with the Terms of Service. The current service does not require an account, legal name, or email address to launch a coin.
Data we process
The data processed depends on the features you use. It may include:
- Your public wallet address, network, launch choices, transaction signature, mint address, and verification status.
- The name, ticker, description, social links, image, optional audio, metadata, and technical asset information you submit.
- Your IP address and network-request information as needed by hosting providers or abuse-prevention systems. AudioPad creates an HMAC identifier for rate limiting and stores the derived value, rather than a raw IP address, in its rate-limit table.
- Theme and sidebar preferences stored in your browser’s localStorage.
Why we process data
AudioPad processes data as needed to prepare and verify a launch you request, display confirmed coins, provide search and audio playback, protect the service and apply rate limits, and maintain the service.
Wallet addresses and transaction details are used to build and verify transactions. AudioPad does not ask for private keys or recovery phrases. The current app does not include advertising analytics or marketing profiles.
The applicable legal basis depends on the data and law involved. It may include providing a requested feature, complying with a legal obligation, protecting the service, or consent where required. The controller must review and confirm the legal bases before this policy takes effect.
Information that becomes public
If you launch a coin, information included in its metadata, image, audio, and transaction may be visible to the public. AudioPad displays launches it has verified and uses the mint address as the coin identifier.
Final assets may be published through IPFS and gateways. Blockchain transactions are public, and distributed content may be copied or saved by others. Removing content from AudioPad does not remove blockchain records or guarantee that every IPFS or cached copy is erased.
Service providers that receive data
To provide the service, data may be processed by providers that support its infrastructure or transactions. Integrations present in the current code include Vercel hosting, Cloudflare R2 for temporary audio files, Filebase and IPFS gateways for public assets, the wallet you choose, Solana and the configured RPC provider, Pump.fun, and DEX Screener for market data.
These providers may receive technical information needed to handle your connection. Wallets, networks, and other third-party services have their own privacy policies. The operator must confirm the final subprocessor list, processing locations, and their retention settings before publication.
Storage and uploaded files
Images are uploaded directly to Filebase for publication to IPFS when reachable. If the browser cannot reach Filebase, the image is uploaded temporarily to Cloudflare R2 and a worker publishes it to IPFS. Launch metadata is published through Filebase. Audio is uploaded to Cloudflare R2 through a temporary link, processed by a worker, and then the final version is published to IPFS. After successful processing, the worker requests deletion of temporary files.
The current code does not define a retention period that can be promised for failed or abandoned audio uploads. A retention and cleanup schedule for those cases must be set before production. AudioPad cannot guarantee deletion of every network copy of public files on IPFS.
Browser storage and technical logs
The app stores your theme choice and sidebar state in localStorage so those preferences persist on later visits. No advertising or third-party behavioral analytics SDK was found in the site implementation reviewed for this draft.
Hosting and infrastructure providers may generate technical logs, such as IP address, request time, browser, and response status, for operations and security. Those providers and deployment settings determine log configuration and retention; the exact details must be confirmed before this policy takes effect.
Retention
Launch records are needed for AudioPad to verify and display coins. AudioPad does not currently publish fixed retention periods for successful launch records, abandoned drafts, security records, or hosting logs. Temporary audio uploads are requested to be deleted after successful processing; other provider logs follow the applicable provider and deployment settings.
Public data on a blockchain, IPFS, gateways, or copies held by other users may remain available even if an AudioPad record is deleted.
Security and your rights
AudioPad uses rate limits and access controls to help protect the service, but digital transmission and storage cannot be guaranteed risk-free. Do not share private keys, recovery phrases, or secret credentials.
Depending on applicable law, you may request access to, a copy of, correction or deletion of your personal data, restriction of processing, or object to processing. Contact audiopad.support@gmail.com. We may need to verify that a request is yours, but will never ask for your recovery phrase or private key.
A deletion request may be limited by legal obligations, security needs, launch verification, or the public and persistent nature of blockchain and IPFS data. Applicable rights and exceptions depend on relevant law.
Children, data transfers, and updates
AudioPad is not intended for children. If you believe a child’s personal data was submitted without an appropriate basis, contact the privacy contact once official contact details are published.
Infrastructure providers may process data in the countries where they operate. The operator must confirm transfer locations, safeguards, and the subprocessor list before this policy takes effect.
AudioPad may update this policy when data-processing practices change. The current version will be published on this page.