myViewBoard Security

The following content provides an overview of myViewBoard security. For more details, please see our security white paper.

myViewBoard integrates Github, Docker, and Circle CI, deploy secure, scalable architecture on Amazon Web Services Amazon Web Services Cloud platform, WebRTC’s protocol for securing our streaming service, and PGP (Pretty Good Privacy) in our secure file sharing and transmit use case. This approach is designed to balance customers’ needs for security and confidentiality with public information in regard to technologies and third-party solutions that myViewboard integrates. For more details, please see our security white paper.

	Safe Loop Supports HTTPS 256 AES encrypted connections, there are NO open text connections to myviewboard.com. No any attacker secretly relays and possibly alters the communication between two connected parties.
	Data Encryption and Authentication? Myviewboard.com keeps renewing “SSL & TLS certificates” which are the industry standard encrypted protocols to secure data encryption and authentication on network communications.
	Keep Your Privacy Unlike other apps which require users to input their Username/Password and save locally causing high risks, myviewboard.com adopts TOKEN based access for the registration of Third Party Cloud Storage Applications without saving or using Username/Passwords from other services such as Google Drive or OneDrive.
	Unique User ID and Device ID During installation, the app will verify a validated email address for ID registration to activate it. After installation, the app generates a unique ID for this Windows device with instance ID technology to make sure any records can be identified without ID confusion.
	Encrypted Files Every .vboard file is encrypted with AES256 encryption scheme and can be locked with a password to a specific user who will require the Private/Public Key to open the file.
	No Trace Behind When exiting the app, sign-out, users switch, or reaching the set idle timeout, the app will delete every temporary file. It also follows OAuth 2.0 which is commonly used as a way for Internet users to grant websites or applications access to their information on other websites/cloud storages but without giving them the passwords.