We aim for 99%+ uptime and publish all outages, breaches, and metrics on our status page. You can subscribe to our status page to get updates in a timely manner. In the last 12 months there has been less than 3 hours of downtime and no breaches.

We continuously backup our database and can rollback to any point in time up to 7 days ago. We make logical backups of our database once a day.

None, we send push notifications and email notifications instead. We can send push notifications because we publish the Lookout app for iOS and Android devices on the App Store and Play Store respectively. It's like SMS in that it appears as a notification, but it doesn't cost you anything to send.

No, we work on all modern browsers. See our Supported Devices Policy.

We conservatively estimate 450kb of mobile data per visit. That is, loading the schedule, checking in, checking out, confirming breaks, leaving a note, reading the help plan, responding to a must do. If a worker provides 5 visits in their shift for the day they'll use about 2.25mb of mobile data.

We have extensive monitoring into the health of the application as well as logging which we retain for 15 days. We use encryption in-flight (Everything is HTTPS), at rest (Data is encrypted on hard drives), and at work (Fields like date of birth are encrypted in the application). We host Lookout in an environment isolated from the public internet. We enforce all accounts in Lookout Admin to have a second factor of authentication. We run regular penetration testing as a part of our build pipeline. See our Privacy Policy.

Updates to Lookout and our underlying infrastructure happen many times a day and are done seamlessly without interruption. They include small updates, security updates, bug fixes, or partial/full feature implementations. On a single week, there are about 30 updates to Lookout. See What's New? for our full change log.

We physically host Lookout and backups of Lookout in Sydney, Australia. See our Privacy Policy.