1. Security at Flo

Security

Your personal data security is our top priority at Flo. We do understand that your app profile may contain highly sensitive personal data. Therefore, every day we do our best to implement industry best practices and standards.
Legal compliance
Flo is committed to ensuring the security and protection of personal data following the requirements of the EU General Data Protection Regulation, California Consumer Privacy Act and other regulations.
3rd party audits
We regularly conduct audits with the assistance of well-known third-party agencies to screen and enhance our internal security processes and policies.
Physical and environmental security
Flo complies with the highest industry standards for physical, environmental, and hosting controls. Flo data centers handled by Amazon Web Services get advantage of the brand new architectural and engineering approaches.
Product security
Servers and networking

We use Amazon Web Services to host all production environments. AWS is designed to help us build a secure, high-performing, resilient, and efficient infrastructure for our application. AWS data centers are secure by design and SOC 1, SOC 2, and SOC 3-certified. All our production servers are immutable, continuously patched Docker-based systems. We also utilize additional AWS services such as VPC (Virtual Private Cloud), AWS multi-account infrastructure, EKS (Elastic Kubernetes Service). To secure communication over the network, we use HTTPS protocol encrypted using TLS (Transport Layer Security). 

 

We use Amazon Web Services to host all production environments. AWS is designed to help us build a secure, high-performing, resilient, and efficient infrastructure for our application. AWS data centers are secure by design and SOC 1, SOC 2, and SOC 3-certified. All our production servers are immutable, continuously patched Docker-based systems. We also utilize additional AWS services such as VPC (Virtual Private Cloud), AWS multi-account infrastructure, EKS (Elastic Kubernetes Service). To secure communication over the network, we use HTTPS protocol encrypted using TLS (Transport Layer Security). 

 

Encryption

We utilize AWS KMS (Key Management Service) to create and manage keys and control the use of encryption across a wide range of AWS services and our application.

 

We utilize AWS KMS (Key Management Service) to create and manage keys and control the use of encryption across a wide range of AWS services and our application.

 

Storage

Flo stores all data such as metadata, activity, original files, and customer’s data in different places. All data is encrypted by KMS in each place.

End-user sensitive data is removed from logs and Flo engineers have no access to this data.  

Flo stores all data such as metadata, activity, original files, and customer’s data in different places. All data is encrypted by KMS in each place.

End-user sensitive data is removed from logs and Flo engineers have no access to this data.  

Isolated environments

The Production network is isolated from other Staging, Development, and Infrastructure environments. Every environment is located on the separate AWS account into separate VPC networks.

 

The Production network is isolated from other Staging, Development, and Infrastructure environments. Every environment is located on the separate AWS account into separate VPC networks.

 

Customer payment data

All payments are processed either by the App Store, Google Play or Stripe who take full responsibility for payment security. Flo doesn’t store any credit card information.

 

All payments are processed either by the App Store, Google Play or Stripe who take full responsibility for payment security. Flo doesn’t store any credit card information.

 

Secure by design
Flo engineers leverage best product development techniques that adhere to industry standards such as having a documented development and quality assurance processes. Guided by security principles of confidentiality, integrity, and availability, we design our app in such a way to reduce risks of vulnerability-opening mistake.