How we protect
your records.

Access checks run on the server and in the database, not just in the app. Technicians see the equipment assigned to them; owners and admins have wider access. Deactivating a staff member blocks their future online access. Signing someone out isn’t the same as deactivating them.

The website, dashboard and apps connect over HTTPS. Authentication and application data are held in Supabase. Photos and other evidence files are kept in private storage and only retrieved through access-checked routes.

We keep submitted readings, sign-offs and photos along with both the reported capture time and the time our server received them. Ordinary editing doesn’t overwrite accepted evidence; corrections are recorded separately. These records are maintenance evidence, not a guarantee of equipment safety or that a third party will accept them.

Database backups and photo copies are handled separately, and restores are tested. Your own exports are useful for your records but don’t replace our backups. We don’t currently promise a specific recovery time or continuous availability.

Some release checks, including real-device offline and notification testing, are still in progress. Keep your normal operational checks in place and confirm queued work has been accepted.

Protect your devices and sign-in details, remove access for people who leave, and never share passwords or sign-in codes, including with us.

Email [email protected] with a clear description. Don’t include passwords, access tokens or other people’s records. We’ll arrange a safe way to receive any sensitive details we need to investigate.