## Overview

As an Embed partner, you need flexibility **and** trust. Your clients rely on your platform integrations to deliver seamless learning experiences—so data security and responsible AI use must be built in, not bolted on.

This article explains how Coassemble approaches AI capabilities and data security, and what that means for you and your end-customers.

## AI innovation without compromising data control

Coassemble includes generative AI features to help you create and improve learning content faster—while keeping your data secure and under your control.

### How Coassemble uses AI

Coassemble integrates directly with **Google’s AI services** for AI capabilities.

Models used include:

* **Gemini Flash** for text generation, including course generation, document transformation, text refinement, and translation.

* **Imagen** for AI-generated images, with a planned move to **Gemini 2.5 Flash Image** in a future release for sharper, more detailed visuals and improved prompt accuracy.

* **Chirp** for AI narration voices.

> Note: Specific model and feature details may change over time. Refer to the provider’s terms of service and data policies for the most current information.

### Customer data is not used to train AI models

A core principle of Coassemble’s AI approach is that **customer data is not used to train the underlying AI model**.

* Content you upload or generate remains yours.

* Coassemble does not feed your documents, course content, or prompts back into the model for training.

* When you use features such as **Transform a document**:

  * Your document is securely stored in object storage.

  * Relevant course context is retained in Coassemble’s database to support generation.

### Content ownership

* **You own the output.** Anything generated with Coassemble AI tools is fully owned by you.

* Through your Embed integration, this ownership extends clearly to your end-customers.

* Ownership applies whether content is:

  * AI-generated, or

  * Manually created in Coassemble.

## Data storage, encryption, and trust standards

Coassemble applies the same rigorous security controls to AI features as across the entire platform.

### Security controls

* **Encryption in transit and at rest**

* **Strict access control**

* Alignment with **industry best-practice security frameworks**

### Data location and default hosting

* By default, data is stored on **US-based infrastructure** (currently Oregon, USA).

* AI processing requests are also executed in the **United States**.

* If you have specific data residency requirements, see [Regional infrastructure for Embed partners](#regional-infrastructure-for-embed-partners) and [Server architecture for Embed partners](#server-architecture-for-embed-partners) below.

### Compliance and certifications

Coassemble maintains security and compliance standards to support enterprise customers.

* **GDPR compliance** (without formal GDPR certification)

* **SOC 2 Type 2 certification**

Certifications and security controls are available via the **Coassemble Trust Centre**:

* <https://trust.coassemble.com/>

## AI processing pathway and subprocessor reduction

Coassemble has updated how the AI Course Creator processes data to improve:

* Reliability and performance

* Data governance

* Transparency in data handling

Coassemble now integrates directly with **Google’s AI services**, which supports:

* AI processing in a **fixed, known region**

* Fewer subprocessors

* Clearer data-handling pathways for compliance and audit needs

* Expansion of regional infrastructure options for partners with specific requirements

This shift enables Coassemble to:

* Ensure AI processing happens in a fixed, known region

* Reduce the number of subprocessors involved

* Improve data-handling transparency and compliance

* Prepare for region-specific infrastructure options

## AI image generation

Coassemble is in the process of moving **from Imagen to Gemini 2.5 Flash Image** for AI-generated images, producing sharper, more detailed visuals with improved prompt accuracy and consistency.

Coassemble will notify partners once this switch has occurred.

## Server architecture for Embed partners

Your server environment is **chosen upfront** as part of partnership setup. Configuration is set at the start of the partnership and cannot be changed after sign-up without starting a new account.

Coassemble offers five server options:

### 1) Standard Release server *(previously Production)*

* Shared environment that receives platform updates immediately on each release.

* For Embed customers using the Controlled Release server in production, the Standard Release server typically serves as their dev/test workspace.

### 2) Controlled Release server *(previously Enterprise)*

* Shared environment that receives platform updates **two weeks after** the Standard Release server.

* Releases are more rigorously validated, giving customers extra preparation time at each stage.

* Designed for production stability.

### 3) Region-Locked Server

* All data is processed and stored within a specified region: **UK** or **EU**.

* For partners with data residency or compliance requirements.

### 4) Dedicated server

* Private, single-tenant environment.

* Can optionally be region-locked.

### 5) Self-hosting

* Available for partners with specific deployment requirements.

* Subject to commercial approval and discussed during partnership setup.

## Regional infrastructure for Embed partners

For Embed partners with data residency or compliance requirements, Coassemble offers a **Region-Locked Server** option in addition to our US-based infrastructure.

### Available regions for region-locked servers

* **UK**

* **EU**

With Region-Locked Server enabled, data is **processed and stored within the selected region**.

## What this means for you as an Embed partner

These controls and commitments help you meet your own customer promises.

* **Confidence for your clients:** Assure end-customers that your integrated offering does not introduce unexpected data-use risks.

* **Clear ownership:** Content created through your Embed integration remains owned by your clients, with no hidden downstream usage.

* **Regulatory alignment:** For customers with compliance requirements (for example, GDPR or SOC 2), you can reference Coassemble’s certifications and data-location transparency.

* **Scalable innovation:** Benefit from Coassemble’s AI improvements without building or maintaining an AI stack, so you can focus on your Embed experience and differentiated features.

## Related resources

* Coassemble Trust Centre (security controls and certifications): <https://trust.coassemble.com/>

* Google AI provider terms of service and data policies: <https://ai.google.dev/gemini-api/terms#data-use-paid>



AI and Data Security for Coassemble Embed Partners

Resources specifically for Embed (previously referred to as Headless course creation). These are resources that previously lived on the Headless Resources Hub.

Coassemble Embed Partner Security, Data Protection & AI FAQ

Default usage caps for clients

Managing tenant caps

Accessibility guide

Coassemble vs. Articulate: Feature comparison guide for course authoring teams

Coassemble is WCAG 2.2 Level AA Conformant

Competitor analysis

Designing effective microlearning courses

How to access and interpret the Headless usage report

How to handle competitor objections when positioning your Embed solution

Guide to pricing models for Coassemble Embed and key competitor benchmarks

Sales enablement guide: Driving user adoption

Customer testimonials for Coassemble Embed course creation (sales enablement)

Our mission: Barrier-free knowledge transfer (partner-friendly positioning language)

Getting started guide

How to communicate Coassemble feature releases to your customers 

How to migrate courses from other authoring tools into Coassemble Embed

Guide to releases

Curate

AI Create

Customize

Learner experience

Embed Partners

Release notes

General

What is Coassemble?

Coassemble terminology explained

Accessing the login page

Getting to know your Coassemble workspace

Build the business case for Coassemble

Getting started: Common questions

How do I sign up for a Coassemble account?

What file types can I transform into a course?

What is a screen?

What tone should I select?

What is a collection?

Can I use Coassemble as an LMS?

How to log in to your account

Getting started

Connecting to Google Drive or OneDrive

Convert a presentation into an online course

Your knowledge

Usage limits

Identified Recipients and Anonymous Recipients

Logging in with Microsoft

Folders

Creators

Transfer ownership of your workspace

Configuring your email preferences

Common questions: Workspaces

How to delete a creator

Managing account, workspace, and billing settings

Organizing courses with folders

Your workspace & settings

How to upload custom fonts in Coassemble

How to save a legacy course theme

Brand kit: Saving pre-existing themes

How to apply Brand voice when generating courses

Brand voice

Asset library

Managing logos

How to create and configure themes

Managing and defaulting themes

Using the Brand kit

Brand Kit: A complete guide

How to edit video details

Brand kit

AI image generation

Generate a screen with AI

Refine with AI

Difference between transforming a document and converting a presentation

Coassemble's AI

Screens

Creating courses from scratch

Deleting courses

Duplicating courses

Enforce completion of videos

Generate a course with AI

The Finish screen

The Quiz screen

Transforming a document to a course

Translations

Images

Upload your videos to your course

Which screen should I use?

How do I create a course?

Common questions: Course creation

How to Upload Videos to Your Course

Narrating translations

Narration

Publishing

Loom integration

How to preview and review a course

Customizing course appearance with Themes

Managing and editing your course

Guide to AI Narration Tokens in Coassemble

Create & customize

Sharing course links & invitations

Collections: create, customize, share, and track learning paths

How to import a course from a template link

How to share your courses

Sharing courses with Slack

SCORM packages and translations

Exporting courses as SCORM

Common questions: Sharing

Template links

Email invitations

How to Add Your Coassemble Courses to Another Platform

How Coassemble tracks unique anonymous users

Sharing

How to filter Course insights by date range

Course insights

Link Insights

SCORM usage

Common Questions: Tracking Learners, Reporting, and Limits in Coassemble

Detailed Quiz results

Sentiment

Analyzing course-level Insights

Analyzing Collection-level Insights

Tracking content performance with Insights

Insights

Flow

Pulse

Embed Core

Embed Automate

Embed Partner

Overage, bands, and rates

Payments, billing, and subscriptions

Plans and advanced features

Explore best practices for sharing your knowledge.

Accessibility

Assessment: Best practice for quizzes

Best practices

SCORM files not loading

SCORM session errors on Apple devices

Why isn't my Embed screen working?

Common questions: Troubleshooting

What do I do if there is a bug?

Requesting a password reset link

Setting a new password

How to change or reset your password

Troubleshooting

SOC 2 compliance

Coassemble's approach to AI

AI & data security

Data security & AI

API keys

Passing identity (and tenant context) in embedded sessions

Notion

YouTube

Hubspot

Arcade

Vimeo

Unsplash

360Learning

aNewSpring

Docebo

Embed and Stripe: How to Sell Access Using Your Own Checkout and Coassemble Embed