Security at CleanZ

CleanZ is designed to keep personal data about the people a facility serves out. It stores rooms and areas, tasks, products, staff roles and cleaning results, not patient, resident, student or guest information. The table shows each control and its real status, so your security team can see what exists, what is in progress and what is planned.

Controls and their status

CleanZ security controls, each with its status and notes
ControlStatusNotes
No personal data about the people you servePilot releaseNo patient, resident, student or guest information
Encryption in transit and at restPilot releaseTLS for all traffic; encrypted storage for data and photos
Multi-factor sign-inPilot releaseRequired for managers and admins
Role-based accessPilot releaseCleaner, supervisor, spot-check reviewer, admin
Append-only audit logPilot releaseEvery change, override and approval is kept
Full data exportPilot releaseCSV and PDF, at any time
Shared-device sign-inPilot releaseFast switch by PIN or badge scan
Written security policies and questionnaire answersIn progressPart of the security packet
Single sign-on (SAML, OpenID Connect)PlannedVersion 2
SOC 2 Type I, then Type IIPlannedType I in Version 2; Type II in Version 3
Independent penetration testPlannedBefore the first large contract
Hosting provider and regionIn progressNot yet published
SubprocessorsIn progressNot yet published

This website

No advertising trackers and no analytics. Form submissions are sent only to our team's inbox, through Resend, an email delivery service. The site sets no cookies, so it needs no cookie banner. Privacy policy

Request the security packet

Architecture overview, data-flow diagram, policies and standard questionnaire answers.

Report a vulnerability

Write to [email protected]. We acknowledge reports within two business days.

Bring your security questions to the walkthrough.

A person replies within one business day.