Law 25 for municipalities: what Beluga does for you.

Law 25 obligations for municipalities and non-profits, and how Beluga addresses them: hosting in Québec, audit log, legal hold, access requests answered within 30 days.

February 27, 2026 · The Beluga team · Compliance

Law 25 is in force. For a municipality or a non-profit, it imposes concrete, verifiable obligations. Here are the main ones and how Beluga addresses them, separating what we do for you from what remains your responsibility.

1. Knowing where your data is

Beluga: in Québec, on servers we own. One answer, with no exception for everyday use. The processing activities that leave Québec (payments through Stripe, bot protection at sign-up through hCaptcha, Convo notifications in Element X through Element, transcription by Mistral AI, in the European Union, if the host asks for it on a recorded meeting) are described on our Subprocessors page.

2. Controlling who can access it

Beluga: Keycloak authentication with 2FA and passkeys, roles per organization (owner, administrator, member, viewer), an audit log in the administration console, and an organization-wide mandatory 2FA policy if you decide to turn it on.

3. Suspending deletion when needed

Beluga: legal hold to suspend deletion during a proceeding.

4. Answering access and deletion requests

Beluga: your users access their data through open standards (IMAP, CalDAV, CardDAV, vCard and iCalendar exports). For formal requests, our person in charge of the protection of personal information answers within 30 days, and yours stays in control of your own obligations.

What Beluga does not replace

Appointing your own person in charge, training your team, setting your retention schedules: these obligations remain yours. No provider can carry them for you. Be wary of those who claim otherwise.

All posts