The security and privacy of your data is very important to us, and we have taken significant measures to protect it, through both technical and procedural processes. We will never share your data with any third parties, nor use your data for any purpose. Your data in Close will only be shared/visible to other team members from your organization. Only a few members of our team could see your data, and we have processes in place where we only look at it if needed to diagnose a specific technical issue.
All connections to Close (in both web browsers and our Mac/Windows apps) are fully encrypted using bank-grade encryption and authenticated using a strong protocol (TLS 1.2), a strong key exchange (ECDHE_RSA with P-256), and a strong cipher (AES_128_GCM).
Since Close only works over HTTPS, you can be sure that your data in Close remains safe and can be accessed securely even from insecure public wifi locations.
We take extra precautions specifically around your email credentials and email data. For example your email credentials are encrypted using 256 bit AES, with the data and keys stored on separate servers. We also only ever show/attach your emails in Close if there's already an existing contact with a matching email address, to avoid having non-sales related emails exposed.
- Anytime you provide your email credentials to a service like Close, you're opening the ability for that company to have access to the emails in that account.
- We do scan through all your emails so that we can sync relevant emails that match with your sales leads.
- We take your data security and privacy extremely seriously - our reputation depends on it.
No third parties have access to your emails.
If you/your company aren't comfortable with the IMAP sync option, you could manually forward specific emails to Close using our secret Forward/BCC address. The downside of this approach is that it's not automatic.
Close has gone through an extensive professional security audit to help ensure the security of your data.
If you believe you have found a security vulnerability, please visit our Security Vulnerability Disclosure Policy.
Updated over 2 years ago