Security and your data
The first question a serious buyer asks about AI is where their data goes and whether it could leak or be trained on. That question deserves a documented answer, not reassurance. Here is ours, including the parts we do not yet claim.
Data residency
Personal data has one home. Only two things ever cross a border, and neither of them is your personal data.
The controls
Buyers worry about two distinct things: that AI will be trained on their content, and that their content could leak. They are different problems, and they get different answers.
Production runs on enterprise AI, not the consumer tools that learn from what people type. The strictest no-training terms are activated before any confidential material is uploaded. Your content builds your academy and nothing else.
Your material and learners sit in your own tenant, enforced at the database. Isolation is continuously checked by an automated security suite, and a routine audit that found cross-tenant gaps had them closed and re-verified. Checked, not asserted.
Every AI action runs through the platform and its validation gate. There is no raw model to converse with that could carry one client's material into another's course. The AI is an ingredient, never an exposed endpoint.
The design goal at ingest is to keep as little of your raw source as possible: use it to produce the course, then hold your finished content rather than the confidential originals. Fewer copies, shorter-lived, is the leak answer.
You own the academy you build. Export it, in standard formats, and take it with you. Leaving does not strand your content, and we do not hold your library hostage to a renewal.
A data-processing agreement you can sign, a named sub-processor register, and a data flow you can walk your security team through. The kind of thing a vendor risk assessment actually asks for.
Two tiers
We would rather be exact than impressive. Some controls are live today; others are real engineering we provision for an enterprise pilot, not a switch we flip.
The nos, first
A trustworthy security page is as clear about its limits as its strengths. So, plainly:
We do not hold one, and we will not imply that we do. The controls above are real and documented; a formal certification is a road we can discuss, not a badge we are wearing.
There are no client references because there are none yet. The video and audio services run on their standard tiers today; their enterprise no-training tiers are activated before any client-confidential material, not after.
The dedicated database, EU-pinned processing and self-hosted media are real engineering we stand up for a pilot. We would rather scope them properly with you than pretend they are a checkbox.
Courses are training, grounded in your sources and reviewed by a named expert. They are not a legal opinion, and we are clear about that in the terms.
For your security team
We will take your team through the sub-processor register, the data-processing agreement and the residency picture, and answer a vendor security questionnaire directly. On a pilot, we honour deletion live.