1. Scope of this draft
This page outlines privacy topics for the proposed Nexus Crypto service. A final policy must identify the operator and accurately describe data handling before launch.
2. Information in this preview
Registration stores your name, email, password hash, optional referral code, and terms acceptance in the configured database. The contact form stores your name, email, topic, and message. Sign-in uses a session cookie. Passwords are hashed before storage.
3. Browser storage
Sign out to end your session. Dashboard demonstration settings may be stored locally in your browser. Hosting services may have their own logging practices, which must be documented for the final deployment.
4. Information a live service may need
The final policy must list the actual account information, contact messages, verification details, transaction records, and technical data collected, along with their specific purposes.
5. Sharing and retention
Service providers, international transfers, retention periods, and deletion processes have not been established for this preview. They must be specified based on the implemented service.
6. Your choices
The live service must explain applicable access, correction, deletion, and other privacy rights, together with a working contact route. The process will depend on the confirmed operator and jurisdiction.
7. Cookies and analytics
No analytics scripts are included in these sample pages. Any cookies, analytics, or tracking introduced later must be described along with applicable choices.
8. Contact and updates
For privacy enquiries, email info@nexuscryptoltd.com. The effective date and final policy procedures remain subject to operator approval.
Website chat
Website chat stores the name you provide, optional email address, message contents, conversation status and timestamps in the configured database. A session-held random identifier associates your browser with its conversation. Messages are accessible to that browser session and authorized administrators.
Clearing session cookies or switching browsers can prevent you from returning to the same chat. Do not send passwords, recovery phrases or private keys. The operator must define retention periods and an applicable request process before launch.
Account emails
Activation and security emails support account access. Deposit, withdrawal and support-ticket email alerts can be managed in Email Preferences. The application stores notification preferences, queued message contents, recipients, delivery attempts and delivery status. Email is sent through the configured mail provider. Messages do not contain passwords or private keys.