Security Statement

Overview

The Lou platform is built with state of the art software frameworks and technologies. It consists of a secure web application and content delivery network (CDN) that store, deliver, and serve content to customer applications. All data is stored in top-tier cloud environments managed by Amazon Web Services.

Security

The security of all data that Lou collects, receives, and stores is our top priority. Lou employees are responsible for maintaining the security of any data that they interact with and all employees are trained and informed of the requirements surrounding our data privacy policy. Only authorized employees with security clearance have access to customer data and these employees are required to provide credentials before receiving access. We do not collect any personally identifiable data from our customers' end-users. It is the responsibility of our customers to provide and maintain secure login information. At Lou our team of engineers is constantly monitoring system health and server uptime. If you have any questions, email contact@louassist.com.

Chrome Extension Policies

While Google's permissions and privacy policy grant our chrome extension access to read data from websites that you visit, the Lou Builder extension DOES NOT read, scrape, or store any data other than the website elements that you select when building a Lou experience. Also, the extension can be disabled at any time when not in use. For more info on exactly what data our extension collects, please email contact@louassist.com

Continuous Monitoring

24/7 error logging and uptime monitoring ensures that if you or your users run into any issues with Lou, we will respond rapidly and fix them.

Data Management

Lou retains data for the entire duration of a customer contract. Upon request, Lou will delete all customer data within 10 business days.

Security Breach Notifications

In the unlikely event of a security breach, Lou will immediately take action to contain the incident and notify customers of the breach.

This Security Statement was last updated on 02/15/22.