NEXORA
Launch AppPreview / Development
On this page

NEXORA — Privacy Policy

Document Version: v1.1

This Policy describes potential information handling in connection with NEXORA. It does not by itself identify a data controller or establish that a particular operator has implemented every activity described below.

This Privacy Policy applies to:

  • The NEXORA core application.

  • The official NEXORA-WEBSITE.

  • NEXORA frontend applications.

  • Smart contract interaction interfaces.

  • Related on-chain information and interaction services.

The current application is a Preview / Development build. The project materials available for this release do not identify a verified operating entity or data controller, production contract deployment, configured production RPC/data source, or deployed analytics service. The actual controller and processing activities, if any, depend on the service and infrastructure actually used and applicable law.

Blockchain data may be immutable, traceable, publicly accessible, and retained for extended periods.

The project is designed to minimize reliance on traditional centralized servers and to use smart contracts for specified core rules. The current static application does not include a server-side account system or database for core order execution; however, no production contract deployment or live blockchain operation is verified for this release. The frontend is designed for static distribution, potentially through IPFS or Arweave, but no such production deployment is verified.

However:

  1. Decentralization does not eliminate personal data processing.

  2. Blockchain transactions are generally publicly accessible.

  3. Wallet addresses may be linked to other identifying information through transaction activity.

  4. IPFS, Arweave, and similar systems may retain published content for extended periods.

  5. Hosting providers, gateways, RPC providers, wallets, browsers, and other infrastructure providers may process connection and access information if used.

  6. Frontend availability and contract execution are separate; an unavailable frontend does not by itself establish that a deployed contract has stopped operating.

Wallet addresses should not be considered inherently anonymous or impossible to identify.

If you connect a wallet or interact with a deployed smart contract, the following information may be generated or publicly recorded:

  • Public wallet addresses.

  • Blockchain networks and chain IDs.

  • Transaction hashes.

  • NXC order amounts and statuses.

  • Referral relationships and invitation codes.

  • Reward distribution records.

  • Automatic repurchase records.

  • NEX allocation eligibility and claim records.

  • Asset swap records.

  • Smart contract interaction records.

No live NEXORA contract interaction or corresponding production records are verified for the current application. If such information is recorded on a public blockchain, it is not controlled by a frontend alone and may not be erasable by a person or entity acting through that frontend. Applicable legal responsibilities are not waived by this technical limitation.

Depending on the actual hosting and technical implementation, the frontend, its host, or a provider may process:

  • Browser type and version.

  • Operating system.

  • Device screen dimensions.

  • Language preferences.

  • Theme preferences.

  • IP address or network connection information, including in ordinary hosting or security logs.

  • Page access records.

  • Error logs and performance information.

No analytics or telemetry service is verified as deployed in the current application. The existence of this Policy does not itself mean such a service is active.

The current application uses browser storage for user interface preferences such as locale and theme. Depending on the implementation, browser storage may also retain:

  • Language preferences.

  • Theme preferences.

  • User interface preferences.

  • Non-sensitive interface states.

The current application does not use a server-side session for these preferences. Users may clear local data through browser settings, although doing so may reset preferences or affect features.

If you contact a channel represented as official, you may provide:

  • Contact email addresses.

  • Voluntary feedback.

  • Technical issue reports.

  • Information reasonably necessary to resolve inquiries.

Never provide private keys, recovery phrases, passwords, or other sensitive authentication credentials.

The project materials available for this release do not provide a verified official privacy contact channel or guarantee a response. Information sent to any third-party channel may also be processed by that provider.

If the relevant service or feature is actually deployed, information may be processed to:

  1. Provide wallet connectivity and, if configured, smart contract interactions.

  2. Retrieve and display user orders.

  3. Display global sequence and reward status, if implemented.

  4. Record referral relationships.

  5. Calculate and display referral rewards.

  6. Retrieve TOKEN airdrop eligibility.

  7. Retrieve and display blockchain transactions.

  8. Maintain or improve frontend performance and user experience, if corresponding logs or tools are deployed.

  9. Respond to technical inquiries.

  10. Comply with applicable legal obligations.

Connecting a wallet does not disclose its private key to the frontend. The current application is not designed to request private keys or recovery phrases. A wallet address may nevertheless be personal information under applicable law, depending on context and identifiability.

Blockchain transactions are generally public and irreversible.

Once you submit a transaction through your wallet, the transaction information may be permanently recorded on the blockchain.

The frontend cannot by itself:

  • Rewrite or delete confirmed blockchain transactions.

  • Modify publicly recorded transaction history.

  • Guarantee that wallet addresses cannot be associated with real identities.

  • Prevent third-party blockchain explorers from reading public data.

  • Reverse completed smart contract operations.

Always review transaction details before signing.

If NEXORA uses IPFS, Arweave, or other distributed storage networks:

  1. Uploaded content may be retained by multiple nodes.

  2. Content may be accessible through content identifiers or transaction records.

  3. Removing a frontend reference does not necessarily delete the underlying content.

  4. Permanent storage networks such as Arweave may not support conventional deletion.

  5. Sensitive personal information, private keys, identity documents, and other information unsuitable for public disclosure should never be uploaded to public distributed storage.

Review the content and intended visibility before submitting information.

Where necessary and lawful, information may be processed or shared through:

  • Wallet services selected by users.

  • Blockchain networks and RPC providers.

  • Blockchain explorers.

  • Decentralized trading protocols.

  • Distributed storage networks.

  • Third-party tools voluntarily selected by users.

  • Judicial or regulatory authorities where legally required.

NEXORA should never provide users' private keys or recovery phrases to third parties.

Anyone with access to a public blockchain may be able to read its publicly available data.

The Platform may use blockchain infrastructure and third-party services located in different countries or regions.

Those providers may process information under their own privacy policies.

Data protection requirements differ across jurisdictions.

You should review the privacy policies of third-party services before using them.

Different types of information are retained under different mechanisms:

  • Blockchain transactions: according to the technical characteristics of the blockchain.

  • Smart contract state: according to on-chain storage rules.

  • IPFS content: depending on content providers and node retention.

  • Arweave content: potentially for extended or permanent periods.

  • Browser local data: controlled by browser storage and user deletion.

  • Information sent through a contact channel: retained by the actual channel operator according to its policies and applicable law.

  • Contact emails: retained according to inquiry handling, legal obligations, and reasonable retention periods.

Because blockchain records may be immutable, no deletion of all publicly recorded data can be guaranteed. This technical limit does not remove any legal obligation applicable to a responsible controller.

Depending on applicable law, you may have the right to:

  • Access personal information.

  • Correct inaccurate information.

  • Request deletion of information that can legally be deleted.

  • Withdraw certain permissions or consent.

  • Object to specific processing activities.

  • Request data portability.

  • Lodge complaints with relevant data protection authorities.

These rights may be limited by blockchain immutability, legal obligations, and independent third-party processing.

The Platform is not intended for individuals below the legal age of majority in their jurisdiction. No age-verification or dedicated minor-data process is verified for the current application. Any responsible controller must handle personal information concerning minors in accordance with applicable law.

Any responsible operator or controller must use appropriate safeguards for information under its control as required by applicable law. No particular organizational program, security audit, or guarantee is established by this document.

However, no blockchain network, smart contract, or internet infrastructure is completely secure.

You remain responsible for protecting your wallet, device, network environment, and authentication credentials.

This Privacy Policy may be updated in response to product changes, technical architecture, or applicable legal requirements. Updated copies should identify the applicable document version; no effective date is asserted in this draft.

An update does not mean that historical public blockchain records can be modified or deleted.

The project materials available for this release do not identify a verified operating entity, data controller, registered address, or official privacy contact channel. This documentation gap does not establish that no responsible entity exists or remove any legal responsibility. The responsible controller must be determined from the actual service, processing activities, and applicable law. No permanent response channel, response time, or staffed support service is promised. Contact details should be published only after verification and legal approval.