Security at Cleaner OS

Security is foundational to a platform that handles homes, schedules, and people's pay.

How we protect data

• Encryption in transit (TLS) and at rest (disk-level encryption on our managed database and object storage).
• Multi-tenant isolation enforced at the database layer with row-level security — one company's data is never visible to another. Isolation is proven by an automated test suite that runs on every change and blocks the release if it fails.
• Least-privilege access with role-based controls. Cleaners cannot see what a client is charged; clients cannot see internal notes, margins, or crew identities. These boundaries are enforced in the database, not only in the interface.
• Home photos are served through short-lived, access-controlled links that expire in minutes.
• Break-glass support access — internal access to a customer's data is read-only, requires a stated reason, auto-expires on a server-set timer our staff cannot extend, and shows the account owner a live banner naming the reason while it is open. Every open and close is written to an append-only audit log.
• AI processing runs under zero-data-retention terms with every provider we send data to — your data is not retained by them and is not used to train models. Current providers are listed in the DPA.
• Secrets management, dependency and vulnerability monitoring, and backups.
• Vendor due diligence on our sub-processors (see DPA).

Home access information

Some customers store gate, door, or alarm codes against a property so the assigned cleaner can get in.

Be precise about what this is. Access notes are stored as ordinary text in our database. They are protected by tenant isolation, row-level security, and least-privilege access — the same controls that protect every other record — and by encryption at rest at the storage layer. They are not held in a separate secrets vault, and they are not encrypted with a per-record key that would keep them unreadable to our own database administrators.

If that is not the right control for a given property, do not store the code here — leave a lockbox instruction instead. We would rather tell you exactly what we do than let you assume more.

Compliance posture

We are not SOC 2 certified. A SOC 2 audit is on our roadmap and we will publish the report here when one is issued. We do not hold any other security certification today. Our processing terms are in the DPA; privacy practices in the Privacy Policy.

Data residency

Cleaner OS is a United States service. It runs in the US and is offered only to businesses in the US.

Responsible disclosure

Found a security issue? Email security@cleaner-os.com. We appreciate responsible disclosure and will respond promptly.