Your information at Curialy
We need some information to fulfill and support your order. We do not claim that no personal information is stored.
Recent orders on this device
This browser remembers up to five orders you create or open, including their private codes, plan summaries, totals, last-known statuses and timestamps. Entries stop appearing 200 days after they were last opened. We do not store your X username, wallet address or transaction hash in this recent-order list. Use Forget or Forget all on the Track order page to remove local entries; this does not delete server records. Anyone using this browser can open remembered order links, so forget them on shared devices. If browser storage is unavailable, keep your order code yourself.
Optional Telegram order updates
If you send an order code to @Curialybot or use Get updates on Telegram, we store your Telegram chat ID, language and the order you follow so the bot can send status messages. Those messages include the code, plan, total and payment guidance, but not your X username. Anyone with the private order code can follow it. Telegram processes messages under its own policies. Send /stop to delete your follow records and stop updates; blocking the bot removes them when delivery fails. No subscription is created just by opening the website.
Order information we keep
Our order database stores the X username you enter, selected products and durations, price, order code, payment network and coin, destination address, quoted amount, transaction hash, status history, timestamps, your checkout confirmations, and support/admin notes. We use these records for fulfillment, payment checking, receipts, support, and resolving disputes.
Who can see order details
The operator can access orders through the admin system. When a transfer hash is submitted, order information and a receipt can be sent to our configured operator chat on Telegram. Telegram handles those messages under its own policies. If you contact support, we also receive the information you send there. Subscription fulfillment requires using the designated X account information with X.
Keep your order code private
Anyone who has your order code can use the existing lookup and receipt tools to access order information. Treat the code and payment link as private access details. Do not post them publicly or share an unredacted receipt. Renewal lookup requires an order code; it does not offer a public search by X handle.
Browser preferences and cookies
The site stores language and theme preferences in your browser. A language-preference cookie remembers your choice. The admin login uses a secure session cookie and server-side session record; customers do not need an account or that cookie to shop.
Visit statistics
To understand how many people visit and which countries they come from, each page you open sends Curialy a short anonymous record: the page (payment links and referral codes are grouped, never recorded individually), the referring website's domain, any campaign tags in the link, your browser, operating system and device type, your screen width, the site and browser language, and how long the page was visible. The country is looked up from your IP address when the record arrives (using DB-IP data on our own server). Your IP address is not stored. To count a visitor once per day, we keep a one-way code made from your IP address, browser identifier and a random daily key. The key is deleted after about a day, so the code cannot later be linked back to you. This uses no cookies or browser storage and no third-party analytics service. Totals for visits before 11 October 2026, when this counting began, were rebuilt from the server's connection logs using the same rules; no IP address, browser identifier or full link was copied into these statistics. Records are deleted after about 13 months, and only the operator can see the totals.
Connection logs and blockchain records
Our hosting server may log requests, including IP addresses and requested URLs. The API uses IP-based request counters to limit abuse; administrator sessions also record connection information. Cryptocurrency transfers are recorded on public blockchains and cannot be erased by Curialy. Avoid putting sensitive information in URLs.
Renewal-helper dates
The expiry date you type in the renewal helper stays in the current page and is not sent to Curialy or saved as a server reminder. The downloadable calendar file is generated in your browser and contains no order code, X username, or payment details. Importing it into a calendar puts that event under your calendar provider’s control.
Retention and requests
The current order system does not automatically delete order history on a fixed schedule. Contact support if you want to review or correct your order details or request deletion. We will explain what can be changed or removed and whether payment, support, dispute, or legal recordkeeping requires some records to remain. This is not a promise that blockchain records can be deleted.
Affiliate accounts and referral attribution
Affiliate accounts store your chosen Curialy username, a one-way password hash, public promo code, hashed session records, referral earnings, and withdrawal amounts, networks, coins, destination addresses and status history. Your account password is sent securely to authenticate and is never stored as readable text; do not send it to support. Your browser remembers a validated referral code for up to 30 days, not your affiliate password. A later valid code replaces the earlier one before the payment quote is prepared. The order stores the applied code and exact discount. Referrers see, for orders that used their code, the plan, status, discount, reward amount and the hour the order was placed and delivered, not buyer identities, order codes, receipts or transaction hashes. When someone opens a referral link, Curialy adds one to a daily count for that code; the count stores no IP address, device, cookie or order link, and repeat opens are filtered with a short-lived keyed hash that cannot be read back as an address. Withdrawal requests are shared with the operator via Telegram for manual review/payment. Affiliate sessions use an HttpOnly cookie, not the public promo code. Keep your login private; sharing a promo code does not grant wallet access.
Orders placed through a reseller
If you buy through a reseller's Telegram bot or website, that reseller sends Curialy your X username, plan, their own order reference and your account confirmations, and can see the order code, status, payment network, coin, amount, transaction hash, status notes and receipt for orders they created. The reseller's own privacy practices apply to anything you share with them directly. Curialy does not give resellers access to other customers' orders. Resellers authenticate with secret API keys stored only as one-way hashes; order status updates sent to a reseller's webhook are signed so they cannot be forged. Reseller applications (business name, sales channel and contact) are shared with the operator via Telegram for manual review.
Information we never need
Do not send X passwords, wallet seed phrases, private keys, recovery codes, or payment-card details. Use your Curialy password only in the affiliate login/signup form, never in support messages. Curialy uses manual crypto transfers and never needs to connect to your wallet. For privacy questions, contact @Curialy on Telegram.