TrustSecurity & data ownership

You decide where it runs.We stay inside.

A company brain holds what a company knows. So LectureHub runs where you decide — an EU region, a single tenant, or your own cloud — on a model you choose, and never learns from your data. This page says exactly what that means, in the terms your IT team will ask about.

  • Tenant isolationalways
  • Single tenanton request
  • Your own cloudon request
  • The modelshared, dedicated, or yours inside
  • EU region by default · US available
  • Nothing you put in the hub trains a model — ours or anyone else's.
Deployment boundary

What crosses the line. What never does.

Your people, your hub, the model — and what travels between them. Everything on this page comes back to this line.

  1. 01

    Your people

    Sign in with email, Google or your SSO. Each person sees only what their role and team allow — permissions inherit from your identity provider.

  2. 02The boundary

    Your hub

    Tenant-isolated, on its own address. EU region by default, US available; single tenant or your own cloud on request. The assistant answers only from sources you admitted.

  3. 03

    The model

    A shared model, a dedicated instance, or a private LLM you control. Every answer cites its source. Nothing you put in the hub trains a model — ours or anyone else's.

Never crosses it
  • Your content into anyone's training data
  • One tenant's knowledge into another tenant's answers
  • Card details onto our servers — billing runs on Stripe's hosted checkout
The model

Three ways to run the model. You pick.

In every one, your content trains nothing and every answer cites its source. What differs is where the model sits — and so what leaves your boundary.

  1. 01

    Shared model

    Our managed model, tenant-isolated. The fastest way to start.

    What leaves your boundary

    The question and the approved passages needed to answer it. Nothing is kept for training.

  2. 02

    Dedicated instance

    A model instance that serves your hub and no one else's.

    What leaves your boundary

    The same, to an instance that serves only you.

  3. 03

    Your own LLM

    Bring the LLM you already run — in your cloud or ours. The hub talks to it and to nothing else.

    What leaves your boundary

    Nothing. The model runs where you run it.

Controls

Every control, with its status.

Four words, and what they mean. Nothing is listed as done before it is; the day a status changes, this page changes with it.

Reviewed 2026-09-08
  • Always

    How the product works.

    3 controls

  • Available

    On every hub.

    8 controls

  • On request

    Set up for you.

    6 controls

  • Roadmap

    Not done yet.

    1 control

Data & tenancy

No training on your data
Your content never trains a model — ours or a provider's.
Always
Tenant isolation
Your content is isolated by tenant; each hub lives on its own address.
Always
Approved sources only
The assistant answers from the sources you explicitly admitted to the hub.
Available
Source citations
Every answer names the document, recording or person it came from.
Available
Configurable retention
Retention windows for prompts, answers and uploaded content.
Available

Hosting

EU hosting
EU region by default; US region available.
Available
Single-tenant deployment
Your hub on infrastructure that serves no other customer.
On request
Your own cloud
Bring-your-own-cloud deployment.
On request

Identity & access

Roles and permissions
Granular access by team, role and content collection.
Available
Email and Google sign-in
Standard sign-in for every hub.
Available
SAML single sign-on
Sign-in through your identity provider.
On request
SCIM provisioning
Accounts created and removed from your directory.
On request

Model

Dedicated model instance
A model instance serving only your hub.
On request
Private LLM you control
Your own LLM, in your cloud or ours.
On request
MCP access for outside assistants
Compatible assistants and agents read the same hub. Permissions are enforced here, not by the caller: the asker's identity travels with the request and only what they may see comes back.
Available

Compliance

Designed around GDPR
Data-processing terms are part of every evaluation.
Available
SOC 2 / ISO 27001
Listed on this page the day they are verified, not before.
Roadmap
Card data
Never touches LectureHub: payment runs on Stripe's hosted checkout.
Always
During evaluation

Current materials, on request. Claims only once verified.

We share the current security overview, data-processing terms and hosting details with prospects during evaluation, under NDA where needed. Certification and audit status appear on this page only after they are verified — never before.

Answered in writing

Not stated on this page, answered in writing during your review:

  1. 01Encryption at rest and key management
  2. 02Backup, restore and recovery objectives
  3. 03Uptime history and incident communication
  4. 04Subprocessors and where they run
  5. 05Penetration testing and remediation
  6. 06Export and deletion at the end of a contract
Your questionnaire

Send your security questionnaire with the review request. We complete it as part of the evaluation, and the answers become part of your contract.

Send it with the review request
Before you buy

The questions your IT team will ask.

Where does our data live?
In an EU region by default; a US region is available. Single-tenant deployment and hosting in your own cloud are available on request.
Does the model learn from our data?
No. On any plan, with any model option. Your content is never used to train a model.
What does the model actually see?
The question and the approved passages needed to answer it. Only sources you admitted to the hub, and every answer cites them.
Can we use our own LLM?
Yes. Run on our shared model, a dedicated instance, or a private LLM you control — in your cloud or ours. The private options come with AI Knowledge Hub and Enterprise.
Who can see what?
Permissions are granular by team, role and content collection, and inherit from your identity provider.
How do people sign in?
Email and Google sign-in on every hub. SAML single sign-on and SCIM provisioning on request.
How long do you keep prompts and answers?
As long as you decide. Retention windows for prompts, answers and uploaded content are configurable.
Are you certified?
LectureHub is designed around GDPR. SOC 2 and ISO 27001 are on the roadmap and will appear on this page only once verified. Ask for the current security overview during your review.
Security review

Tell us where it has to run.

Region, tenancy, model, identity — tell us your requirements and we come back with how LectureHub meets them, in writing.

Report a security issue

Found something? Send suspected vulnerabilities and security concerns straight to us. We acknowledge every report.

Report through the contact form