The aim of this policy (“Security Policy”) is to establish and maintain the security and confidentiality of all the information and services provided by CryptoView.
By using the services (also referred to as “Web Services”) provided by CryptoView, you (the User) agree to be legally bound by the terms of this Security Policy. Wherever used in this Security Policy, unless otherwise defined herein, capitalised terms used herein shall have the same meanings ascribed thereto in the Terms of Service.
You (the User) may not attempt to gain unauthorized access to the Web Services, or to any our server, by hacking, DDoS, spam, password “brute- forcing” or any other similar means.
You may not reverse look-up, trace or seek to trace any information on any other user of the Web Services, or exploit the Web Services in any way where the purpose is to reveal any information, including but not limited to personal identification or information, other than your own information.
You should not perform or try to perform non-technical attacks such as social engineering, phishing or physical attacks against our employees, users or our infrastructure and Web Services. You are not allowed to use automated tools and scanners to find vulnerabilities.
02 System security
AES 256-bit encryption of user data. Sensitive user data (encrypted or not) is never returned to the User.
Every data request on CryptoView goes through a verified and secure (ORG) SSL.
All User data requests go through filtering and validation on the front-end and back-end for XSS, SSL, CSRF, Clickjacking and Session Impersonation attacks.
For further prevention of injection attacks, only parameterized queries to the database are used.
Our servers are protected by a powerful firewall and are accessible only by key team members.
DNS-level DDOS (Distributed Denial of Service) protection is applied.
Security screening, internal auditing and monitoring for suspicious activity is employed across all Web Services. We perform regular audits and updates on our security systems and procedures.
03 API Key security
Exchanges allow you to set API key permissions, which enable functionalities used by CryptoView. Enable only API permissions required by CryptoView platform such as “Balance” or “Trading” and never activate “Withdrawal”.
It is your responsibility to keep both your CryptoView Account and your exchange accounts secure. By using the Web Services, you agree that you will notify CryptoView immediately if you are aware of any unauthorized use of your CryptoView account by any person or any other violations to the security rules.
- Confirm URL; enable 2FA; never disclose password or make any transactions to anyone. CryptoView will never ask you for your credentials.
- Never install any browser plug-ins that claim to be associated with CryptoView.
- Never make any phone calls to anyone that claims to be a CryptoView representative.
- Never disclose your password, Google authentication code, SMS authentication code or Google authentication key to anyone, including to CryptoView support.
- Never make transactions or send funds to anyone who claims to be a member of CryptoView support.
- Two-factor authentication (TOTP or U2F) is required to enable trading through your account.
04 Employee security
CryptoView’s employees will never ask you, by email or phone, to provide access credentials, API keys or any other information that might compromise your account security. Furthermore all sensitive personal information is strictly handled by authorized personnel. All employee accounts are restricted/compartmentalized to their specific area of knowledge.
Regular account auditing and password rotation are carried out.