All Collections
Getting Started
Articles
Security and privacy compliance
Security and privacy compliance

Find out how Reply is compliant with data requirements & regulations

Reply Team avatar
Written by Reply Team
Updated yesterday

Physical Security and Database Security

we prioritize the security and privacy of your data by adhering to leading standards and leveraging world-class MS Azure Cloud Services. Our infrastructure is designed with multiple layers of defense-in-depth security measures, ensuring comprehensive protection for your information. Our data centers are guarded by security measures, including perimeter fencing, video surveillance, security personnel, secure entrances, and real-time communication networks. These measures are implemented throughout the facility and extend to each physical server unit.

Restricted Access

Access to our production environment is strictly limited to authorized members of the Reply engineering team. Additionally, database access is restricted to specific IP addresses, such as those belonging to the Reply Service and our development office.

Network Security

We employ SSL/HTTPS for all network connections, guaranteeing privacy and data integrity during communication between computer applications. Our internal infrastructure is further secured by strict firewall policies.

Data Recovery

Azure's robust backup system ensures that your data is backed up every minute using incremental backups and encryption. These backups are stored in geo-replicated storage, maintaining six copies of your data across two Azure data centers.

Data Ownership and Privacy

Your data remains your exclusive property, and we utilize it solely to deliver our services. We do not share your data with third parties or engage in data mining for advertising purposes. Furthermore, we provide ample time for you to export your data before any deletion occurs.

Vulnerability Defense

Our application is protected against major security vulnerabilities including, but not limited to:

  • SQL injection;

  • XSS - Cross-site scripting;

  • Authentication vulnerabilities;

  • Application setup vulnerabilities (to avoid known website backdoors), handled by professional DevOps engineers.

  • Sensitive data theft;

  • CSRF (Cross-Site Request Forgery);

  • Other vulnerabilities (not disclosed due to security reasons).

Did this answer your question?