The contact email in this tab
Confirm one email address before usable payment instructions are shown. It is the only account-contact field; the standard checkout does not ask for a name, phone number, passport, identity-card scan, selfie or proof of address. No routine documentary KYC is performed at registration. Additional information may be required where applicable law requires it.
The current frontend keeps the confirmed email in this tab’s session storage, separate from the configuration and financial quote. It does not send the email to a backend, send a message, verify mailbox ownership or create an account. The address is not included in page URLs, payment QR codes, exchange-rate requests or frontend logging and analytics events.
You can correct the contact email without changing an active quote’s local reference, selected asset or network, receiving address, rate, totals or original expiry. While editing or without a valid confirmed contact, usable instructions are hidden. Cancelling the edit restores the previous confirmed contact and any still-valid quote. Confirming a replacement stores the current contact rather than an email history; it does not restart the quote’s hour.
Technical choices and quote storage
The configurator saves your plan, options, period, hostname and optional SSH public key in this tab’s session storage. A quote saves the confirmed configuration, selected asset and network, receiving address, rate, amount and timestamps. This lets a reload retain your choices and the original expiry. Changing the configuration or payment route invalidates its financial quote; correcting only the contact does not.
Hostnames and SSH public keys remain in browser session storage in the current frontend. They are not placed in URLs or sent to a checkout service. Never enter a private key, password or seed. Recognized private-key blocks are rejected before draft storage. Browser session storage normally lasts for the tab session; a browser’s session-restoration behavior can retain it across a restart.
Exchange rates and website access
Your browser requests public ticker data directly from Kraken. Kraken receives the connection’s IP address and ordinary request metadata. This request does not include your contact email, hostname, SSH public key, configuration, payment reference or receiving address. QR codes are generated in the browser and encode the receiving address only.
Your browser also requests website files from the server serving this site. Those connections expose ordinary network metadata to that server. The current site adds no advertising or analytics scripts. The support brief button copies text to your clipboard; it does not submit a support ticket. These frontend behaviors do not establish a no-logs policy for hosting or network providers.
Limited collection is not blanket anonymity
An email, hostname or SSH public-key comment can identify a person. Offshore operation and Monero support do not remove that possibility. Panama’s data-protection authority describes identifiable-person information as personal data and explains access, rectification, cancellation, opposition and portability rights. See ANTAI’s Law 81 guidance; the applicable conditions and legal exceptions must be considered for the actual processing.
A DMCA notice alone does not trigger automatic customer-data disclosure. We assess legal requests under the law applicable to the Panama-based operation and comply with legally binding process, including international procedures recognized in Panama. Read the legal-request policy and references.
Operator, contact and future service processing
The owner declares the operator to be based in Panama. The legal controller’s identity and dedicated privacy contact have not been supplied for publication. For now, use your existing contact with the owner for a privacy question. Server-country choices are Malaysia, Romania and Switzerland. A complete service notice must also identify processing purposes, legal bases, processors, backup countries, retention periods, international transfers and how applicable rights are exercised. Choosing a server country does not place every copy of your data there.
The current frontend has no connected account or invoice-registration service. When the developer connects those services, a contact email will need to be transmitted for the relevant quote and invoice request under the service’s disclosed processing rules. That future processing is not taking place through this page today, and a local email correction does not update a server-held account or invoice.