White paper · Business

Law 25 and sovereignty: dedicated cloud or your own cloud

What Quebec's Law 25 asks for your team's knowledge, and the two ways to stay in control: a dedicated instance in Montréal, or an installation in your own Google Cloud account.

10 min read
Two-voice conversation · Synthetic voices4:49
Conversation: Law 25 and sovereignty

Two voices walk through the white paper, question by question, for those who prefer to listen.

0:004:49
Read the full conversation

Two-voice conversation generated with synthetic voices from the verified content on this page.

Julie

People often assume Québec's Law 25 only applies to customer CRMs or HR files. Why does an internal SOP and team knowledge platform fall squarely into that conversation?

Marc

Because real operational knowledge rarely stays abstract. When a team lead records a software walkthrough in Chrome using Show & Tell inside a live ERP or CRM, a client name or file number can appear in a screenshot. When you summarize an internal call with the AI Scribe, identifiable voices and discussions are processed. And in /plan checklists or onboarding paths, timestamped completions and quiz results tie directly to named employees.

Julie

What practical duties follow from that for leadership and for the organization's privacy officer?

Marc

Four practical things: knowing exactly where those records reside and which subprocessors touch them, restricting access by role, being able to export or delete records when needed, and—when data sensitivity or internal governance requires it—completing a Privacy Impact Assessment. For many growing SMBs, our standard Canadian workspace with repository-level tenant isolation fits comfortably. Regulated firms, professional orders, institutions, and large networks often need dedicated boundaries.

Julie

That brings us to the two sovereign deployment models in this white paper. Let's start with Option 1: the Dedicated Sovereign Cloud in Montréal. What gets isolated?

Marc

In Option 1, we provision an isolated Google Cloud project and a dedicated MongoDB database exclusively for your organization in Montréal—northamerica-northeast1. You don't share database clusters, media buckets, or compute services with any other tenant.

Julie

And who operates and updates that dedicated Montréal environment day to day?

Marc

Our team runs it end to end—monitoring, backups, security patches, and application updates. So your privacy officer gets clean single-tenant residency in Montréal, while your internal IT team doesn't have to take on cloud operations or deployment pipelines.

Julie

Now compare that with Option 2: Bring Your Own Cloud under an annual license—BYOC. When does an organization choose BYOC instead?

Marc

BYOC is built for organizations whose security policy states that no operational data, media asset, or AI prompt may ever leave their own cloud boundary. Using automated deployment scripts, Skillztank is installed directly inside your own Google Cloud account, behind your VPC network rules and your own IAM policies.

Julie

How do AI features and licensing work when everything runs inside the client's Google Cloud account?

Marc

You connect your own Google Gemini or Vertex AI and Speech-to-Text keys governed by your enterprise cloud agreement. The instance activates with a signed offline license key, so zero content, zero screenshots, and zero AI traffic ever transit through Skillztank infrastructure.

Julie

If an executive team and their IT director are weighing Option 1 against Option 2, what is the cleanest way to decide?

Marc

Look at three trade-offs: operations, cloud ownership, and update control. With Dedicated Sovereign Cloud in Montréal, we host, manage AI keys, and ship updates turnkey under a single enterprise agreement. With Licensed BYOC, your IT team owns the Google Cloud project under your direct Google Cloud agreement and controls the exact maintenance window for every release.

Julie

What questions should the IT lead and Privacy Officer walk through together before picking a deployment model?

Marc

Five questions settle almost every case: first, will screen captures or call summaries include client or citizen details? Second, do client contracts or regulations mandate a single-tenant database in Québec? Third, do we have an in-house Google Cloud and IAM team ready to run BYOC, or do we want managed hosting? Fourth, do we require internal change-management sign-off before updates go live? And fifth, what documentation does our Privacy Officer need for the Law 25 register or PIA?

Julie

Regardless of whether a team runs on standard Canadian cloud, Dedicated Montréal, or BYOC, what practical habits keep internal content clean under Law 25?

Marc

Three everyday habits prevent almost every unnecessary exposure: first, record Chrome Show & Tell walkthroughs using a test or demo account rather than a live customer record whenever possible; second, always let participants know before turning on the AI Scribe in a video call; and third, scope sensitive operational paths and checklists to the specific roles and groups that actually need them.

Julie

Where can listeners review the full side-by-side table and talk through their setup?

Marc

The comparison matrix and readiness checklist are right below on this page—you can print or save the full paper as a PDF, or reach out to our team at the bottom to scope a Dedicated Montréal or BYOC deployment with your IT and privacy leads.

In short

  • Even when a knowledge base is not meant to store HR or customer files, personal information regularly enters operational content: software screenshots, voices and faces on team calls, and employee completion timestamps.
  • In Quebec, Law 25 governs any project to acquire an information system that handles personal information—requiring a privacy impact assessment (PIA), a written service-provider contract, retention rules and oversight of cross-border processing.
  • For most SMBs and academies, our Canadian shared platform paired with a written data-processing agreement and clean capture habits satisfies day-to-day compliance needs.
  • For professional orders, public bodies, regulated firms and larger enterprises, we offer two sovereign architectures on quote: Dedicated Sovereign Cloud in Montréal (managed by our team) and Bring Your Own Cloud under licence (BYOC) inside your own Google Cloud account.
  • This paper explains both options in plain technical detail and gives your IT lead and privacy officer a practical decision checklist.

What Law 25 changes for your internal content

Organisations usually think of Quebec's Act respecting the protection of personal information in the private sector (modernised by Law 25) in connection with customer databases, payroll or health records. Yet as soon as an operational team documents how work gets done, personal information shows up in four common places:

  • Chrome Show & Tell screen captures: when a team lead records a workflow inside a CRM, ERP or POS (see the Show & Tell guide), a real customer's name, email address or order number can appear in screenshots unless the walkthrough uses a dummy profile.
  • Video calls and AI Scribe summaries: a team check-in or coaching call (see the AI Scribe guide) captures participants' voices, faces, spoken remarks and named action items.
  • Checklists in /plan and learning path logs: when a multi-location business like Café Boréal tracks opening routines or onboarding quizzes, each entry links an employee's name, branch and exact timestamp.
  • Internal escalation procedures: direct phone numbers, on-call contacts or role-specific instructions tied to identifiable staff members.

Whenever content identifies a natural person, Law 25 places clear duties on your organisation:

Obligation (Quebec Private Sector Act)SectionWhat it means for your team's knowledge
Governance policies and a designated privacy officer (RPRP)s. 3.1 & 3.2Define who manages workspace permissions, who reviews captured procedures and how long call recaps or logs are kept
Privacy impact assessment (PIA) for IT system acquisitions. 3.3Assess the sensitivity and volume of personal information likely to appear in your procedures and calls before rollout
Cross-border disclosure outside Quebecs. 17Complete a PIA and sign a written agreement whenever a subprocessor handles personal information outside Quebec
Written service-provider contracts. 18.3Set out security measures in writing, restrict use strictly to delivering the service, bar post-contract retention and require prompt breach notice
Destruction, access and rectifications. 23, 27–32Be able to locate, correct or delete a knowledge page, unredacted screenshot or call summary within the statutory 30-day window

Three practical habits regardless of hosting model

  1. Record software workflows on test accounts: when running Chrome Show & Tell on a business app, use a fictional customer record so real personal data never lands in step-by-step screenshots.
  2. Always announce AI Scribe before turning it on: inform participants at the start of a call, review the draft summary afterwards, and file only the operational decisions or learning takeaways worth keeping.
  3. Scope visibility by group: restrict sensitive procedures (finance, HR, quality audits) to the specific groups that need them rather than publishing workspace-wide.

When your regulatory mandate, client contracts or internal security posture further require zero shared databases or strict Quebec residency across every AI call, two sovereign deployment models are available.

Option 1: dedicated sovereign cloud, in Montréal

Dedicated Sovereign Cloud is built for regulated organisations that want single-tenant hardware and Quebec data residency without assigning an internal DevOps team to run Kubernetes clusters, databases and upgrades.

What we deploy exclusively for you

  • Isolated Google Cloud project in Montréal (northamerica-northeast1): your application containers, real-time media server and storage buckets run inside a dedicated Google Cloud project provisioned solely for your organisation in Montréal.
  • Dedicated, isolated database in Montréal: zero database clusters, collections or search indexes are shared with any other Skillztank customer. Your knowledge pages, paths, /plan checklists and logs live in your own isolated instance.
  • Regionalised AI endpoints: Gemini calls (via Vertex AI) and speech transcription are routed to regional Canadian endpoints where available, with zero model training on your content and zero commercial retention for model improvement.
  • Enterprise identity and white-label: SAML / OIDC single sign-on (SSO), your custom domain (for example knowledge.your-organisation.ca) and full brand customisation.

Day-to-day operations

Our engineering team provisions the infrastructure, applies security patches, monitors uptime, manages encrypted backups in Montréal and rolls out Skillztank updates on an agreed schedule with your IT lead. You get turnkey single-tenant sovereignty under an annual contract on quote, backed by a comprehensive Law 25 data-processing agreement.

Option 2: on your cloud, under licence (BYOC)

On your cloud, under licence (BYOC — Bring Your Own Cloud) meets the strictest enterprise and institutional security mandates: zero content, zero screenshots and zero audio streams ever leave your own cloud perimeter.

How deployment inside your perimeter works

  • Automated installation in your Google Cloud account: we deliver reproducible infrastructure scripts (Terraform and signed container images) to deploy the complete Skillztank stack directly inside a Google Cloud project owned by your organisation, in Montréal (northamerica-northeast1) or your chosen region.
  • Your own AI keys and cloud contracts: the instance connects directly to your organisation's own Google Cloud Vertex AI (Gemini) and Cloud Speech-to-Text credentials. Every AI call stays governed by your direct enterprise agreement, quotas and residency policies with Google Cloud.
  • Your VPC, encryption keys and audit logs: your IT security team controls the virtual private cloud (VPC), firewall rules, customer-managed encryption keys (CMEK / KMS), SSO identity provider and log forwarding into your internal SIEM.
  • Cryptographically signed offline licence key: your annual Skillztank software licence is verified locally via cryptographic signature. The application sends zero external telemetry, zero content and zero user lists back to Skillztank Inc.

Comparing the two options

The table below helps executives, IT leads and privacy officers compare our shared Canadian platform (see Business Pricing) with both sovereign deployment models:

CriterionShared SaaS (Pro & Growth)Option 1: Dedicated sovereign cloud (Montréal)Option 2: On your cloud — BYOC (licensed)
Content hosting locationGoogle Cloud Montréal + MongoDB Atlas CanadaDedicated Google Cloud project and database in Montréal (northamerica-northeast1)Your own Google Cloud account (Montréal or chosen region)
Database isolationStrict logical isolation per workspace (tenantId + projectId)100% dedicated single-tenant databaseDatabase deployed inside your own cloud environment
AI keys and processingSkillztank commercial API keys (no training; Google API transit)Isolated credentials pinned to regional Canadian endpointsYour own Vertex AI / Speech-to-Text keys under your Google contract
Operations and updatesManaged continuously by SkillztankManaged and scheduled by SkillztankDeployed by your IT team from our signed versioned releases
Cloud infrastructure billIncluded in your Skillztank subscriptionIncluded in your annual dedicated contractBilled directly to you by Google Cloud, separate from the licence
Skillztank staff accessNo customer super-admin impersonation; shared infra operationsContractually governed infrastructure operations under Law 25Zero network or data access (unless you open a support session)
Law 25 (s. 17) posturePIA covering subprocessors listed in the security briefMaximum Quebec residency in a managed single-tenant environmentZero disclosure of personal information to Skillztank Inc.
Typical organisationGrowing SMBs, franchises, private schools and educatorsProfessional orders, regulated networks without dedicated DevOpsLarge enterprises, public institutions, financial services
Pricing$79 to $249 CAD / mo (billed annually)Annual contract on quoteAnnual software licence on quote

Note: the Enterprise & Franchise plan ($399 / mo billed annually) serves as a bridge tier that already includes full white-labelling, SSO and a dedicated isolated database.

Questions to ask before choosing

Before deciding between our shared Canadian platform, Dedicated Sovereign Cloud in Montréal or licensed BYOC, review these ten questions with your privacy officer and IT lead:

For your privacy officer (RPRP)

  1. What personal information will actually enter our workspace? Strictly internal procedures recorded on dummy accounts, or live client/member calls summarised by AI Scribe?
  2. Do our internal policies or client contracts prohibit any cross-border AI processing outside Quebec? If so, choose Option 1 (regional Montréal endpoints) or Option 2 (BYOC under your own Vertex AI residency controls).
  3. What retention rules apply to call summaries and checklist logs? Decide who in your organisation periodically purges outdated session recaps.
  4. Which contractual schedules do we need for our Law 25 compliance file? (A section 18.3 data-protection agreement plus the subprocessor inventory in our Security and privacy brief).
  5. Who handles 30-day access or rectification requests? Name the workspace administrator responsible for locating, editing or deleting records tied to an individual.

For your IT and security lead

  1. Do we already operate Google Cloud with an internal team comfortable managing containers and databases? If yes, BYOC slots straight into your pipeline; if not, Dedicated Sovereign Cloud removes operational overhead.
  2. Do we mandate customer-managed encryption keys (CMEK) and direct SIEM log streaming? Both requirements point directly to Option 2 (BYOC).
  3. Which identity provider do we run (Microsoft Entra ID, Google Workspace, Okta)? Confirm SSO federation requirements and group-mapping rules up front.
  4. Can staff workstations install enterprise-managed Chrome extensions? Relevant if your teams plan to use Show & Tell capture and live Chrome GPS overlays on internal web apps.
  5. How do we govern software upgrades? Turnkey managed updates by Skillztank (Option 1) or internal staging sign-off before production rollout (Option 2).

Next step. Preparing a Law 25 privacy impact assessment or scoping a dedicated architecture? Write to contact@skillztank.com to schedule a direct architecture review with your IT lead and privacy officer.

Try it with your own team

Create your workspace in a few seconds and capture a first knowledge page today.

Start the free trial →