1. Controller and processing context
Milano Service processes the data required to create and operate SaaS tenants, authenticate users, manage subscriptions, protect the service and respond to technical or administrative support requests.
Milano Service SaaS
SaaS product privacy
Public summary of multi-tenant product data handling: accounts, branding, domains, operational activity, integrations and support. Ready to be replaced by final legal copy without changing the UX.
Operational draftLast operational review: May 9, 2026
This summary still requires final legal review. It already reflects the current SaaS technical flow so the final legal text can be inserted into a stable structure.
2. What data we process
We may process admin and team identity and contact data, tenant branding, domains, audit events, internal settings, technical metadata and the minimum information required for payments and security.
3. Purposes and operational bases
Data is used to provision tenants, authenticate access, enforce quotas, send notifications, enable billing, record security events and keep integrations active.
4. Sharing and providers
We only share information with infrastructure, email, payment, monitoring or other providers strictly required to run the service.
5. Retention and export
The service already supports self-service tenant export and audit log traceability. The exact retention, archival and final deletion policy still needs to be finalized in the legal version.
6. Customer rights
Customers should be able to request access, correction, export, restriction or deletion when permitted by applicable law and described in the final contract.
Recommended next step
This page already covers what exists in code today: tenant backup, audit log, billing, domains, branding and credentials. Only the final legal copy is still missing.