The meeting ends.
The page is ready.

Two obligations, each within a week. Since 1 July 2022 the compte rendu has been replaced by publication of the list of adopted deliberations, with their subject and date (article L2121-25 of the CGCT). And once approved, the procès-verbal must be published on the commune's website and stay freely accessible there (article L2121-15). One page satisfies both and gives a resident something worth opening.

No, though it helps. Without one, segmentation works from what is said in the room and the titles are the ones the chair announces. With one, items are attached to their reference number and carry their official wording. PDF, DOCX or plain text, it does not matter which.

Nowhere. Everything is computed on the machine that processes the session: no upload, no account, no third-party service, so there is no processor to vet and no data processing agreement to sign. The offline flag makes network access impossible outright. If you explicitly pick a remote summary engine, that does send the transcript to a third party, and it is refused the moment offline mode is requested.

No, and the published page says so itself: only the minutes approved by the assembly are authoritative. BW Minutes produces the timecoded chapter list, the summaries and the list of deliberations with their vote outcome. That saves most of the drafting time and makes the video navigable, and it is not a document that binds the organisation.

They come from rules rather than a language model, and every result keeps the exact sentence that produced it with its timecode. A clerk clicks and hears what produced “adopted unanimously”. Being checkable in one click is what makes them usable, and it is a stronger position than a claim of infallibility we could not stand behind. Counts are read when they are spoken, for example “15 for, 2 against, 2 abstentions”. Vote detection is French only today, see Languages above.

No. By default it carries no logo, no product name, no link back to us, not even a generator meta tag. The one fixed line is the provenance statement, which a machine-written document owes its readers. If you are happy to credit us, an option adds it beside that line.

Yes, by one of three routes, because content management systems vary wildly in what they will accept. If yours allows an HTML upload, the file goes straight in. If it refuses one, which is common, embed it in an iframe: it reports its own height to the host page, so it sizes itself. And if you would rather not touch either, we publish the page and give you a single line to paste, on your own domain if you want one. Deep links work in every case, so a news article can point straight at the seventh item of the meeting of 24 June. The file stays yours whichever route you take: move it somewhere else later and it keeps working.

An Apple Silicon Mac is the fast path: a three-hour sitting takes fifteen to twenty-two minutes there. A machine without that acceleration works too, more slowly. Installation is a signed macOS installer.

Take the smallest plan and run your own meetings through it. If it is not for you, cancel before it renews. There is no crippled demonstration build and no separate trial to request, which also means nothing to keep re-installing.

It validates periodically and sends one number: how many meetings you have exported. No titles, no audio, no transcript, no client names. The audio itself never leaves your machine, which is the part that matters to the collectivité you are working for. If the validation service is unreachable, processing carries on and the count reconciles at the next successful check.

Yes. The plans are open to anyone, and a commune holding six to twelve sessions a year sits comfortably inside the smallest one. If your finance department can issue a bon de commande but not sign a recurring engagement, write to us and we will sell you a perpetual licence for your own assembly's sessions instead.