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.
Governance
Content ownership, access boundaries, and provenance
SLAN is designed to support explicit permissions, cohort scoping, and careful handling of proprietary materials.
Content ownership
Course materials remain owned by the professor or institution; internal playbooks remain owned by the company.
Review before release
Treat extracted structures as proposals. 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.
- Course- and cohort-scoped availability
- Public, private, or restricted access modes
- Registration link and code generation
Data residency
EU data storage with transparent AI infrastructure
SLAN stores application data in Europe. LLM inference is processed by third-party APIs — this page explains 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.
Align on governance early
Request a demo to discuss content boundaries, cohort scoping, data residency expectations, and what you can publish from pilots.