Skip to main content
Skip to content

Security & AI FAQ

Common security, data protection, compliance, authentication, and AI questions for teams building with Coassemble Embed.

Data storage, regions, and encryption

Where is data stored and processed?

By default, Coassemble runs on US infrastructure. The application is hosted in Oregon, USA, and uploaded files are stored in AWS object storage in the US (us-east-1). This covers course content, uploaded documents and learner data. AI features use Google's Gemini models, through OpenRouter, our AI gateway.

Can you guarantee data is stored in a specific region?

Yes, with a region-locked server. Region-locked servers are available in the US, EU, UK and Australia, on the Partner plan. Your content is stored in the region you choose. The Standard Release server doesn't offer this guarantee.

Does AI processing run in the same region as my data?

Not always. Where AI runs depends on your server:

  • US servers: AI features use Google's Gemini models, through OpenRouter, our AI gateway.
  • UK servers: Your content is stored in the UK. AI processing, including image generation and narration, runs in Google's EU region.
  • Australian servers: Your content is stored in Australia, and AI text processing runs in Sydney. Image generation and narration are processed by Google outside Australia.
  • EU servers: Your content is stored in the EU, and AI processing, including image generation and narration, runs in Google's EU region.

For any other server, such as a US dedicated server or self-hosting, we confirm the AI processing region on request.

What encryption standards are used?

  • Data at rest: AES-256.
  • Data in transit: TLS 1.2.
  • Database: encrypted at rest, with keys managed by our hosting provider.

Environments and server options

Are different environments segregated?

Yes. Production and testing use separate environments and separate databases.

What server options are available?

Choose your server option with our team before you set up. The options are:

  • Standard Release server: a shared environment that receives platform updates immediately on each release.
  • Controlled Release server: receives updates after the Standard Release server, giving extra preparation time. Depending on your agreement, it's either shared or dedicated. The gap varies by release.
  • Region-locked server: your data is stored within a specified region, available in the US, EU, UK and Australia, for data residency or compliance requirements.
  • Dedicated server: a private, single-tenant environment, which can optionally be region-locked.
  • Self-hosting: the application runs in your own infrastructure, subject to commercial approval.

Region-locked servers, dedicated servers and self-hosting are available on the Partner plan. One locked region is included, and more regions can be added. See coassemble.com/pricing for plan details.

Authentication and cookies

Does the embedded experience use cookies?

No. The Embed flow is cookie-less by design so it works reliably inside iframes, which avoids problems caused by third-party cookie blocking in embedded contexts (for example, when Safari or Chrome treats an iframe as a third party). Coassemble does use cookies for the regular, non-embedded login experience.

How does authentication work in an embedded session?

Authentication uses a short-lived token (JWT) rather than a cookie-based session on Coassemble's domain:

  1. When the embeddable mounts, it holds a JWT in memory.
  2. It uses that JWT for each request to Coassemble's server.
  3. The signed link is valid for 3 hours by default. You can set it to anything from 30 seconds to 3 hours when you request the link.
  4. While the session is open, the token renews automatically, for up to 24 hours from when the link was first issued. After that, or as soon as the API key that issued it is revoked, the embed needs a new signed link.

Access controls and logging

What internal access controls are in place?

We follow an internal Access Control Policy, available on request. Only authorised engineers have administrative access to production systems, and multi-factor authentication is required for production access.

Are audit logs maintained?

Yes. Audit logs are generated, centrally managed and encrypted at rest. Server request logs are kept for about three months.

Compliance and documentation

Which security reports do you hold?

Coassemble has a SOC 2 Type 2 report covering the Security, Availability and Confidentiality criteria, and a SOC 2 Type 1 report. You can request them through the Coassemble Trust Centre at trust.coassemble.com. Coassemble isn't ISO 27001 certified itself, but the cloud providers underneath our hosting maintain SOC 2 Type 2 and ISO 27001 certifications.

Are you GDPR compliant, and do you have a DPA?

Yes to both. Our standard Data Processing Agreement (DPA) is public at coassemble.com/dpa and applies on every plan, so you don't need to ask for it. It includes terms specific to AI processing: AI is used for inference only, and neither we nor our AI sub-processors use your personal data, content, prompts or outputs to train or fine-tune any AI model.

Can you provide audit reports or security assessments?

Yes, on request through the Trust Centre.

Data retention and deletion

How long is uploaded data retained?

Your content is kept while your account is active, until you delete it. If you build courses through the API or an embedded builder, your developers can set discardSourceDocuments so Coassemble deletes its processing copies of your source documents after the course is built. The finished course keeps the content built from them. Database backups (up to 7 days) and our providers' own short retention periods still apply.

How do I delete data?

Use the Embed API to delete learners, their tracking and courses through the available endpoints. Deleting a course, learner or their tracking is a soft delete: the data is kept for the retention period that applies to your workspace, then permanently removed. Our team can tell you the retention period for your workspace.

During that period you can restore a deleted course through the API. For other deleted data, contact our team. Deleting a learner's tracking removes hosted SCORM resume data straight away, and deleting a client can't be undone.

Any UI to trigger deletion is built into your own integration. Opt-out processes are usually implemented on your side, and the deletion endpoints support those workflows.

Backups, incidents, and monitoring

What backups are in place?

Point-in-time recovery, allowing restoration to any point within the last 7 days.

What is your incident response plan?

We maintain an Incident Response Plan and a Business Continuity and Disaster Recovery Plan, both available on request.

How do you detect security and availability issues?

We use Vanta for continuous monitoring of our security and privacy controls, and Better Stack for uptime monitoring and our status page. We also monitor error rates, including AI error rates, with alerting.

Privacy and PII

Does Embed require me to pass PII?

No. The Embed API doesn't require you to pass any PII to identify users. We recommend passing pseudonymous identifiers, such as your own internal user IDs, rather than names or email addresses.

What data is sent to AI when documents are uploaded?

Uploaded documents are converted into a format the language model can process and sent to the model as they are, so any personal information inside a document is sent with it. Course features don't send account data or learner records to the model. When you upload a document to build a course from, the file is securely stored in object storage.

AI processing

Which AI providers and models do you use?

Coassemble integrates with Google's AI services: Gemini Flash for text generation (course generation, document transformation, text refinement, translation), Gemini Flash Image for AI-generated images, and Google's Chirp voices for AI narration.

Is customer data used to train AI models?

No. Customer content, prompts, and uploaded documents are never used to train the underlying models.

Can I switch AI off?

Yes. You can turn off AI content generation, AI narration and AI translation for any tenant through the embed configuration options.

Who owns AI-generated content?

You do. The customer retains full ownership of all content created in Coassemble, whether AI-generated or manually authored.

How large a document can I upload?

The models support a 1 million-token context window, so large documents (100 pages or more) can be uploaded, though the resulting course will be heavily summarised unless you choose Verbatim. The main guidance is pedagogical: keep courses short enough that people finish them.

This is about how much text a model can read in one go. It's a different thing from the narration and image generation allowances on your account, which are about usage rather than document size.

What guardrails exist against AI hallucinations?

The system includes guardrails to keep generated content aligned with training and learning objectives. All language models can still hallucinate, so full factual accuracy cannot be guaranteed. AI generation gets you 80 to 90% of the way to a complete course, with a human review pass recommended to finalise it.

What happens if an AI provider has issues or changes?

We monitor AI availability and error rates, with alerting. On US servers, requests go through OpenRouter, our AI gateway, which fails over between the providers serving the same Gemini model. It never swaps in a different model. On region-locked servers, the AI processing location is fixed, with no failover to another region or provider, so a regional outage makes the request fail rather than run somewhere else.

We give at least 14 days' notice before adding or replacing an AI sub-processor, as with any sub-processor. If a third-party AI provider has a breach that affects you, we'll tell you.

Subprocessors and infrastructure

Where are your subprocessors listed?

Our subprocessor list is available via the Coassemble Trust Centre at trust.coassemble.com/subprocessors. We vet subprocessors by reviewing vendor documentation and relying on published certifications and security assurances.

Who hosts the infrastructure, and how are denial-of-service attacks handled?

US servers are hosted on Render, in Oregon, USA. Region-locked and dedicated servers are hosted on Sevalla in their own region, with AWS object storage in the same region, and each runs its own applications and database. The hosting providers handle physical security, and the cloud providers underneath them maintain SOC 2 Type 2 and ISO 27001 certifications. Denial-of-service protection comes from the hosting platform, and our infrastructure auto-scales to absorb high-load traffic.

Do you conduct penetration testing?

Yes. An independent penetration test of our production web application and API (coassemble.com and api.coassemble.com) runs every year, with a re-test to confirm fixes. Reports are available on request through the Trust Centre.