Each client, a separate area
Your laundry has its own area in the system. Your team never sees another operation's data — not by mistake, not on purpose.
Security and compliance
Hospital data stays where it should stay.
Hospital laundry handles sensitive data — weight, soiling, contracts, invoices, linen history. Cleanifly is built so this data does not leak between clients, does not disappear in a network outage, and answers back when the auditor (or the hospital's CCIH, or procurement) asks.
Isolation
Your laundry is an island. No bridge to the next one.
Every laundry using Cleanifly has its own area in the system. There is no report, export or screen that mixes data from different clients — this is not just a toggle that can be flipped; it is how the system is built.
- Each client has a sealed area — the system does not cross data between them
- The block happens at the system core, not the interface
- No report or search ever shows another laundry's data
- Every action is recorded with who did it and when
Six layers. One calm operation.
Security is not a separate feature. It is how the system is built, from the database query to the icon on the operator's screen.
Data protected end to end
Connection to the system is encrypted. Passwords are stored in an unreadable format — not even our team can see them. Sessions expire automatically.
Every change is logged
Updated soiling index in a contract? Logged. Changed the price of an item? Logged. Every change has date, user and previous value — searchable.
Each user sees only what they need
The weighing operator sees weighing. Finance sees invoices. The hospital client sees only their data. You define who accesses what — by role and by page.
Compliant with sanitary regulation
Weight tolerance of ±30% (RDC 06/2012) validated automatically. Collection history searchable by date. Client documents linked to the process. ANVISA, ONA, CCIH — the system answers in the format the auditor asks for.
Works even without internet
Automatic daily backup. When the internet drops, the driver's tablet keeps working — syncs on its own once reconnected. Zero collections lost.
Audit trail
Every event, searchable.
The system records creation, validation, configuration and audit events. When an auditor asks about a collection from six months ago, the answer is a timeline — not a reconstruction from memory.
00:00:00 Record
Operator X registers a collection at hospital A
00:00:42 Record
Dirty weighing: 142 kg linked to contract #4581
02:14:17 Record
Clean weighing: 128 kg, soiling 9.8% (contract 10%)
02:14:18 Validation
Tolerance ±30% validated — within range
03:45:09 Configuration
Admin Y changed contract #4581 soiling from 10% to 11%
03:45:09 Audit trail
Audit trail: previous value preserved, new value applied from 05/09/2026
Compliance
Where we are today, where we are going. No promises, just the real state.
LGPD Brazil's General Data Protection Law
RDC 06/2012 ANVISA regulation for hospital textile processing
TLS 1.3 Transport encryption (HTTPS)
SOC 2 In preparation — audit 2027
ISO 27001 Under evaluation — 2027 roadmap
A 30-minute call with our technical team.
If the hospital's procurement or your IT team has a specific security question, we set up a direct conversation — not commercial. Your team asks, our team answers.