FR EN

Consent documents

A consent document is the article 8 disclosure the person concerned reads and consents under. It is the text that makes consent informed: it states which information is collected, for which purposes, by which means, how long it is retained, how to withdraw consent, and to whom the information may be communicated.

Anatomy of a document

A document carries a code, a name, a version, an effective date (date d'entree en vigueur), a status, and a list of items: the catalog cells it groups.

The article 8 disclosure fields are bilingual (French and English):

  • Purposes (fins): the purposes the information is collected for.
  • Means of collection (moyens de collecte, article 8 para. 2): the means by which the information is collected.
  • Categories: the categories of personal information involved.
  • Retention (conservation): how long and how the information is retained.
  • Withdrawal of consent (retrait du consentement): how the person concerned can withdraw consent.
  • Recipients (destinataires): to whom the information may be communicated.
  • Cross-border communication (communication hors Quebec): communication of information outside Quebec, where applicable (this field may be null when there is no cross-border communication).
  • Rights: the rights of the person concerned.
  • Responsible person (responsable): the name and contact details of the privacy officer.
  • Automated decision: a flag and a text, when the disclosure covers a decision based exclusively on automated processing.

Editable draft, immutable published version

A document has two states that matter. A draft (DRAFT) is editable: until it is published, you freely adjust its fields and items. A published version (PUBLISHED) is immutable.

To change a published document you do not reopen it: you create a new version, which clones the published version into a new draft. You edit that draft, then publish it in turn. The old version stays intact, frozen as it was for the people who consented under it.

Why immutability matters

A consent is given under a precise version of the disclosure. If that version could change after the fact, the company could no longer demonstrate what the person actually consented to. Freezing the published version is what makes the consent provable after the fact.

Publishing: material or minor change

When publishing, the company classifies the change as material (MATERIAL) or minor (MINOR). The default is material.

A material change opens a re-consent campaign: the affected persons are invited to consent again, on the new version.

Re-consent only reaches people who log in

A re-consent campaign can only prompt a person when they log in to the portal. It has to be said plainly: an existing consent stays valid for its original scope until it is re-consented or withdrawn. Publishing a new version does not retroactively revoke consents in effect and does not upgrade them on its own.

Assisted generation of a draft

The app can generate a draft disclosure from the structured sources you have already entered:

  • the grouped catalog cells feed the purposes and the categories;
  • the retention rules feed retention;
  • cross-border communication and governance feed the communication section;
  • the privacy officer feeds the contact details.

Generation is gated, not one-click magic. It hard-blocks when the sources are incomplete and shows you the list of missing sources to fill before you can proceed. Recipients stays a manual entry. And above all, a human review and a review by legal counsel remain mandatory before any publish.

A template, to review with counsel

The generated draft is a template, not legal advice. It assembles what you declared; it does not judge whether your disclosure satisfies the law in your particular case. Have it reviewed by legal counsel before publishing. This documentation is guidance; it is not a substitute for legal advice.

PDF and IPFS anchoring

A published version can be downloaded as a PDF on the company side, and it is pinned to IPFS. Its CID (content identifier) is surfaced on the document detail page, with a way to copy it, a gateway link, and an anchor-status pill: anchored (anchored), pending (pending), or not pinned (notPinned).

The CID is a public verifiable copy, never proof of consent

The CID is a public, verifiable copy of the disclosure: anyone can retrieve the exact document the person concerned read and confirm it has not changed. It is never proof that a person consented, and it contains no personal information. Proof of consent is a distinct artifact, described in Core concepts. The CID proves what could be consented to, not who consented.

For the detail of pinning, CID computation, and document integrity, see IPFS document integrity.

Next