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) | Section | What it means for your team's knowledge |
|---|---|---|
| Governance policies and a designated privacy officer (RPRP) | s. 3.1 & 3.2 | Define who manages workspace permissions, who reviews captured procedures and how long call recaps or logs are kept |
| Privacy impact assessment (PIA) for IT system acquisition | s. 3.3 | Assess the sensitivity and volume of personal information likely to appear in your procedures and calls before rollout |
| Cross-border disclosure outside Quebec | s. 17 | Complete a PIA and sign a written agreement whenever a subprocessor handles personal information outside Quebec |
| Written service-provider contract | s. 18.3 | Set out security measures in writing, restrict use strictly to delivering the service, bar post-contract retention and require prompt breach notice |
| Destruction, access and rectification | s. 23, 27–32 | Be 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
- 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.
- 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.
- 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:
| Criterion | Shared SaaS (Pro & Growth) | Option 1: Dedicated sovereign cloud (Montréal) | Option 2: On your cloud — BYOC (licensed) |
|---|---|---|---|
| Content hosting location | Google Cloud Montréal + MongoDB Atlas Canada | Dedicated Google Cloud project and database in Montréal (northamerica-northeast1) | Your own Google Cloud account (Montréal or chosen region) |
| Database isolation | Strict logical isolation per workspace (tenantId + projectId) | 100% dedicated single-tenant database | Database deployed inside your own cloud environment |
| AI keys and processing | Skillztank commercial API keys (no training; Google API transit) | Isolated credentials pinned to regional Canadian endpoints | Your own Vertex AI / Speech-to-Text keys under your Google contract |
| Operations and updates | Managed continuously by Skillztank | Managed and scheduled by Skillztank | Deployed by your IT team from our signed versioned releases |
| Cloud infrastructure bill | Included in your Skillztank subscription | Included in your annual dedicated contract | Billed directly to you by Google Cloud, separate from the licence |
| Skillztank staff access | No customer super-admin impersonation; shared infra operations | Contractually governed infrastructure operations under Law 25 | Zero network or data access (unless you open a support session) |
| Law 25 (s. 17) posture | PIA covering subprocessors listed in the security brief | Maximum Quebec residency in a managed single-tenant environment | Zero disclosure of personal information to Skillztank Inc. |
| Typical organisation | Growing SMBs, franchises, private schools and educators | Professional orders, regulated networks without dedicated DevOps | Large enterprises, public institutions, financial services |
| Pricing | $79 to $249 CAD / mo (billed annually) | Annual contract on quote | Annual 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)
- What personal information will actually enter our workspace? Strictly internal procedures recorded on dummy accounts, or live client/member calls summarised by AI Scribe?
- 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).
- What retention rules apply to call summaries and checklist logs? Decide who in your organisation periodically purges outdated session recaps.
- 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).
- 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
- 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.
- Do we mandate customer-managed encryption keys (CMEK) and direct SIEM log streaming? Both requirements point directly to Option 2 (BYOC).
- Which identity provider do we run (Microsoft Entra ID, Google Workspace, Okta)? Confirm SSO federation requirements and group-mapping rules up front.
- 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.
- 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.







