Terms of Use and Privacy
These terms describe how the storefront, manual payments and feedback form work. They also explain what to expect from a product marked as a beta and what information the site and its service providers handle. Review the applicable offer, delivery method and device requirements before sending funds.
1. Offers and scope
The storefront displays its own offer, price and calculator. A price applies to the edition or materials identified in that offer. It provides no automatic entitlement to optional products, subscriptions, later editions, extras or future updates. Product requirements, formats, region restrictions and access instructions depend on the specific offer. Check any of these details that matters to you before payment.
The crossed-out amount is a reference amount rather than a statement about the price previously paid by customers. The current amount payable to the recipient appears in the payment window, denominated in the selected asset. Opening the payment window, copying an address and checking an acknowledgment box are local actions and do not move funds.
Any reference to a beta applies to the product or build delivered under the offer when identified as in development. A beta disclosure does not describe a third party’s release status. Use any delivered materials only as permitted by their applicable licence and rules.
2. Beta releases and incomplete builds
A beta may be offered at a reduced price because it is unfinished. Its interface, features, performance, requirements and file formats can change as development progresses. A reduced price does not set a release date, commit to a particular final feature set or guarantee that an issue in one build will be corrected in the next build.
- Stability. You may encounter installation failures, crashes, incomplete flows, incorrectly rendered screens, slowdowns, interrupted downloads, saves that fail or features that work only intermittently.
- Performance. Performance depends on the device, drivers, storage, memory, network conditions, configuration and other running programs. Frame rates, loading times and resource use can differ materially across devices and builds.
- Compatibility. Settings, saves, plug-ins and user-created files may not carry over between builds. Keep a separate copy of anything hard to recover, and test a new build with nonessential data where appropriate.
- Changes. Features, settings and minimum requirements can be modified, postponed or removed. Development, verification and distribution follow their own schedules. An acknowledgment that a product is in beta does not waive rights that apply by law.
When describing a bug, include the version, device or relevant environment, what you expected to happen, and steps that reproduce the problem. Check screenshots and logs for unrelated personal information, private access links or secrets before you share them.
3. Payment calculations and manual transfers
Use the asset, network and exact amount shown under “Exact amount to send”. Network costs are separate. The base fee shown on the page is a Solana network figure, and the dollar total is a calculation based on the displayed exchange rate. A wallet or exchange can charge its own withdrawal fee, priority fee or token-account setup cost. Those amounts are determined outside the storefront.
On a withdrawal screen, a service may subtract its fee from the amount you enter. Review the amount the recipient will receive, and check that it still equals the order amount. A transfer on a different network, using a different token or sent to a different address cannot be treated as the intended payment merely because its estimated dollar value is similar.
The site does not connect to wallets, sign transactions, charge a card or confirm receipt automatically. The user reviews and authorises a transfer in their own app. Market rates may change between a quote and a transfer. For SOL amounts, refresh the quote if it is outdated and verify the quantity shown before confirmation. Keep the transaction identifier and avoid sending a duplicate while the first transaction is still pending.
4. Underpayments, overpayments and errors
An incorrect amount can delay or prevent matching the transfer to the intended order. Sending too little does not automatically complete the order. Sending extra does not create automatic credit, a new order or an automatic refund. Review is manual. Do not send a second payment, a top-up or a supposed recovery fee until you have verified the first transfer and received instructions applicable to the case.
Report a discrepancy under Feedback → Payment. Include the public transaction identifier, network, asset, expected amount and amount actually sent. A transaction identifier can be enough to look up an on-chain transfer. Do not include a password, recovery phrase, private key, one-time code or login credential. If the transfer originated at an exchange, check its withdrawal history for the final net amount and public transaction identifier.
The operator cannot reverse a confirmed blockchain transfer through the storefront. Recovery depends on whether the recipient controls the destination, whether the transfer can be attributed, and whether the relevant network and asset are supported. Selecting a different network or deliberately transferring a different amount does not oblige the recipient to treat it as an exact payment. The operator is not responsible for a discrepancy caused solely by an amount, address, asset or network entered incorrectly by the sender, to the extent permitted by law. Mandatory rights and any applicable right to a refund or correction remain in force.
5. Delivery and file reports
Delivery is handled separately from the storefront. A transfer appearing in a wallet or on a blockchain explorer does not trigger an automatic download. Delivery can include a file, access instructions or another method described in the offer. Keep any relevant delivery instructions and public transaction reference until the matter is resolved.
When an offer includes a file report, the report corresponds to a particular file at the time it was analysed. Compare the file’s SHA-256 hash with the report’s hash. Different versions can have different hashes and different results. A report describes the checks that ran and their results. It does not establish that every configuration or use of the file is safe.
6. Feedback, bug reports and usability
The Feedback form accepts a topic and a message. Use it for bugs, site usability, payment discrepancies or other comments. Keep the message relevant to the subject and leave out sensitive credentials and third-party personal information. Submitting feedback does not establish a response deadline, issue a refund, change a transaction or confirm an order.
When the site is deployed with Netlify Forms enabled, Netlify handles the submission and the site operator can review it. The form shows a sent confirmation after a successful response. On a host without form delivery, the form can save the most recent entry on the current device and offer to copy it. That state is labelled as saved on the device. Clearing browser storage removes the local copy.
7. Technical data, language and storage
Browsing the storefront does not require an account or a payment credential. The hosting provider can receive technical request data such as IP address, browser information, requested resource, timestamp and network information. This can be used for serving content, diagnosing errors and protecting the hosting service.
The storefront can use your browser language and an approximate country lookup through api.country.is to choose a language. The lookup provider receives technical request data, including the IP address used to estimate the country. The site does not request GPS or use the lookup for payment decisions. A manual language choice is saved in browser storage, if available, and takes priority over the automatic choice.
The rate calculator sends a request to Coinbase for SOL/USD pricing. The request contains the quoted pair and ordinary connection data. It does not contain the wallet address shown on the page, the feedback text or a transaction hash. Providers determine their own retention and security practices. A submitted feedback message and its topic may be kept for review in the Netlify account when form delivery is enabled.
The site can write an address or feedback message to the clipboard after a copy action. It does not read unrelated clipboard contents. The storefront does not maintain a server-side record of agreement checkboxes. Browser caches and local storage are controlled by the browser and can be cleared there. Blockchain transaction data may be publicly visible and cannot be erased by deleting local storage or sending a privacy request.
8. Security, external services and rights
Use trusted address sources, verify the full destination shown by your wallet, and check links and files before opening them. The name of an external service does not imply that it operates or endorses the storefront. Wallets, exchanges, hosting services, quote providers and scanning tools are governed by their own terms and may have different availability, fees and privacy practices.
Where applicable, you can request access to, correction of or deletion of personal information held in relation to a feedback entry. Submit a request through the channel available for the issue and provide only information needed to identify the entry. Required retention, platform limitations and public blockchain records can affect what can be deleted. These terms do not limit mandatory rights.
Review the current terms when making a new transfer. Third-party names, files and images remain subject to their respective owners’ rights. A purchase grants only the rights described in the applicable offer or licence.