Scope of explanation
This page explains the data involved in quotes, order creation, status queries, on-chain verification, and fee refunds according to FeilongEX's current operating methods. The periods below apply only to records that FeilongEX can control; data already written to the public blockchain is retained according to the corresponding network rules and cannot be deleted by FeilongEX.
FeilongEX provides exchanges pursuant to an exclusive white-label service contract and bears contractual responsibility for service performance. The following transaction and technical data processing does not constitute identity verification and will not change the guarantee that every order is 100% No KYC throughout.
This site does not make a "zero logs" claim. For more complete rights, purposes and data terms, see Privacy notice and Terms of service.
Data processing details
This table can scroll horizontally.
| Data or record | Use | Current retention method |
|---|---|---|
| Quote parameters | Asset, network, mode, send amount, and estimated receive amount, used to generate quotes and fix the current conditions. FeilongEX processes these parameters according to the boundaries on this page. | Unsubmitted pending quotes are retained for up to 24 hours; all quote records are retained for up to 30 days. Deletion is triggered by subsequent requests and is not completed at the instant of expiry. |
| EUR reference price identifier | FeilongEX uses asset, network, token contract, or market identifiers to obtain EUR reference prices; it does not use user addresses, order IDs, or browser credentials. | Individual prices are usually reused in server memory for no more than 20 seconds; currency identifier lists may be cached for 6 hours. Price bases may also be saved with quotes or orders. |
| Address, Memo / Tag, and refund information | Used to check format and network, create orders, and process payments or refunds for which FeilongEX is responsible. | Regular creation records are retained for up to 30 days; orders still needed for fulfillment or subsequent processing continue to be retained during processing, and after closure are handled according to applicable obligations. |
| Source IP and request frequency | Used to limit abnormal requests. When creating an order, the source IP is used for regional eligibility and checks of address, transaction, and request characteristics without collecting identity documents; these technical checks do not constitute KYC. | Rate-limiting records are marked to expire after approximately 2 minutes, and cleanup is triggered by subsequent requests. FeilongEX handles technical logs according to published data retention rules. |
| Necessary cookies and local records | A one-day session cookie associates quotes; a one-year random attribution cookie and its server-side SHA-256 hash are used for attribution of some orders. Pending recovery IDs are stored in sessionStorage, and exchange IDs of recent refund applications are stored in localStorage. | Session cookies last up to 1 days; browser attribution cookies last up to 1 year. sessionStorage is cleared when the tab session ends or after secure recovery; localStorage records are cleared by the user or site functionality. |
| On-chain payment evidence | Transaction hash, address, amount, block, number of confirmations, and verification time, used by FeilongEX to verify actual deposit and final payment. | Payment evidence still needed for fulfillment or subsequent processing continues to be retained during processing, and after closure is handled according to applicable obligations. Public blockchain records are not controlled by FeilongEX. |
| Fee refund applications and notifications | Order snapshot, fee basis, USDT amount, Ethereum address, and processing status, used by FeilongEX to verify eligibility, complete payment, and prevent duplicates. | No fixed automatic deletion period is currently published; relevant records are retained for the period needed to complete refunds and subsequent verification. |
| Technical access logs | FeilongEX may process source IP, request time, path, and fault information for operation, security, and troubleshooting. | Specific content and periods follow the retention rules published by FeilongEX. FeilongEX makes no "zero logs" claim. |
FeilongEX data use boundaries
This table can scroll horizontally.
| Functional scenario | Data processed | Boundaries |
|---|---|---|
| Quotes and orders | Currency directory queries; where applicable, quote parameters, amount, address, Memo / Tag, refund information, and the source IP at creation time. | Only the information needed to complete the current function is transmitted; an address format check by itself does not create an order. |
| EUR reference price | Asset, market, network, or token contract identifier. | EUR price queries do not send the user's amount, address, order number, or browser credentials. |
| On-chain verification | Verify the required address, transaction hash, block, or RPC parameters. | Used to view the public record of the corresponding network or the configured Monero proof; no wallet transfer is performed. |
| Fee refund notice | Depending on the event, may include the order number, asset, network, amount, status, payment hash, and the full USDT Ethereum refund address. | The notice is used only to record the progress of the refund completed by FeilongEX, and is not a channel for customer support or security issue reports. |
| Site operation | Process requests, store the above business records and possibly technical access logs. | The site frontend currently has no advertising tracking or analytics scripts. |
Order numbers and public on-chain data
Some orders can be queried with the order number; some orders also require the attribution credential of the original browser. The fee refund entry point allows summary queries and applications using the FeilongEX exchange number, so the number should be kept safe as a private link with operational capability. The query page is not included in search indexing, which does not mean it is password-protected.
Blockchain addresses, transaction hashes, amounts, and times are usually publicly visible and may also be subject to correlation analysis. FeilongEX cannot delete public blockchain records.
What FeilongEX will not ask for
Every FeilongEX exchange, regardless of amount, does not require a customer account, email, or KYC materials at any stage, and does not ask for identity documents, facial verification, proof of address, proof of funds, private keys, seed phrases, wallet passwords, exchange login credentials, remote control permissions, or wallet transfer authorization. No KYC does not mean anonymity; on-chain records, necessary technical logs, regional eligibility, and applicable laws still apply, but they do not constitute a KYC exception.
FAQ
Does FeilongEX promise "zero logs"?
No. FeilongEX requires necessary records to run exchanges, restore creation results, verify payments, prevent duplicate applications, and limit abnormal requests.
What happens when cookies and local storage are cleared?
You can clear recent exchange IDs and site data, but after clearing the attribution cookie, some orders may no longer be provable as yours from that browser. This does not delete blockchain records that are already public.
Does no account and no KYC equal anonymity?
No. A dedicated contract guarantees that every FeilongEX order is 100% No KYC throughout, regardless of amount, but on-chain addresses, transaction hashes, amounts, and times are usually publicly visible and may also be subject to correlation analysis.