We are Fanatical About Protecting Your Privacy.

KeeperChatTM utilizes best-in-class security to safeguard your messages and attachments.

Keeper's Best-In-Class Security

  • Private Master Password

    ONLY the user has knowledge of and access to their Master Password and key that is used to encrypt and decrypt their information.

  • Strongest Encryption

    Keeper protects your information with AES 256-bit encryption and PBKDF2, widely accepted as the strongest encryption available.

  • Multi-Factor Authentication

    Keeper supports multi-factor authentication, biometric login and Keeper DNA which uses personal devices like your smartwatch to confirm your identity.

  • Deep-Level Encryption

    User data is encrypted and decrypted at the device level not on Keepers servers or in the cloud.

  • Secure/Reliable Cloud Vault

    Keeper Security, Inc. utilizes Amazon AWS to host and operate the KeeperChat architecture providing customers with the fastest and safest messaging solution.

Overview

Keeper Security, Inc. (KSI or Keeper) is passionate about protecting its customer’s information with KeeperChat mobile and desktop security software.
KeeperChat was created by Keeper Security, Inc., the creators of Keeper, the world’s leading password manager and secure digital vault. Millions of consumers and businesses trust Keeper to secure and access their passwords, messages and private information.

Keeper’s software is constantly improved and updated to provide our customers with the latest in technology and protection. This page provides an overview of Keeper’s security architecture, encryption methodologies and hosting environment as of the current published version. An overview into the technical details involving our encryption and security methods are described in this document.

Data Protection

Keeper Security is a zero-knowledge security provider. The KeeperChat user is the only person that has full control over the encryption and decryption of their data. With KeeperChat, encryption and decryption occurs at the user’s device and is securely transported from the user's app to KeeperChat’s Cloud Security Vault. The encryption key that is needed to decrypt your data always resides with the KeeperChat user. KSI cannot decrypt or view your KeeperChat messages, including any file attachments such as photos or videos.

KSI does not have access to your master password nor does KSI have access to the records stored within the KeeperChat vault. KSI cannot remotely access your devices nor can it decrypt your KeeperChat vault. The only information that Keeper Security has access to is your email address, device type and subscription plan details. If your device is lost or stolen, KSI can assist in accessing encrypted backup files to restore your KeeperChat vault once you have replaced your device.

Information that is stored and accessed in KeeperChat is only accessible by the customer because it is instantly encrypted and decrypted on-the-fly on the device that is being used - this applies to both mobile and desktop devices. The method of encryption that Keeper uses is a well-known, trusted algorithm called AES (Advanced Encryption Standard) with a 256-bit key length. Per the Committee on National Security Systems publication CNSSP-15, AES with 256-bit key-length is sufficiently secure to encrypt classified data up to TOP SECRET classification for the U.S. Government.

The cipher keys used to encrypt and decrypt customer records are not stored or transmitted to Keeper's Cloud Security Vault. However, to provide syncing abilities between multiple devices, an encrypted version of this cipher key is stored in the Cloud Security Vault and provided to the devices on a user's account. This encrypted cipher key can only be decrypted on the device for subsequent use as a data cipher key.

Strong Master Password

It is highly recommended that customers choose a strong Master Password for their KeeperChat account. This Master Password should not be used anywhere outside of KeeperChat. Users should never share their Master Password with anyone.

Two-Factor Authentication

To protect against unauthorized access to a customer’s account, KeeperChat offers Two-Factor Authentication. Two-factor authentication is an authentication method that requires two or more of the three authentication factors: a knowledge factor, a possession factor and an inherence factor. In other words, it’s based on something you know, something you have and something you are. For more information on Two-Factor Authentication see this link.

KeeperChat uses something you know (your password) and something you have (the phone in your possession) to provide users extra security in the case where your master password or device is compromised. To do this, we generate TOTPs (Time-based One-Time Passwords).

KeeperChat generates a 10-byte secret key using a cryptographically secure random number generator. This code is valid for about a minute, and is sent to the user by SMS or Google/Microsoft Authenticator (TOTP).

When using the Google Authenticator or other TOTP application on your mobile device, the KeeperChat server internally generates a QR code containing your secret key and it is never communicated to a third party. Each time a user deactivates and then reactivates Two-Factor Authentication, a new secret key is generated.

To activate Two-Factor Authentication, visit the Settings screen.

Client Encryption

Data is encrypted and decrypted on the user's device, not on the Cloud Security Vault. We call this "Client Encryption" because the client (e.g. iPhone, Android Device, etc.) is doing all of the encryption work. The Cloud Security Vault stores a raw binary which is essentially useless to an intruder. Even if the data is captured when it's transmitted between the client device and Cloud Security Vault, it cannot be decrypted or utilized to attack or compromise the user's private data.

Breaking or hacking a symmetric 256-bit key would require 2128 times the computing power of a 128-bit key. In theory, this would take a device that would require 3×1051 years to exhaust the 256-bit key space.

Sharing

Each user has a 2048-bit RSA key pair that is used for sharing records and messages between users. Shared information is encrypted with the recipient's public key. The recipient decrypts the shared information with their private key. This allows a user to share records only with the intended recipient, since only the recipient is able to decrypt it.

Key Generation

KeeperChat uses PBKDF2 with HMAC-SHA256 to convert a password to a 256-bit encryption key with up to 100,000 rounds. PBKDF2 iterations are based on the device platform and managed by the user in KeeperChat's 'Advanced Settings' screen. Iterations can also be enforced by the KeeperChat Business administrator.

Key Storage

All secret keys that must be stored (such as each user's RSA private key and the Data Key), are all encrypted prior to storage or transmission. The user's Master Password is required to decrypt any keys. Since Keeper's Cloud Security Vault does NOT have access to the user's Master Password, we cannot decrypt any of your keys or data.

Cloud Security Vault

The Cloud Security Vault refers to KSI's proprietary software and network architecture that is physically hosted within Amazon Web Services (AWS) infrastructure.

When the user synchronizes their KeeperChat vault with other devices on their account, the encrypted binary data is sent over an encrypted SSL tunnel and stored in KeeperChat's Cloud Security Vault in encrypted format.

Network Architecture

Keeper Security, Inc. utilizes Amazon AWS to host and operate the KeeperChat solution and architecture. Utilizing Amazon AWS allows Keeper to seamlessly scale resources on-demand and provide customers with the fastest and safest cloud storage environment. KSI operates both multi-zone and multi-region environments to maximize uptime and provide the fastest response time to customers.

Server Authentication

To prevent unauthorized vault access, KeeperChat's Cloud Security Vault must authenticate each user when transmitting data. Authentication is performed by comparing a PBKDF2-generated hash of the Master Password. The user's device uses PBKDF2 to generate the hash from the Master Password and the server compares the hash to a stored hash.

By using the PBKDF2 hash instead of the Master Password itself, the Cloud Security Vault authenticates the user without requiring the Master Password. PBKDF2 is also used for generating encryption data keys, but the authentication hash is not used for data encryption.

Transport Layer Encryption

KSI supports 256-bit and 128-bit SSL to encrypt all data transport between the client application and KSI's cloud-based storage. This is the same level of encryption trusted by millions of individuals and businesses everyday for web transactions requiring security, such as online banking, online shopping, trading stocks, accessing medical information and filing tax returns.

KSI deploys SSL/TLS certificates signed by Digicert using the SHA2 algorithm, the most secure signature algorithm currently offered by commercial certificate authorities. SHA2 is significantly more secure than the more widely used SHA1, which could be exploited due to mathematical weakness identified in the algorithm. SHA2 helps protect against the issuance of counterfeit certificates that could be used by an attacker to impersonate a website.

KSI also supports Certificate Transparency (CT), a new initiative by Google to create a publicly auditable record of certificates signed by certificate authorities. CT helps guard against issuance of certificates by unauthorized entities. CT is currently supported in the latest versions of the Chrome web browser. More information about Certificate Transparency can be found at: http://www.certificate-transparency.org/

  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA256
  • TLS_RSA_WITH_AES_128_CBC_SHA
  • TLS_RSA_WITH_AES_256_CBC_SHA256
Key Pinning

KeeperChat's native clients implement HTTP Public Key Pinning (HPKP). HPKP is a security mechanism which allows HTTPS websites to resist impersonation by attackers using fraudulent certificates.

iOS Keychain, Touch ID® and Face ID®

Touch ID on iOS devices allows you to access your KeeperChat vault on your iOS device using your fingerprint. To provide this convenient feature, an unintelligible version of your Master Password is stored in the iOS Keychain. The iOS Keychain item created for this functionality is not designated to synchronize to the iCloud Keychain and thus will not leave your iOS mobile device.

It is highly recommended that you use a complex Master Password and enable Multi-factor authentication in order to provide maximum security for your encrypted KeeperChat Vault. Using Touch ID makes it more convenient to use a complex Master Password on your iOS mobile device. It is also recommended that you set a passcode longer than the minimum 4-digits to secure the iOS Keychain.

The iOS Keychain is used by iOS and apps to securely store credentials. iOS apps use the iOS Keychain to store a variety of sensitive information, including website passwords, keys, credit card numbers and Apple Pay™ information. KeeperChat does not use the iOS Keychain to store your KeeperChat records - all KeeperChat records are protected with 256-bit AES encryption and are securely stored in the KeeperChat Vault. The iOS Keychain is also encrypted with 256-bit AES encryption using the device's passcode. Even if the device is lost or stolen or an attacker obtains physical access to the mobile device, they will be unable to access any stored KeeperChat information. The iOS Keychain cannot be decrypted without the passcode and the KeeperChat Vault cannot be decrypted without the user's KeeperChat Master Password.

Apple Watch® and Android Wear

The Apple Watch Favorite feature allows the viewing of selected records on a paired Apple Watch. Keeper records must be explicitly enabled to allow viewing on the Apple Watch. A paired Apple Watch communicates with the Keeper Watch Extension that transparently runs in a sandboxed space separate from the iOS Keeper App. The Keeper Watch Extension also uses iOS Keychain to securely store and access keys to enable it to seamlessly and securely communicate with the iOS KeeperChat app.

Keeper DNA®

Keeper DNA is a new and innovative addition to multi-factor authentication. When used with a paired Apple Watch or Android Wear device, Keeper DNA provides a multi-factor authentication method that is unparalleled in convenience and security. These time-based authentication requests can be approved and sent automatically from the Apple Watch or Android Wear device with a tap on the screen of the watch or entered manually by the user. Multiple layers of encryption, biometric ID and multi-factor authentication help make Keeper DNA the most elegant, secure and advanced authentication method available.

Security Audits, Scanning & Testing

Third-Party Security Scanning & Penetration Tests

KSI is tested daily by McAfee Secure to ensure that the KeeperChat desktop application and KSI’s Cloud Security Vault are secure from known remote exploits, vulnerabilities and denial-of-service attacks. Secure badges may be found on the Keeper website to verify daily testing of the KeeperChat website, Web application and Cloud Security Vault.

A comprehensive external security scan is conducted monthly on the KeeperChat website, KeeperChat desktop application and KeeperChat Cloud Security Vault by Trustwave. Keeper’s staff periodically initiate on-demand external scans through Trustwave.

Certified SOC2 Compliant
Customer vault records are protected using stringent and tightly monitored internal control practices. Keeper is certified as SOC 2 Type 2 compliant in accordance with the AICPA Service Organization Control framework. SOC2 certification helps ensure that your vault is kept secure through the implementation of standardized controls as defined in the AICPA Trust Service Principles framework.
Payment Processing and PCI Compliance

The KSI uses PayPal Payments Pro for securely processing credit and debit card payments through the KSI payment website. PayPal Payments Pro is PCI-DSS compliant transaction processing solution.

KSI is certified PCI-DSS compliant by Trustwave.

The KeeperChat desktop client, Android App, Windows Phone App and iPhone/iPad App have been certified EU Safe Harbor compliant with the U.S. Department of Commerce’s EU-U.S. Safe Harbor program, meeting the European Commission’s Directive on Data Protection. For more information about the U.S. Department of Commerce U.S.-EU Safe Harbor program, see https://www.export.gov/safeharbor

U.S. Department of Commerce Export Licensed Under EAR

Keeper is certified by the U.S. Department of Commerce Bureau of Industry and Security under Export Commodity Classification Control Number 5D992, in compliance with Export Administration Regulations (EAR). For more information about EAR: http://www.bis.doc.gov

24x7 Remote Monitoring

Keeper is monitored 24x7x365 by a global third-party monitoring network to ensure that our website and Cloud Security Vault are available worldwide.

Phishing or Spoofed Emails

If you receive an email purporting to be sent from KSI and you are unsure if it is legitimate, it may be a “phishing email” where the sender’s email address is forged or “spoofed”. In that case, an e-mail may contain links to a website that looks like KeeperChat.com but is not our site. The website may ask you for your KeeperChat master password or try to install unwanted software on your computer in an attempt to steal your personal information or access your computer. Other emails contain links that may redirect you to other potentially dangerous websites. The message may also include attachments, which typically contain unwanted software called “malware.” If you are unsure about an email received in your inbox, you should delete it without clicking any links or opening any attachments.

If you wish to report an e-mail purporting to be from KSI that you believe is a forgery or you have other security concerns involving other matters with KSI, please contact us.

Hosting Infrastructure Certified to the Strictest Industry Standards

The KeeperChat website and cloud storage runs on secure Amazon Web Services (AWS) cloud computing infrastructure. The AWS cloud infrastructure which hosts Keeper’s system architecture has been certified to meet the following third-party attestations, reports and certifications:

  • SOC 1 / SSAE 16 / ISAE3402 (SAS70)
  • SOC 2
  • SOC 3
  • PCI DSS Level 1
  • ISO 27001
  • FedRamp
  • DIACAP
  • FISMA
  • ITAC
  • ITAC
  • CSA
  • MPAA

Vulnerability Reporting and Bug Bounty Program

Keeper Security is committed to the industry best practice of responsible disclosure of potential security issues. We take your security and privacy seriously are committed to protecting our customers’ privacy and personal data. KSI’s mission is to build world’s most secure and innovative security apps, and we believe that bug reports from the worldwide community of security researchers is a valuable component to ensuring the security of KSI’s products and services.

If you believe that you have found a security vulnerability on a KSI website, web application, mobile app, or desktop application we encourage you to let us know about it right away. We will investigate all legitimate reports and do our best to rapidly fix the problem. Before reporting a suspected security vulnerability, please review this page including our responsible disclosure policy, reporting guidelines, items that should not be reported, and activities that are prohibited.

Responsible Disclosure Policy

If you comply with the policies listed below during the process of reporting a security issue to KSI, we will not initiate a lawsuit or law enforcement investigation against you in response to your report.

  • You do not modify or access data of any account if the account owner has not consented to such actions
  • You do not violate the privacy of others
  • You do not cause the unauthorized access to or destruction of data and/or the interruption or degradation of KSI products and services
  • You do not exploit the security issue you discover for any reason, including but not limited to demonstrating additional risk or using the discovered security exploit to seek to discover additional vulnerabilities)
  • You do not intentionally violate any other applicable laws or regulations, including (but not limited to) laws and regulations prohibiting unauthorized access to data
  • For the purposes of this policy, you are not authorized to access user data or company data, including but not limited to personally identifiable information (PII), personal data (PD), and data relating to an identified or identifiable natural person
  • You do not publicly disclose the information without explicit written approval consent by KSI's Director of Security

Bug Bounty Program Eligibility

We recognize and value the community of security researchers that help keep our products and users safe and secure through responsible disclosure of security vulnerabilities. Monetary bounties for such responsibly disclosed reports are entirely at the discretion of KSI and are based on impact, severity, risk, and other factors. To qualify for a bounty you need to first meet the following requirements:

  • Adhere to our Responsible Disclosure Policy (see above)
  • Report a previously unknown issue
  • Report a security bug - a vulnerability in services or infrastructure that creates a security or privacy risk
  • Your report must describe a problem in a product or service listed under the bug bounty scope
  • If you inadvertently cause or privacy violation or disruption, you must disclose this in your report

Eligible Bugs

  • Authentication bypass
  • Bugs on customer-facing web applications
  • Bugs in desktop applications or mobile apps
  • Bugs in third-party assets located by KSI-operated customer-facing web applications
  • Cross-site request forgery
  • Cross-site scripting (XSS)
  • Privilege escalation
  • Information disclosure
  • Remote code execution
  • Timing or enumeration attacks that have a tangible risk to security or privacy

Out of scope / Ineligible for Bug Bounty

  • Spam or Email Spoofing
  • Social engineering attacks or phishing
  • Denial-of-service attacks
  • Cookie bugs
  • Previously submitted bugs
  • Brute-force attacks against locally encrypted data stores
  • Bugs that rely on key logging, compromise of the operating system or privileged access
  • Bugs on KSI blog sites
  • Legacy or unsupported versions of apps
  • Use of Keeper to bypass corporate firewalls or network malware detection

Disqualified Actions

Attempting any of the following activities against KSI’s services or infrastructure will result in permanent disqualification and possible criminal investigation and/or legal action. We do not allow any actions that could negatively impact our products or services.

  • Code injection on live systems
  • Brute force attacks against servers or services
  • Disruption or denial-of-service attacks
  • Threats, attempts of coercion or extortion of KSI employees, partners, or customers
  • Physical attacks against KSI employees, partners, or customers
  • Vulnerability scans or automated scans by scanning software tools or third-party scanning services without the explicit written permission of KSI

Bounty and Submission

If you have discovered a security bug that you feel meet the requirements for submission for a bug bounty, and you are the first researcher to report it, we will gladly reward you for your hard work. Bounty payout is based on the severity and impact of the bugs. We do not publish a schedule of bounty payouts, as each bounty is evaluated individually and bounties may vary greatly.

Please follow these steps to submit a security bug for consideration for a bounty payout:

  • Email us at “security@keeperchat.com” and include the title “Bug Bounty Report”
  • Within body of the email, please describe the nature of the bug along with any steps required to replicate it. Please include screenshots if applicable
  • Include your full legal name and contact information
  • If you feel that your report may be sensitive in nature, we ask that you encrypt your report with our public PGP key