Everything you want to know about MLOG

No. MLOG sends no bot and never joins the call — it captures this computer’s system audio and mic on two separate channels. The other side sees no “meeting bot”.

No. It’s a quiet sidebar floating beside your call: silent when passive, and only when asked it gives one answer, one data point and an evidence link. It never pops, blinks or auto-expands — and you can collapse it anytime.

Every conclusion carries a timecode link to the exact words and audio. When it can’t find a basis, it says “not found” — it never produces pretty but unaccountable content.

No. Outbound emails are only saved as drafts and go out solely after your explicit confirmation; writing back to Notion / Google Docs needs your confirmation too. The system never sends on its own — a human is always in the loop.

No. Audio is encrypted to this computer’s disk before any cloud processing (local-first). Recording continues through a network outage; once you’re back online it uploads and catches up the transcript. A crash loses ≤5 seconds — we treat any failed capture as an incident.

Due to operating-system and third-party app policy restrictions, we do not promise reliable capture of online-meeting audio on mobile. Mobile is built for in-person and on-the-go scenarios — offline capture, briefs, Advisor Q&A and post-meeting confirmation all happen on your phone. For online meetings, capture on desktop.

The interface and outputs support 8 languages: English (en), Español (es), Deutsch (de), Français (fr), 日本語 (ja), Português (pt), 简体中文 (zh) and 한국어 (ko). Switch anytime in Settings.

In-sentence code-switching is MLOG’s flagship capability, and you never declare a meeting’s language up front: the transcript keeps every language exactly as spoken instead of folding them into one. Search and minute generation understand the mixed context too. Chinese-English is the pair we have tested most thoroughly; other languages are labeled by tested engine capability.

Yes. A minute in your team’s language and a follow-up email in your client’s language are generated together as a pair; the language pair is set per meeting or per workspace. Every decision still carries its timecode link.

Yes. Audio is encrypted to this computer’s disk before processing, encrypted in transit and at rest, and a crash loses ≤5 seconds. Data resides in Singapore, is never used to train any model, and vendors are bound by zero-retention terms.

Cloud data resides in Singapore — the data center and backups stay within the Singapore region — while your original recordings always keep a local copy on your machine. See the Privacy Policy for details.

Never. Your recordings, transcripts and minutes never enter any model training; our speech-recognition and LLM vendors are bound by zero-retention terms and may not store or use your content.

You can export or delete all of your data from Settings at any time — the access, portability, correction and erasure rights granted by GDPR / CCPA. Deletion completes across all systems and backups within 30 days, with a confirmation sent to you.

Data takes exactly three steps, encrypted at every one: first AES-256 encrypted to your own disk (offline-safe, ≤5s loss on crash); TLS 1.2+ in transit; then encrypted at rest in the Singapore region, never replicated across regions — deletion cascades.

Four promises built into the product’s behavior: your data is never used to train any model; meeting content is workspace-only by default; outbound sends always need human confirmation; deletion cascades everywhere (audio, transcript, minutes, index and share links). Full text in the Privacy Policy.

Only three categories, under least privilege: cloud infrastructure (Singapore residency), ASR providers and LLM providers — the latter two bound by zero-retention terms and barred from training on your content. Full list in the Privacy Policy appendix; DPA customers get a live named list.

Yes. Data-subject rights — access, rectification, export and erasure — can be initiated directly in the app, answered within 30 days; we sell no personal information. Voiceprints are biometric data: separate consent, revocable anytime. Pro workspaces can request the DPA.

There is no free plan. All three tiers bill monthly in USD: Basic and Standard (hard-locked at 1 seat each) and Professional (3 seats included). All three place no limit on the number of meetings; each tier comes with a pool of credits that four services draw from, and each meeting draws its actual duration — never rounded up. Subscriptions belong to the workspace — see the pricing page for allowances and prices.

Nothing stops, and we never charge you automatically. As credits run low, services shut off in order of how safely they can wait — the live Advisor first, then cross-meeting questions, then cloud OCR — and recording and transcription are always the last to stop. Local capture and writing to disk never stop at all. When credits reach zero, cloud post-processing is held, not failed: add credits or wait for the next period to reset and it finishes on its own, with the held audio kept at least 30 days. Buying more takes one deliberate click, and the price is written there before you click. We will not debit you first and tell you afterwards. Usage is itemised and auditable.

Credits are the only meter in the product. One sentence is enough: 1 credit = 1 minute of recording, and the live Advisor runs at 4×. Recording and transcription costs 1 credit per minute and covers desktop capture → transcription → bilingual minutes, plus any historical recordings you upload. The live in-meeting Advisor costs 4 credits per minute — it is our most expensive item, which is why the rate is visible instead of hidden. Cross-meeting questions are 5 credits each and cloud OCR fallback is 1 credit per page; on-device OCR in the desktop app is free and unmetered. Credits included with your plan are granted monthly and do not roll over; credits bought in a pack do not expire. Multi-seat plans pool them across the workspace. See the pricing page for the per-plan allowances.

Because what Professional sells is “a team’s meetings become an organization you can query”, and organizational memory only means anything when it spans people and seats — a one-seat Professional plan would be a contradiction. At 3 seats that is $26.67 per seat; extra seats are $28/mo with a hard cap of 25, so a team of 10 is $80 + 7×$28 = $276/mo. That per-seat number lands squarely inside the price band of comparable team plans — and nobody in that band gives you team-wide live in-meeting advice.

Yes — and that is the design, not a hole we forgot to close. A seat is a recording seat: it buys the right to have the meetings you personally attend captured, transcribed and analysed. The people reading the minutes are Guests: free, unlimited and never downgraded, scoped to the single meeting explicitly shared with them. The minutes already exist; one more reader adds no recognition or inference cost. Gong, Avoma, Granola, Circleback and tl;dv all do the same — charging readers is the strange choice.

No — and this is not a policy rule, it is physics. Desktop capture records only the audio your own machine can hear: to record a meeting, you have to actually be in it. One seat is one calendar, and one person’s time has an upper bound; concurrent capture is also 1 stream per seat, so you cannot be in two meetings at once. Products that send a bot into the call are the ones that need a back-office switch saying “no simultaneous recordings”. We don’t — not joining the call is the gate.

What expires is only the cloud copy of the original audio. Text evidence — bilingual quotes, timecodes and the bilingual minutes — is kept forever on every plan; the evidence links still open, there is simply no audio left to play. The original audio on your own machine is not governed by the cloud audio retention period: it stays on your own drive until you delete it yourself — we never rotate it, never clean it up, and cannot touch it. Two weeks before anything expires, the Monday digest lists every meeting expiring in the next 14 days in a single email — we never send one email per meeting.

Never. Storage state is never a precondition for meeting capture — that is an assertion written into the architecture, not a reassurance. Knowledge-base space is a fence, and it only governs the files you upload: when it is full, only new uploads stop. Existing files stay readable, searchable, citable and exportable — we never delete your files — and meeting capture, transcription and bilingual minutes are entirely unaffected. A fence takes no processing pack: when it is full you clean up, or you move up a plan (moving up raises the fence, it does not buy an allowance).

Because resolution time is not a quantity we control, and promising it would be a lie. How long a ticket takes depends on whether it is a configuration issue, a bug of ours, or an upstream vendor outage — the only thing we control is how long before a human actually sees it and answers you. So we commit to a first-response target only, and no plan commits to a resolution time. By the same logic these are targets, not guarantees, and a missed target produces no service credit, refund or other remedy — the industry attaches credits to availability, not to response clocks, because a response-clock payout bends the support team’s incentive toward firing off a holding reply to stop the bleeding. We publish the P1 attainment rate, not an average: averages get diluted by P3 volume and hide exactly the P1 failures that matter. Support hours are UTC 01:00–10:00, Monday to Friday; tickets filed outside them start the clock at the next window, and the clock pauses while we wait on your reply. Per-plan targets and all conditions are on the pricing page and in the Terms.

Probably not — our support day starts when yours ends (UTC 01:00–10:00, Monday to Friday). If your team spans time zones that is not necessarily bad news: file a P1 during your working hours and, typically, the reply is waiting for you when your next working day begins, instead of eating the hours you needed for meetings. Platform-wide incidents are a different matter — those are 24/7 on-call plus a status page, not a per-ticket response clock.

Meetings are private to you by default. You can share minutes with workspace members per meeting, with role-based permissions. Org-memory search respects the same permissions — everyone can only find meetings they are allowed to see.

Yes. External sharing creates a read-only link with an expiry and access scope you control, revocable anytime; every decision in a shared minute still carries its evidence link.