Room Flow
Room Flow
Public sector

Room booking for the public sector

Municipal halls, equipment pooled between departments, committee schedules: local authorities face a double constraint — sovereignty requirements now written in black and white, and budgets that rule out paying for each room or each building as yet another billed “resource”.

Your sector's context

In France, the “cloud au centre” doctrine, the SecNumCloud framework and the SREN law of 21 May 2024 govern public bodies' use of clouds subject to extraterritorial jurisdictions.

Regulatory framework

The obligations specific to your sector.

The “cloud au centre” doctrine

The circular of 5 July 2021, updated on 31 May 2023, requires French administrations to host sensitive data on SecNumCloud-qualified clouds, immune to extraterritorial legislation. A schedule that stays inside your information system never enters that debate: it simply is not outsourced.

SREN law of 21 May 2024

Law No. 2024-449 on securing and regulating the digital space tightens the rules on public bodies' use of clouds subject to non-European jurisdictions. Fewer outbound flows means fewer analyses to produce — and fewer dependencies to justify.

Simpler public procurement

A per-person software licence, with public pricing and no booking data hosted by the vendor: the tender file shrinks — no hosting annex and no reversibility plan for the schedules, they never leave the authority.

On the ground

Three typical use cases.

Municipal and community halls

Town hall, community centre, gymnasium: each hall is a calendar; requests from departments and associations go through your authorised staff (administrator role), who accept or decline.

Equipment pooled between departments

Projectors, vehicles, marquees, sound systems: unlimited resources, no inventory cost — pooling does not inflate the invoice.

Demonstrable sovereignty

The client is lean and verifiable: no trackers, no CDN, no hidden outbound calls — your technical teams can see it for themselves, in the spirit of digital public procurement.

For your DPO and your CISO: the vendor holds only the authority's account (organisation, e-mail addresses, licence, hashed device fingerprints). The record of processing shrinks accordingly — the compliance sheet in the customer area provides its exact, dated inventory.

By architecture, not by promise

What the architecture guarantees.

Your bookings stay with you

Schedules, attendees and bookings live in your Zimbra/CalDAV calendars and on your workstations — not with the vendor, not in a foreign cloud subject to extraterritorial laws.

The network goes down, your bookings don't

The licence is a signed certificate verified locally: the app keeps working without a connection, network outage included.

A lean, auditable client

No trackers, no embedded analytics, no CDN: what the app does can be verified — nothing has to be taken on faith.

These points describe the product's architecture, not a sector certification. They are not legal advice: have your compliance reviewed by a specialist. Content to be reviewed by a lawyer before publication.

Your cookie preferences

Choose what you allow. Your choice is stored for 6 months and can be changed at any time via “Manage cookies” in the footer.

Necessary Always on

Session, security (CSRF protection), and remembering your language and cookie choices. Without these, the site does not work.

Audience measurement (Matomo, self-hosted) Off by default

Anonymized visit statistics, processed on our own servers. No data shared with third parties, no ad profiling.