Who the firm receives, when, and about what: a lawyer's or notary's diary is a direct extension of professional secrecy. Booking the room “case X — client Y, Thursday 2 p.m.” in a third-party cloud means entrusting that information to one more provider.
Your sector's context
A schedule hosted by a third party is one more third-party access to document in your risk analysis. Removing it at the source is simpler than supervising it.
Regulatory framework
The obligations specific to your sector.
Lawyers' professional secrecy
In France, professional secrecy covers consultations and correspondence in all matters (Article 66-5 of the law of 31 December 1971); breaching it is a criminal offence (Article 226-13 of the French Criminal Code). Appointment metadata — client identities, frequency, subject matter — is in practice part of that scope.
Switzerland: Article 321 of the Criminal Code
Swiss lawyers and notaries are bound by professional secrecy under Article 321 of the Criminal Code. The firm's choice of tools follows from it: every cloud service that sees appointments pass through is one more link to assess.
Professional ethics and outsourcing
Professional rules (the RIN in France, CCBE recommendations in Europe) require lawyers to ensure confidentiality whenever technical providers are involved. A scheduling tool that holds no schedules radically simplifies that due diligence.
On the ground
Three typical use cases.
Client rooms and signing rooms
Confidential appointments are booked in your own calendars — the subject of the appointment and the client's name pass through no external service.
The firm's shared resources
Video-conference room, hearing equipment, vehicle: each resource is a bookable calendar with no per-unit cost, and requests are approved by your partners or your office manager.
Internal confidentiality
Every account is personal, and every activated device is visible and revocable in one click — useful when a colleague leaves or when internal information barriers between cases are required.
For your compliance officer: on the vendor's side there are only the organisation's account, the accounts' e-mail addresses and the hashed device fingerprints — neither your appointments nor your clients. The compliance sheet in the customer area documents that exact scope for your due diligence.
The shortest due diligence is the absence of a third party
Governing a provider that sees the firm's appointments requires clauses, audits and trust. Doing without one is shorter: booking the firm's rooms remains an entry in your own calendars, protected by the same measures as your files. The licence portal, for its part, knows only the firm's name and the accounts' e-mail addresses — not your clients, not your matters, not your hours. And the day the firm changes tools, there is nothing to retrieve or have erased: the schedules never left its calendars.
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.
Cookies: the bare minimum — and nothing without your consent.
This site only uses cookies that are strictly necessary for it to work (session, security). With your consent, we also enable anonymized, self-hosted audience measurement (Matomo). No advertising cookies, no third-party trackers.
Cookie policy