Cleanzi compliance centre

Every module has the right place and its own security boundary.

This public website is an entry point. Operational data belongs in the protected portal, operative app and Cleanzi backend — not in marketing pages.

Module architecture

What belongs here, and what belongs elsewhere in the system?

This public website

Explains the product, handles only the information needed for contact and a waiting-list request, and guides businesses towards a safe start.

  • Packages and trial principles
  • B2B contact and versioned notices
  • Privacy, cookies and provider information
  • Security, GPS and supplier descriptions
  • Contact and operator information

Company portal

Where owners, administrators and coordinators work, with organisation data and roles separated.

  • People, roles, invitations and access review
  • Clients, sites, zones and standards
  • Schedules, jobs, checklists and quality
  • Working time, pauses, QR and an event GPS point
  • Inventory, reports, settlement and export

Operative app

A simple role-limited view needed to perform work without access to company administration.

  • Personal account from a secure invitation
  • Daily plan, tasks and checklists
  • Start, pause and finish
  • QR scan and one location point
  • Comments, photos and issue reporting

Backend and cloud services

The non-public layer that enforces security, billing and the data lifecycle.

  • Identity, authorisation and organisation isolation
  • API and acceptance records
  • Payment provider and subscription state
  • Verification email, logs and security alerts
  • Retention, backup, export and deletion procedures

Privacy by design

Principles that apply regardless of package.

GPS only at an event

Cleanzi records one point during a deliberate action such as starting work. It does not track a route in the background.

Passwords belong to users

Operatives set passwords through secure invitations or resets. Administrators cannot read them.

The client controls its data

The DPA defines return, export and deletion procedures, while production parameters are confirmed before implementation.

Organisational governance

Part of compliance is not a page or a screen.

These controls operate internally at Cleanzi or are supplied as implementation documentation. Detailed safeguards that could facilitate an attack are not published.

  • Processing records and legitimate-interest assessments
  • DPIA for time, location, QR, photos and productivity reports
  • Data-subject, incident, breach and continuity procedures
  • Supplier register and sub-processor notifications
  • Employee privacy information and client monitoring templates
  • Country matrix and regional annexes before market launch

Documents

One public source of current versions.

International legal documents remain controlled drafts until local review and the exact production environment are approved.