- All Collections
- Security, Privacy and Terms
- Data Security
Our team believes your email data is sensitive and should remain secure and private. We've built Bounceless using our 10 year's experience in the email security and privacy industry to ensure your data is protected using industry best practices. Bounceless will never sell or share the addresses you verify using our system.
As a part of our commitment to your security and privacy, we feel it's important to share the measures Bounceless takes to ensure your email data remains protected.
How does Bounceless Protect Your Data?
When you upload or import a list of email addresses to Bounceless for processing, we take the following measures to secure your data:
List data is transmitted over 256-bit SSL, the same protocol used by financial firms to ensure secure data transmission.
Your data is then stored, encrypted, on our servers. After your list has been processed, the results are also uploaded, and encrypted, to our servers. This data is stored under a private policy, and can only be accessed by someone with access to your account and certain Bounceless staff members.
Your list data will be automatically deleted after 90-days. At this time, neither you nor the Bounceless staff will have access to any list data, so it's important to make sure you've downloaded your results before this time. You may also delete your results any time before the 90-days as an added precaution.
How does Bounceless Protects Your API Data?
Email addresses verified using the Bounceless API are protected during transmission using 256-bit SSL. Bounceless may cache the email address results for a time, but does so using an irreversible cryptographic hash of the email address from which the original verified address cannot be derived.
Bounceless may log data related to unexpected errors, which may include email address data, in order to identify and diagnose any issues with our system. This data is typically disposed of within 7 days and remains protected using best practices in the interim.
Did this answer your question?