Review the guidance. Define the access. Understand the data flow.

Set up coaching with clear content and audience boundaries.

You see what the coach will guide people through.

  • Review

    Inspect the proposed frameworks before they're released to anyone.

  • Sources

    See which modules and documents informed each framework.

  • Access

    Manage availability by course, assistant and cohort.

0:00 / 0:00
Review the proposed guidance. Approve what is ready to share.

Scope access by course, assistant and cohort.

Choose who can use each coach and how they join.
  • Cohort management

    Run several cohorts on one course without duplicating anything.

  • Assistant assignment

    Give a cohort every assistant in the course, or a curated subset.

  • Private, Registration Code or Public

    Set on the course, on each assistant and on each cohort.

  • Joining

    Learners sign up with the cohort's registration code, or you add members by email.

Where data is stored and processed.

Application data is stored on AWS in Frankfurt. AI model processing may take place outside the EU.

Application data

  • Stored on AWS eu-central-1 (Frankfurt)

  • Accounts, course content, conversation history and cohort data

  • Encrypted in transit and at rest; no cross-region replication by default

  • Conversation data deleted 24 months after last activity

Model providers

  • Google Gemini, Anthropic (Claude) and OpenAI

    Accessed under their paid API terms, not free tiers.

  • Not used for model training

    SLAN's published policy states that submitted content is not used for model training.

  • Model processing may take place outside the EU

    If you need EU-only processing, discuss the available model-hosting options before deployment.

Review your requirements before a pilot.

Agree permitted materials, access boundaries and data-processing requirements before sharing sensitive content.