Governance & IP

Built for governed learning environments

SLAN is designed for academic and enterprise settings where course content, playbooks, and derived structures are proprietary.
Application data is stored in the EU. Governance policies are scoped per organization, with explicit permissions and review before release.

Discuss governance requirements How it works

THE PILLARS

Content ownership, access boundaries, and provenance

SLAN supports explicit permissions, cohort scoping, and careful handling of proprietary materials at every step.

Content ownership

Course materials remain owned by the professor or institution. Internal playbooks remain owned by the company.

Review before release

Every extracted framework and ThinkingPath is a proposal. Content owners review and approve before broad release.

Provenance

Where feasible, ground guidance in approved materials and surface which sources informed each output. Tracked per deployment.

Access control

Scope access by course, cohort, or organization

Deploy private, public, or restricted experiences as needed. Boundaries are configured at the assistant and ThinkingPath level.

Cohorts & scoping

Cohort management: Run multiple cohorts per course without duplicating structures.
Course- and cohort-scoped availability: Limit what learners see vs. what stays internal.

Access modes & links

Access modes: Public, private, or restricted, depending on deployment.
Registration codes & links: Per-cohort codes and share-links to control who joins.

Data residency

EU data storage with transparent AI infrastructure

SLAN stores application data in Europe. LLM inference is processed by third-party APIs. Here is what that means for your deployment.

Application data

Stored on AWS eu-central-1 (Frankfurt)
Covers user accounts, course content, conversation history, and cohort data
No cross-region replication by default

LLM inference

Processed by third-party AI APIs based in the US — standard across AI-powered products
Prompts and responses pass through these APIs; review their data processing terms for your use case

If EU-only inference is required, we can discuss EU-hosted model options or customer-managed deployment patterns during your governance review.

Looking for legal text? See Privacy and Terms.

Align on governance early

Request a demo to discuss content boundaries, cohort scoping, data residency expectations, and what you can publish from pilots.

Request a demo See how it works