Security and trust

What a board can check before uploading a single document: how an answer is made, where the data lives, who can read it, and how long it is kept.

How an answer is made

An answer from Savoir is an extract of the community’s documents, with the place it came from beside it.

Cited, or nothing
Every answer names the document and the section it came from. An answer with no source is not shown.
The Civil Code in a group of its own
In Québec the Civil Code’s articles are cited apart, under the legal-information notice. They are never mixed into the community’s own documents.
It says when it does not know
When the documents do not answer, Savoir says so and sends the question to the board instead of guessing.

None of this is an option on a plan: it is the way the application is built.

Encrypted in transit
Everything that travels between a browser, the application and the database goes over HTTPS.
A private store, opened by a signed link
Uploaded files are kept in a private store. They open only through a signed, temporary link made for the person entitled to read them.
One community never reads the one next door
Every row and every file carries its community’s id, and the database refuses any read that would cross that boundary.
A Canadian region in production
In production, a community’s documents and the questions asked of them stay in a Canadian region.

Three roles, one way in, and a withdrawal of rights that takes effect at once.

Three roles, held as access groups
Admin, manager and member. Each role is an access group whose rights are granted key by key, and an administrator adjusts them from the console.
You come in by a link sent to your address
Nobody chooses a password: you sign in through a magic link sent to your address, and where a deployment enables them, Google and Microsoft stand beside it as a second door.
Taking rights away ends the sessions
When a board takes somebody’s rights away, it can end their open sessions in the same gesture, rather than waiting for their token to expire.

These windows are rows in a table of the database, applied every night. They are not intentions.

What the product keeps, and for how long
What is kept	For how long
The trail of changes made in the console	24 months
A member’s questions and their answers, counted from the last message in the thread	24 months
The anti-spam counter behind this site’s public forms	1 day
The service checks behind this site’s status page	90 days
An unconfirmed or ended subscription to the monthly guide	30 days

Two cookies. That is all.

Your answer to the question
The site-consent cookie holds your answer to the notice, for a year, so that the question is asked once rather than on every page.
The language you are reading in
The site-locale cookie holds the language of the page you are on, for a year, and it is written only if you said yes.
Visits, counted with no cookie
Visits are counted page by page, with no cookie, no IP address and no identifier. No advertising cookie, no tracker, nothing third-party.

The four services this application’s code talks to, and no others.

Savoir’s subprocessors: what they do and where they are
Service	What it does	Where it is
Supabase	The database, the accounts and the file store	Canada in production, as the deployment names it
Resend	Sending the product’s e-mails	United States
Engine	Reading a community’s documents and composing the answers	As named in the data-processing agreement
Commander	Deploying the application and receiving its crash reports	As named in the data-processing agreement

List verified on September 7, 2026.

This list is kept by a person, and the data-processing agreement names it in full.

The data-processing agreement and the full subprocessor list are had by writing. The subject and the first sentence are filled in for you.

These practices are aligned with PIPEDA and with Québec’s Law 25.

Upload your documents and see, in a few minutes, what Savoir answers to the questions your board gets every month.