Security
How Minto handles your meeting data.
A plain description of where your data goes, who can reach it, and what happens when you delete it. Nothing here is aspirational.
Where recordings live
Uploaded and recorded audio goes into a private storage bucket scoped to your workspace. It is never publicly addressable; playback happens through a signed link that expires after an hour.
Who can see a meeting
A meeting is private to the person who created it until it is explicitly shared. Sharing targets named people in the same workspace. Members cannot browse meetings that haven't been shared with them.
What happens when you delete
Deleting a meeting deletes the stored audio file first, then the meeting and everything derived from it — transcript, summary, key points, decisions and participant links. Tasks that already exist are kept and simply lose their link to the meeting, so work in progress isn't destroyed.
Who processes the content
Transcription and analysis run on Google's Gemini API. Minto uses meeting content only to produce your transcript, summary, decisions, tasks and Minto AI answers. It is not sold, and it is not used for advertising.
How you sign in
Authentication is passwordless: an emailed magic link, or your Google account. Minto stores no passwords. API keys you create are stored only as a hash and shown to you once.
What Minto AI can reach
Minto AI answers using the recent meetings, tasks and people of the workspace you're currently in, under the same access rules as the rest of the app. It is instructed to answer only from that material.
What Minto does not claim
Minto has no SOC 2, ISO 27001 or HIPAA certification, and does not claim application-level encryption beyond what the platform provides. If a certification is a hard requirement for your organisation, Minto is not the right fit today.