✓ Teams starting with approved written explanations
✓ Readers comparing script, recording and presenter workflows
✓ Editors budgeting review and revisions
— Fake endorsements or fabricated demonstrations
— Guaranteed income, viral reach or automatic courses
— High-stakes training without qualified review
Build an asset record before assembly
For each image, recording, music track or text source, record where it came from and the permission that supports the intended use. Keep original assets distinguishable from examples and placeholders. A file being available online is not permission to republish it. Likewise, a source supplied by a client may still need clarification about its ownership or allowed distribution. Resolve uncertainty before the material spreads across several video variants.
Separate service rights from third-party rights
Fliki’s terms place responsibility for content on the user and restrict infringement and impersonation. A service’s commercial-use provision does not automatically clear someone else’s trademark, confidential record, copyrighted passage or personal likeness. Check the actual terms and plan that apply to your intended use. This guide is an operational checklist, not legal advice or a determination that a particular asset or use is permitted.
Treat voices and faces carefully
Do not clone or imitate a person merely because a recording or photograph is accessible. Establish appropriate permission for the proposed purpose and distribution. A synthetic character should not appear to deliver a real customer’s experience or a personal endorsement that was never given. Keep any required disclosure accurate and visible. When consent or rights are uncertain, use a clearly licensed alternative or a presenter-free format instead of inventing a justification.
A fictional client handoff
An agency receives product photographs and a voice recording for an explainer. It asks the client to confirm the permitted public uses and retains that record with the final asset inventory. A stock music license is checked separately; permission for the photographs does not cover the soundtrack. If a later request adds paid advertising or a different territory, review the scope again. This example shows why rights belong in the production record rather than as an assumption attached to a software invoice.
Where the safety evidence stops
This guide draws on Fliki content and service terms, Canva video editor. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.
Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Fliki content and service terms — Merchant documentation · fliki.ai · Merchant-controlled · checked 2026-09-24
- Canva video editor — Merchant documentation · canva.com · Merchant-controlled · checked 2026-09-24