A practical summary of how Milago handles your meeting data. For the full legal terms see our Privacy Policy and Terms and Conditions.
A note on what this page is. The list below reflects the controls and practices we have in place today. Milago does not currently hold formal certifications such as SOC 2 or ISO 27001 — we'll publish those if and when we obtain them. Customers needing a named sub-processor list, signed Data Processing Agreement, or detailed security review can request one via support@milago.ai.
Customer content is not used to train general AI models
Export or delete from product settings
HTTPS / TLS for all traffic
Milago relies on third-party providers to deliver the Service. The categories below describe the kinds of providers we use and what they do. A specific named list of providers (and the signed agreements we hold with each) is available to customers on request — see the Privacy Policy for how to ask.
| Category | Purpose | Customer data handling |
|---|---|---|
| AI processing | Generate summaries, action items, and insights from meeting transcripts | Not used for training |
| Speech-to-text | Convert meeting audio into transcripts and speaker labels | Not used for training |
| Meeting capture infrastructure | Help the meeting bot join supported meetings | Processed for the duration of the meeting |
| Cloud hosting & storage | Host the application, store databases and media files | Retained while your account is active |
| Payment processing | Process subscriptions, invoices, and refunds | Card details handled by the payment gateway; not stored on Milago systems |
| Transactional email | Send verification, billing, and notification emails | Minimal (delivery logs only) |
For vulnerability reports, sub-processor lists, security review responses, or a copy of our standard data processing terms:
support@milago.ai