Most training videos cover internal material - proprietary processes, unreleased products, employee workflows, compliance procedures, and operational details that companies do not share publicly. If you are commissioning animated training content, the studio you hire will see confidential information. That is unavoidable. What matters is how that information is protected.
This guide covers what to expect when working with an animation studio under NDA: what the NDA should include, what security practices to ask about, and how to structure the engagement so your confidential material stays confidential.
When You Need an NDA
Not every training video project requires an NDA. A general safety awareness video built from public OSHA guidelines does not contain proprietary information. But most corporate training content does. You need an NDA when the video will cover:
- Proprietary processes or workflows - How your organization does something that competitors should not see
- Unreleased products or features - Pre-launch product training, feature walkthroughs, or roadmap previews
- Internal systems and tools - Software interfaces, dashboard layouts, or system architectures that reveal operational details
- Employee or customer data - Even anonymized or sample data used for context during script development
- Compliance and regulatory procedures - Internal audit processes, incident response protocols, or regulatory submissions
- M&A or organizational changes - Restructuring plans, acquisition integrations, or leadership transitions communicated through training before public announcement
If you are unsure, default to using an NDA. The cost is zero (it is a standard document), and the protection is significant.
Types of NDAs for Creative Projects
| NDA Type | Who Is Bound | When to Use |
|---|---|---|
| One-way (unilateral) | Only the studio is bound to protect client information | Standard for most training video projects where the client shares proprietary content and the studio shares nothing confidential in return |
| Mutual (bilateral) | Both parties are bound to protect each other's information | Appropriate when the studio will also share proprietary methods, tools, or pricing structures they consider confidential |
| Project-specific addendum | Supplements a master NDA with project-level specifics | Used when you have an ongoing studio relationship with a blanket NDA and need to define additional restrictions for a particularly sensitive project |
A one-way NDA is sufficient for most training video projects. Mutual NDAs are common because studios often prefer them as a standard template - and there is no downside to the client in a mutual agreement.
What Your NDA Should Include
A generic NDA template covers the basics, but training video projects have specific information flows that a well-drafted NDA should address:
- Definition of confidential information - Be specific. "All information shared during the project" is too broad to be enforceable in some jurisdictions. List categories: scripts, storyboards, process documentation, product specifications, employee names or likenesses, internal metrics, and system screenshots.
- Permitted use - The studio may only use confidential information for producing the contracted video. Not for marketing, case studies, blog posts, or AI training data.
- Who has access - Limit access to named team members working on the project. If the studio uses freelance animators or subcontractors, the NDA should require them to be bound by the same confidentiality terms.
- Duration - How long the confidentiality obligation lasts after the project ends. Two to five years is standard for creative projects. Trade secrets (formulas, algorithms, proprietary methods) should be protected indefinitely.
- Return or destruction of materials - What happens to your confidential files after the project is complete. Options: the studio returns all materials and certifies destruction, or the studio retains files under the ongoing NDA terms for potential future edits.
- Portfolio and publicity rights - Address this explicitly. Can the studio mention that they worked with your company (without showing the video)? Can they show the video after a specified embargo period? Can they use still frames in proposals to other clients? Define the boundaries clearly.
- Remedies - What happens if confidential information is disclosed. Standard language includes injunctive relief (a court order to stop the disclosure) plus damages. This section is usually drafted by your legal team.
Security Practices to Ask About
An NDA is a legal protection. Security practices are operational protections. Both matter. During vendor evaluation, ask these questions:
- How are files shared? Encrypted cloud storage (Google Drive with access controls, Dropbox Business, Frame.io) is the minimum standard. Email attachments for sensitive files are a red flag.
- Who accesses project files? Production should be limited to the assigned team. Ask whether freelancers or offshore subcontractors will touch the project - and whether they are bound by the same NDA terms.
- Where are files stored? Cloud-based project management tools with access logging (who opened what, when) provide accountability. Local hard drives with no backup or access controls do not.
- What happens to files after the project? Confirm whether the studio has a data retention policy and whether they will certify destruction of your materials at project close if requested.
- Does the studio use AI tools in production? If the studio uses AI-assisted animation or scripting tools, confirm that your confidential content is not uploaded to third-party AI platforms for processing. This is a growing concern - see our post on AI video quality for enterprise for context on how responsible studios handle AI tool usage.
Working with Sensitive Subject Matter
Some training content is more sensitive than others. Product launches and internal processes require standard NDA protection. But certain categories require additional care:
Healthcare and HIPAA - If training videos reference patient scenarios, even fictional ones, the studio should understand HIPAA requirements for protected health information. Animated training avoids this issue better than live-action because no real patients, facilities, or records appear on screen - but scripts that reference specific conditions, treatments, or patient demographics still require careful handling.
Financial services and SOX compliance - Training videos covering internal controls, audit procedures, or financial reporting processes may constitute SOX-relevant documentation. Your compliance team should review the NDA scope and the studio's data handling practices.
Defense and government contractors - Projects involving ITAR-controlled information, classified material, or CUI (Controlled Unclassified Information) require security protocols beyond a standard commercial NDA. Studios working on these projects typically need facility clearances or specific certifications.
For more on compliance-driven training video requirements, see our compliance training video guide.
Red Flags During Vendor Evaluation
These should give you pause before sharing confidential content with any production partner:
- Reluctance to sign an NDA - Any professional studio signs NDAs routinely. Hesitation suggests inexperience with enterprise clients or a lack of formal process.
- No clear answer on who accesses files - "The team" is not an answer. You should know which individuals will see your confidential content.
- Sharing files via personal email or consumer-grade tools - WeTransfer links, personal Gmail, or unsecured Dropbox without access controls are not acceptable for confidential corporate content.
- No data retention or destruction policy - If the studio cannot tell you what happens to your files after the project, they have not thought about it - which means your files will live on their servers indefinitely.
- Resistance to restricting portfolio use - A studio that insists on unrestricted portfolio rights for your internal training content is prioritizing their marketing over your confidentiality. Portfolio terms should be negotiable.
How Sharp Eye Animation Handles Confidential Projects
We work under NDA on the majority of our training video projects - it is standard operating procedure, not an exception. We sign client NDAs or provide our own mutual NDA before any confidential content is shared. Project files are stored in access-controlled cloud storage with team-level permissions. Freelancers and subcontractors are bound by the same confidentiality terms. At project close, we retain source files for potential future edits under the ongoing NDA terms, or certify destruction at the client's request.
If you are evaluating studios for a confidential training project, see our animation RFP checklist for a complete vendor evaluation framework.