Privacy policy
This notice explains what data RockTheCoin uses, why it is needed and what choices you have. It covers the public website, creators and tools. RockTheCoin’s service provider is responsible for this service’s processing.
Updated
Your privacy choices
Optional usage statistics help us understand where creation flows work or fail. You can use the creators and tools with statistics declined.
Your choice is saved for up to six months. Declining stops new browser statistics, removes the current session’s attempt summaries and detaches its analytics links from checkout records. Earlier grouped counters remain. Wallet connections, pending transactions and essential service records are kept.
1. Data used by the service
When you visit, our hosting and security infrastructure receives technical request data, such as your IP address, request time, requested URL, browser information, referrer and response status. Cloudflare sits in front of the website for delivery and security.
When you connect or use a wallet, the service can receive the public accounts you approve, the network, wallet connection details, transaction hashes, public signatures and the transaction information needed to prepare or verify your chosen action. Some native-chain recovery flows retain the original publicly signed transaction. RockTheCoin does not ask for your seed phrase or wallet private key.
Creating or managing an asset can store the options you submit, its name and symbol, artwork, description, metadata, recipients, supply and permissions, the fee and rate snapshot, and the transaction’s status. A saved review does not prove that a transaction was sent or succeeded.
If you contact the operator, the message and reply details are used to handle your request. Provide only what is relevant. Never send a seed phrase or private key.
2. Purposes and legal bases
The service uses checkout and wallet data to prepare the action you request, quote its cost, verify the original transaction, deliver metadata and provide recovery or support. Where the GDPR applies, the basis is taking steps at your request or performing the service contract, Article 6(1)(b).
Security logs, request limits and fraud or abuse prevention support the legitimate interests of keeping the service reliable and protecting users, Article 6(1)(f). Records required by applicable tax, accounting or other laws are processed under Article 6(1)(c).
Optional browser usage statistics use consent, Article 6(1)(a), where the GDPR applies. They stay off until you allow them. Declining or withdrawing does not prevent creation or management. Essential checkout records and their verification continue independently of this choice.
We do not use these statistics for advertising profiles or automated decisions with legal or similarly significant effects. We do not sell personal information.
3. Optional usage statistics
With permission, a small attempt summary records milestones such as starting a form, connecting a wallet, preparing a review and requesting approval. Server checks supply saved-reference and verified-outcome information. The summary includes the chain, service, selected template, wallet app and connection method, mobile or desktop category, language and broad traffic source.
The analytics tables do not copy your form contents, full referrer URLs, campaign parameter values, raw IP address, full browser user agent or arbitrary error payloads. Attempt summaries use a random identifier and a hash of the checkout session; a checkout can link that summary to its existing service record. These summaries are therefore not treated as anonymous while they can be linked.
Identical issues are grouped with a standard description and affected-attempt count. Daily counters contain fixed categories without attempt IDs or wallet addresses. Statistics are sent at milestone changes, not as a record of every click or keystroke.
4. Cookies and browser storage
The secure rtc_session cookie supports the current checkout session and request protection. It is a session cookie; browser session-restore settings can affect how long it remains. The rtc_language cookie remembers the selected language for up to one year. The rtc_statistics cookie stores your statistics choice, notice version and timestamp for up to six months.
Local browser storage can remember your theme, selected network, public wallet account choices and wallet connection sessions. Transaction references, public signed approvals, distribution progress and drafts may use tab session storage so you can recover an interrupted action. These functional records are separate from optional statistics.
Optional statistics use a small browser summary and broad source category only after permission. A resumed attempt or source category is reused within a 30-minute visit window. Tab storage may remain until the tab or its restored session is closed; the time window limits reuse rather than promising immediate browser deletion.
You can disconnect wallets, remove site permissions in the wallet and clear site storage in your browser. Clearing recovery data does not cancel an on-chain transaction or revoke a token allowance. Check any pending transaction first. Wallet providers and Cloudflare may use their own functional storage under their notices.
5. Providers, networks and public data
When automatic publishing is enabled, requesting a creation or mint review sends uploaded artwork and generated metadata from our server to Pinata for public IPFS storage before wallet approval. This includes any public creator addresses or links you choose to put in that metadata. A cancelled review does not retract content already published. Public IPFS copies can remain outside our control.
Hosting and technical service providers support website delivery and security. Configured third-party RPC endpoints receive the requests needed to read network state or relay approved transactions. Depending on the action, this can include public wallet addresses, asset addresses and transaction data. The service does not operate its own blockchain nodes.
Choosing a wallet connection can involve that wallet, WalletConnect/Reown relay or verification services, MetaMask connection infrastructure, or a Solflare connector. Those providers can receive connection and request metadata, including an IP address when your browser contacts them. Their own processing is governed by their privacy notices. Optional SDK telemetry is disabled in our WalletConnect and MetaMask integrations.
Kraken, CoinGecko, Binance and Frankfurter provide server-side rate references. The rate requests do not need a customer wallet address. If you request public contract source verification, Etherscan or Sourcify receives the relevant public contract and source information.
Approved blockchain transactions and the data you put on chain can be publicly readable worldwide. Hosted artwork and metadata URLs, content published to public IPFS, and project pages you choose to publish are public too. Other people can copy or index them. We cannot erase confirmed records from a decentralized blockchain.
Some providers and network participants process data outside your country or the EEA. We do not promise local-only processing. Applicable transfer requirements and provider arrangements depend on the operator and provider; contact the operator for details and any relevant safeguards.
6. Retention
Attempt summaries are kept for at most 14 days with a cap of 10,000 rows. Grouped issues are kept for 30 days after last seen, capped at 1,000 groups. New entries can replace older slots at capacity. Daily counters are kept for 12 months. Cleanup runs daily.
Request-limit records are cleaned after two days. Routine website and PHP logs are configured for daily rotation with seven archived rotations plus the current log. Specific incident or legal-claim records may need longer retention.
Checkout, transaction, public-approval and asset records can be needed for verification, recovery, financial records and ongoing metadata delivery. Unsubmitted reviews are distinguished from successful transactions. These service records are not automatically removed by analytics cleanup. We keep them according to those purposes and applicable legal retention requirements, then delete or minimize data that is no longer needed.
A deletion request can be limited by legal obligations, security evidence, another person’s rights or the need to deliver metadata for an existing asset. Public blockchain copies are outside our control. Relevant requests also need to account for recovery copies; deletion is not a promise that every historic backup or third-party copy changes immediately.
7. Your rights and requests
Subject to applicable law, you can ask for access, correction, deletion, restriction or a portable copy of your data. You can object to processing based on legitimate interests and withdraw consent for future optional statistics. Withdrawal does not make earlier consent-based processing unlawful.
Send privacy requests to the service provider using its public privacy contact. We may need proportionate proof that a request concerns your wallet or records. We will not ask for your seed phrase or private key. You may complain to the competent data protection authority; in the EEA, this can be the authority where you live, work or believe an infringement occurred.
Technical request data is needed to deliver and protect the website. Wallet and transaction information is needed for the action you request; without it, that action cannot be prepared or verified. Optional statistics can be declined. We do not use a customer credit-scoring or automated legal-decision system.
8. Changes to this notice
The date at the top identifies this version. We update the notice when service processing changes and provide any notice or new consent required by applicable law. New optional processing is not authorized merely because you previously used the website.