Gladia
Security

1. Infrastructure Security

‍

All of our services run in the cloud. We don’t host or run our own routers, load balancers, DNS servers, or physical servers. 

Our service runs on most well known, industry leading cloud providers. By default, we use a European provider based in France to respect GDPR constraints, but offer other geographies and specific providers per customer request.

2. Network level security monitoring and protection

Our network security architecture consists of multiple security zones. We monitor and protect our network, to make sure no unauthorized access is performed using:

• A virtual private cloud (VPC), a bastion host or VPN with network access control lists (ACL’s) and no public IP addresses.
• A firewall that monitors and controls incoming and outgoing network traffic.
• IP address filtering

3. DDoS protection

We use Distributed Denial of Service (DDoS) mitigation services powered by an industry-leading solution.

4. Data encryption

Encryption in transit: All data sent to or from our infrastructure is encrypted in transit via industry best-practices using Transport Layer Security (TLS). You can see our SSLLabs report here 

Encryption at rest: All our user data (including passwords) is encrypted using battle-proven encryption algorithms in the database.

5. Data retention and removal

By default, we store data up to 12 months.

For our customers, we can also provide custom data retention policies. These policies are the following: 1-month data retention, 1-week data retention, 1-day data retention, 1-hour data retention, and zero-data retention.
‍

After the end of the period, all data is then completely removed from the dashboard and server. Every user can request the removal of usage data by contacting support@gladia.io. Read more about our privacy settings here.

6. Data Processing and Model Training

Gladia builds advanced AI models. User audio data may be used for the training of the models.

‍

Only users in the Free Plan are subject to data used for model training. 

‍

All users and customers that are in the Pro Plan or Enterprise Plan, will not have their data used for model training.

7. Business continuity and disaster recovery

We back up all our critical assets and regularly attempt to restore the backup to guarantee a fast recovery in case of disaster. All our backups are encrypted at rest.

8. Application security monitoring

• We use a security monitoring solution to get visibility into our application security, identify attacks and respond quickly to a data breach.
• We use technologies to monitor exceptions, logs and detect anomalies in our applications.
• We collect and store logs to provide an audit trail of our applications activity.
• We use monitoring such as open tracing in our microservices.

9. Application security protection

• We use a runtime protection system that identifies and blocks OWASP Top 10 and business logic attacks in real-time.
• We use security headers to protect our users from attacks.
• We use security automation capabilities that automatically detect and respond to threats targeting our apps.

10. Secure development

We develop following security best practices and frameworks (OWASP Top 10, SANS Top 25). We use the following best practices to ensure the highest level of security in our software:

• Developers participate in regular security training to learn about common vulnerabilities and threats
• We review our code for security vulnerabilities
• We regularly update our dependencies and make sure none of them has known vulnerabilities
• We use Static Application Security Testing (SAST) to detect basic security vulnerabilities in our codebase
• We use Dynamic Application Security Testing (DAST) to scan our applications
• We rely on daily automated penetration testing, and yearly third-party security experts to perform penetration tests of our applications.

11. User protection

11.1 Single sign-on

Single sign-on (SSO) is offered for our enterprise customers. Single sign-on (SSO) is available using your Google account.

12. Compliance

12.1 GDPR

Gladia is compliant with the General Data Protection Regulation (GDPR) which went into effect on May 25, 2018. Gladia has worked to enhance its products, processes, and procedures to meet its obligations as a data processor.

The purpose of GDPR is to protect the private information of EU citizens and give them more control over their personal data. Contact us for more details on how we comply with GDPR.

12.2 Other Compliance & Certifications

Gladia has started processes to become SOC 2 Type 1 and Type 2 compliant, as well as ISO 27001 compliant.

13. Payment information

All payment instrument processing is safely outsourced to Stripe which is certified as a PCI Level 1 Service Provider. We don’t collect any payment information and are therefore not subject to PCI obligations.

You can read more about Stripe’s security practices here.

14. Employee access

• Our strict internal procedure prevents any employee or administrator from gaining access to user data. Limited exceptions can be made for customer support.
• All our employees sign a Non-Disclosure and Confidentiality Agreement when joining the company to protect our customers' sensitive information.

‍

If you encounter any issues, or have any questions, please contact security@gladia.io 

‍