White paper

Security and privacy: where your data lives and who processes it

Hosting, AI processing, isolation between workspaces, access: the essentials in a few pages, for you and for your IT lead.

5 min read
Two-voice conversation · Synthetic voices2:38
Conversation: Security and privacy

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

0:002:38
Read the full conversation

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

Julie

Whenever an executive or an IT lead looks at Skillztank, the first question is almost always the same: where does our workspace data actually live?

Marc

It runs on Google Cloud and MongoDB Atlas in Canada, in the Montréal region. Your knowledge pages, paths, checklists, and media files are encrypted in transit over TLS and encrypted at rest. And when an organization needs physical or contractual separation, we offer either a dedicated isolated instance in Montréal or deployment right inside your own Google Cloud account.

Julie

Second big question: what does the AI actually see, and is customer content ever used to train AI models?

Marc

Never. Customer data is never used to train models. AI processing only runs when a user triggers an explicit feature—structuring a voice recording, summarizing a call with the AI Scribe, translating a page, or generating a voice-over. Those requests go through the Google Gemini API and Google Cloud Speech-to-Text under commercial data-protection terms.

Julie

On the standard cloud platform, how do you make sure one organization's workspace stays strictly isolated from every other customer?

Marc

Tenant isolation is enforced directly at the repository layer. Every database read, search, and write automatically scopes to your workspace's tenant and project identifiers rather than relying on manual query filters. And for larger networks or enterprise organizations, you can move to a dedicated isolated database.

Julie

How do sign-in and permissions work inside a team?

Marc

Authentication is handled through Firebase Authentication using email and password or Google sign-in, with enterprise SSO available for organizations that require centralized sign-in. Inside your workspace, three clear roles—Administrator, Content Creator, and Learner—combine with group and item-level access controls so people only see what pertains to their job.

Julie

Which subprocessors touch data across the stack?

Marc

Just five, listed in the table right below: Google Cloud for hosting and storage, MongoDB Atlas for the database, Firebase Authentication for sign-in, Google Gemini and Speech-to-Text for AI features, and Stripe for billing, so payment card numbers never touch our servers.

Julie

What if we ever need to export or remove workspace content?

Marc

Workspace administrators stay in full control of their content, user access, and deletions at all times, without lock-in.

Julie

And if an IT or security reviewer needs the written brief?

Marc

Every section—hosting, AI boundaries, tenant isolation, roles, and subprocessors—is right below on this page. You can print or save it as a PDF in one click, or write to our team at the bottom with your specific security questions.

In short

  • Your workspace's knowledge pages, paths, checklists and media files are hosted in Canada, on Google Cloud (Montréal region, northamerica-northeast1) and MongoDB Atlas (Canada).
  • User sign-in credentials (email address, encrypted password, Google sign-in) are handled by Firebase Authentication, a global Google service.
  • AI features (voice structuring, Show & Tell, translation, voice-over, AI Scribe) rely on the Google Gemini API and Google Cloud Speech-to-Text: your data is never used to train AI models.
  • Every workspace is isolated at the data-access layer (automatic filtering by workspace and project identifier on every query), with TLS encryption in transit and encryption at rest.
  • For stricter sovereignty requirements, we deploy a dedicated single-tenant instance in Montréal or install Skillztank directly inside your own Google Cloud account (BYOC).

This brief describes Skillztank's actual production architecture as of November 19, 2026, without claiming any external certification not yet held. For detailed answers to your IT security questionnaire or a written data-processing agreement, write to us at support@skillztank.com.

Where your data is hosted

In Canada for your content and media. The Skillztank web application, real-time media server and uploaded media files (screenshots, audio or video recordings, narrated voice-over tracks) run on Google Cloud in the Montréal region (northamerica-northeast1). Your structured workspace data (knowledge pages, learning paths, quizzes, /plan checklists, completion logs) is hosted in Canada on MongoDB Atlas.

Sign-in accounts are the exception. Identity verification at login (email address, hashed password, Google sign-in token) is managed by Google Firebase Authentication, a global Google service whose infrastructure is not restricted to Canada.

Two higher isolation tiers. Depending on your internal governance or regulatory rules, you can move from our Canadian shared platform to dedicated infrastructure:

ComponentShared platform (Pro, Growth, Education)Dedicated sovereign cloud (Montréal)On your cloud, under licence (BYOC)
Application and mediaGoogle Cloud, Montréal (northamerica-northeast1)Isolated Google Cloud project in Montréal, managed by SkillztankYour own Google Cloud account and VPC network
DatabaseMongoDB Atlas, Canada region (logical isolation)Dedicated, isolated database in MontréalDatabase deployed inside your cloud environment
User sign-inFirebase Authentication (global Google service)Firebase Authentication or enterprise SSOYour identity provider / SSO and IAM policies
Subscription billingStripe (card numbers stay on Stripe)Annual contract invoicingAnnual offline licence

For a full comparison of both sovereign options under Quebec privacy law, read our white paper Law 25 and sovereignty: dedicated cloud or your own cloud.

What the AI sees, and what it does not keep

Triggered only by explicit user action. Reading a knowledge page, completing a quiz or ticking a checklist in /plan sends nothing to a generative model. Content passes through AI only when a creator triggers a specific assistive action:

  • Voice capture: your spoken walkthrough is transcribed by Google Cloud Speech-to-Text, then organised into titled sections by the Google Gemini API.
  • Chrome Show & Tell: captured workflow steps and your spoken commentary are used to draft the illustrated step-by-step procedure.
  • EN/FR translation and voice-over: the text of the knowledge page is sent to the Google Gemini API to generate the translated version or natural audio narration.
  • Video calls with AI Scribe and Whisper: once participants are informed and AI Scribe is turned on, live speech is transcribed and summarised into a structured recap; Whisper surfaces context strictly from the authorised workspace.

Zero model training on customer data. Neither Skillztank Inc. nor Google uses your knowledge pages, screenshots, recordings or call summaries to train or improve artificial intelligence models. Skillztank calls Google's commercial APIs (Gemini API and Cloud Speech-to-Text), which are governed by Google Cloud's commercial no-training commitments.

A human always reviews before publishing. Whether an operations lead at Café Boréal captures a POS refund workflow or an independent language coach summarises a live session, the AI produces a structured draft: the creator reviews it, adjusts trade-specific wording, and chooses when to publish or share.

Isolation between workspaces

Logical isolation enforced on every query. On the shared platform, every workspace carries a unique tenant identifier (tenantId) and each team space carries a project identifier (projectId). On every authenticated request, the backend binds that verified context in isolated request memory and injects it automatically at the repository layer: no read, vector search, write or deletion query can cross into another customer's workspace.

Dedicated database or customer perimeter. On the Enterprise & Franchise plan and on Dedicated Sovereign Cloud, your organisation gets its own isolated database. Under BYOC, the entire stack runs inside your Google Cloud project: zero operational data or metadata leaves your perimeter.

Protection layerWhat is in place in Skillztank
Data in transitHTTPS (TLS 1.2+) across the web browser, Chrome extension, real-time WebSocket streams and APIs
Data at restEncryption at rest on the database (MongoDB Atlas) and media buckets (Google Cloud Storage)
Application secretsIntegration tokens and sensitive credentials encrypted before storage; zero plaintext passwords
Media file accessGated by workspace authentication and short-lived signed URLs

Access, roles and sign-in

Sign-in options. Team members and learners sign in with an email address and password or with their Google account. Enterprise single sign-on (SSO) is available on the Enterprise & Franchise plan and on sovereign deployments.

Three clear workspace roles. Permissions separate workspace administration, authoring and day-to-day learning or execution:

Workspace roleWhat the person can doWhat they cannot do
AdministratorManage workspace settings, invite or remove members, organise groups, manage billing and oversee all contentAccess any other organisation's workspace
Content creatorCreate, record, translate and update knowledge pages, paths, /plan checklists and Scribe recaps in authorised spacesChange billing or global workspace security settings
LearnerRead assigned knowledge pages and paths, take quizzes, tick /plan checklists and join invited video callsEdit published procedures, view restricted group folders or manage members

Per-content and per-group permissions. Inside a single workspace, you control visibility by group or branch—for instance separating barista opening checklists at Café Boréal from manager-only audit procedures. See the guide Invite your team or your learners for the exact steps in the interface.

Control and reversibility. Administrators can revoke a member's access in one click or delete knowledge pages and call summaries at any time. Ending a subscription never locks you out abruptly: your workspace remains accessible to administrators so you can export or purge your data.

Our subprocessors

Skillztank relies on a focused set of infrastructure providers to deliver the service:

SubprocessorRole for SkillztankProcessing location
Google CloudWeb application hosting, real-time media server and media file storageCanada (Montréal, northamerica-northeast1)
MongoDB AtlasOperational database hosting and automated backupsCanada
Google Firebase AuthenticationUser account sign-in and session token verificationGlobal service (Google)
Google (Gemini API and Cloud Speech-to-Text)Speech transcription, knowledge structuring, EN/FR translation, voice-over and Scribe summaries (no model training)United States / global on shared SaaS; Montréal region configurable on dedicated / BYOC
StripeSubscription billing and AI credit top-ups; payment card numbers never pass through SkillztankUnited States / global

Under Quebec's Law 25 (section 18.3), Skillztank Inc. processes entrusted information solely to deliver the service and notifies your privacy officer without delay in the event of a confidentiality incident. To report a security issue, request our written data-processing agreement or complete your IT review, write to support@skillztank.com.

Try it with your own team

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

Start the free trial →