1. Wallet and token information
You can browse CreateSol without providing an email address or creating a password account. When you connect a wallet, the application receives the public account information shared by your wallet, including its address.
When you prepare or submit a launch, CreateSol stores the information needed to prepare the transaction, verify its result and display your token.
- The creator wallet, token address and protocol pool address.
- The token name, symbol, description, image link and any social links you supply.
- The supply, initial purchase amount, platform fees and launch status.
- Prepared transactions, approved signed transactions and transaction signatures used for submission and confirmation.
- Creation and confirmation times.
Wallet and transaction records can identify or relate to a person even though an address does not directly show a name. Token information and confirmed transactions are public on Solana.
2. How this information is used
We use wallet and launch information to provide the token creation service, calculate and show fees, submit the transaction you approve, confirm launches, handle retries and answer service questions.
Essential session information also helps protect requests and limit repeated preparation attempts. Authorized management actions produce audit records containing the administrator wallet, action and time.
When you email support, your email address and the information you choose to send are used to respond to that request. Avoid sending unrelated personal information.
3. IP addresses and browser information
The token creation application does not save your IP address or browser identity as fields in its launch database. Optional Google Analytics can be enabled by the site administrator. It loads only after you allow analytics. CreateSol does not add browser fingerprinting or advertising tags to the launch workflow.
Your browser still sends technical information when it requests a website. The web server's current access logging can record an IP address, request time, page or URL, browser user-agent and referring page. Server error logs may also include request details when an error occurs.
These technical logs are separate from the launch database and can be used for troubleshooting and service operation. We cannot promise that no IP address or browser information is recorded by the hosting infrastructure or by an external service you use.
4. Essential cookies and browser storage
CreateSol uses an essential session cookie named CreateSol to protect requests and support the local session. Session data can include request protection tokens, recent preparation times and temporary image publication references. An administrator session also holds sign-in state.
The browser stores pending launch, rewards claim and rewards activation references and their signed transactions in session storage so that a launch can be checked again in the same tab. The pending record is removed from that storage after the application confirms a final result.
Browser storage and cookies can be cleared through browser settings. Doing so while a launch is pending may remove the convenient resume option. It does not reverse an already submitted transaction.
Optional Google Analytics
If enabled by CreateSol, Google Analytics helps us understand visits, page usage and traffic patterns. You can choose Allow analytics or Decline in the banner. The Google tag is not loaded before you allow it, and declining does not restrict token creation, wallet connection or reward claims.
After permission, Google may process analytics identifiers, visited pages, device and browser information, network request information and approximate location under its own policies. The connection to Google necessarily exposes technical connection data to Google. These records are separate from the CreateSol launch database.
The integration sends a simplified page address and page title instead of the full URL query string. CreateSol does not add wallet addresses, token contract addresses, recovery phrases, transaction contents or form values as analytics event parameters. Advertising storage, advertising personalization and Google Signals are disabled by this integration. Additional measurement settings in the Google property are controlled by the site administrator.
Your analytics choice is saved in local browser storage for up to 180 days. If you allow analytics, Google may set cookies such as _ga and _ga_*. Use Cookie preferences in the footer to change your choice. Declining stops this integration's future analytics collection and attempts to remove its accessible Google Analytics cookies; it does not erase data already processed by Google. Browser Do Not Track and Global Privacy Control opt-outs are respected by this integration.
Analytics reports are accessed by CreateSol through its Google Analytics account. Retention and other property settings are controlled in that account. Read Google's Privacy Policy for information about Google's processing.
5. Solana, wallets and external providers
Wallet software such as Phantom handles the connection and signing prompts under its own privacy policy. CreateSol sends the transaction and account information needed for blockchain operations to the configured Solana RPC provider. Solana and Raydium process the launch on-chain.
Token images, descriptions and supplied links are published through Pinata to IPFS. Published metadata may be public even if you close the review before signing the launch. Other people or services can copy or retain public IPFS content.
When your browser loads an image from an external gateway, opens a social link, uses a blockchain explorer or sends an email, that external provider receives the request and may collect its own technical data. Providers may operate in other countries and apply their own privacy practices.
Information is shared with these services as needed to perform the action you request. Information may also need to be disclosed where required by applicable law.
6. What becomes public
A token page can be opened by someone with its direct link. Your public token information can also be found through blockchain explorers and other services. CreateSol does not publish a general token discovery feed on its homepage.
Connecting a wallet does not make the blockchain private. Public wallet addresses, transfers and token creation transactions can be viewed independently of CreateSol.
7. Retention and your requests
Public reward transaction history may be indexed from on-chain accounts and cached to display verified claims and historical totals. Launch and transaction records are retained to operate the service, verify completed launches, handle pending transactions, resolve support requests and maintain operational records. There is currently no automatic deletion schedule for the launch database. Retention of hosting and email logs depends on the systems used.
Contact [email protected] to ask about your information or request access, correction or deletion where applicable. We may need a safe way to verify that a request relates to you. We will never ask for your private key or recovery phrase for this purpose.
Requests are considered subject to applicable law and any required record retention. Data already recorded on Solana cannot be deleted by CreateSol, and public IPFS copies may remain accessible outside our control.
8. Contact and updates
Privacy questions for CreateSol can be sent to [email protected]. If the service or its data handling changes, this page should be updated and the date revised to reflect the new version.
Contact us