Your site and visitor data are safe with CliClap. There are a number of steps we take to ensure you are the only person who can access your data and that your visitors' privacy is respected.
All data CliClap collects is stored electronically in USA, Azure Web Services infrastructure, West US and West US 2 data centers. The database containing visitor and usage data is only accessible from the application servers and no outside sources are allowed to connect to the database.
Data collection and transmission
- CliClap transmits data from the visitors browser to our system using HTTPS.
- The protocols and ciphers suite used to encrypt data in transfer is available at the end of this article.
Data access and authentication
Only CliClap engineers which require such access to perform their job efficiently are given access. Engineers who do have access, have their own credentials and these are only valid when used from specific IPs. User/Password or SSH Key-Based authentication is used for server access.
Data collected through CliClap is exclusively reserved for use by our customers. CliClap does not make use of the data collected in any form or way unless consent is officially given by an admin of the CliClap account, clearly outlining what the data will be used for.
Data access and backup
CliClap uses geo-redundant storage (RA-GRS) Database replication as our disaster recovery strategy. The backup database is stored on Azure Data Center (West US 2).
CliClap Architecture & Security
Data in transfer is encrypted using the following protocols and ciphers:
SSL Signature algorithm
Our technology and processes adhere to the strictest legal privacy requirements. In fact, we engaged a specialized law firm to assist us with the process of drafting a policy that is suitable for us, as well as for CliClap users around the world.
Need more details or have any questions?
If you are interested in additional details, we can also provide you with a security Q&A document we created ourselves by analyzing over a hundred security questionnaires we were sent to fill-in. The document outlines the most common queries these documents typically contain.
So we can provide you with our in-depth security Q&A document or if you'd like us to answer any additional queries you might have, contact us at firstname.lastname@example.org.