Privacy overview for SolCreate

This page expands on privacy overview for solcreate with more context than the live tool screens. It is meant to answer common questions, improve trust and give users a clearer understanding of how the SolCreate product is structured.

Content pages like this also support crawling and internal site architecture. They help search engines connect the core tools with the broader product information that users expect from a serious launch platform.

From here, users can continue into the main product flow via Contact support or move into Read the FAQ.

Keeping these pages closely linked to the live tools makes the product easier to navigate for people and easier to understand for crawlers. That is especially useful for a site that combines token creation, liquidity operations and burn workflows.

This privacy policy and data overview is intended to give users a practical explanation of what information appears in the product and what becomes public on-chain.

When you connect a wallet, the app can access the public wallet address needed to prepare or send the requested Solana transactions.

When you use token creation, liquidity or burn features, the app may process public on-chain identifiers such as mint addresses, associated token accounts, pool addresses and transaction signatures.

If you use the token image or metadata upload flow, the content you submit may be processed by the storage or pinning services configured for the deployment.

Only upload content you have the right to publish, especially because token metadata and blockchain-linked storage can be difficult to reverse once used in a live launch.

Solana transactions and many token-related records are publicly visible on-chain. That means wallet addresses, token mints, pool addresses and transaction signatures may be visible to others through explorers and infrastructure providers.

SolCreate cannot make public blockchain records private once a user confirms an on-chain transaction.

Depending on the live deployment, SolCreate may rely on RPC providers, hosting infrastructure and storage providers needed to deliver wallet interactions, metadata uploads and page hosting.

Those providers may process technical request data needed to serve the application. Review your configured vendors and update this page if the production stack changes.

• Do not enter a seed phrase into the app
• Do not share private keys through support or contact channels
• Do not upload sensitive personal information as token metadata

Because privacy details depend on the exact production setup, this privacy policy and data overview should be reviewed and updated whenever you change storage vendors, infrastructure providers, analytics tools or support workflows.