Responsible AI
AI you can stand behind.
Kyndrify turns your face and voice into video. That only works if people can trust what comes out. A real-person Digital Twin needs current consent before it can render in a customer Workspace. Machine-verifiable disclosure and provenance are launch requirements being rolled out, and they are not yet guaranteed on every Render.
Current customer consent requiredIdentity checks when requiredProvenance rollout in progressDisclosure coverage in progressNo Kyndrify model trainingDelete from your Studio
Consent and identity records
- Consent before rendering. A customer Digital Twin representing a real person needs current consent before it can be used in a Render. We keep a record of that consent.
- Identity evidence, when required. When face matching is required, uploaded identity photos are checked against the consented subject before use.
- Permission stays current. For customer Digital Twins, withdrawn or expired consent blocks rendering until consent is renewed.
Machine-verifiable provenance is rolling out
- A launch requirement, not a live guarantee. We are rolling out signed Content Credentials across Render paths. They are not yet guaranteed on every file.
- Why it matters. When present, machine-readable provenance helps viewers inspect how a file was made.
- We won't overstate it. Some paths are best-effort today. We will only call the rollout complete when every required path blocks delivery if provenance is missing.
Watermark coverage is still being verified
- Visible free-tier marking. The free experience is designed to add a visible Kyndrify mark, but coverage is still being verified across every output path.
- Invisible markers are in rollout. Invisible provenance markers are part of the same launch requirement. They are not guaranteed on every output yet.
- Check before relying on them. Until the rollout is complete, do not assume a particular file carries every planned provenance layer.
Built around transparency
- Transparency is on the launch checklist. Kyndrify's launch requirements include disclosure and provenance work for AI-made media.
- The rollout is still in progress. Some output paths apply these steps best-effort today. Coverage is not yet guaranteed.
- Your publishing choices still matter. Follow the disclosure rules that apply where you publish, and contact us if you need the current status for a particular Render.
Your content is for your work
- Your content stays yours. Kyndrify does not use your photos, voice, scripts, or finished videos to train a Kyndrify model.
- Used only to make your work. We use what you give us to provide and protect the service, including producing the Render you requested and enforcing consent and safety.
- Necessary service processing. The services that carry out parts of a Render receive only the data needed for that job and handle it under their applicable terms and our privacy commitments.
You stay in control
- Delete anytime. You can remove a Digital Twin, an eligible standalone Render, or your profile from the Studio. If you own a shared Workspace, transfer its ownership or remove its other members before deleting your profile.
- Clear retention windows. Active personal content is removed promptly after account deletion. Some deleted Digital Twin data can remain recoverable for up to 30 days, while consent and other legally required records follow their stated retention periods.
- Your Workspace, your call. You decide what gets made and what gets kept. We don't reuse your likeness for anything you didn't ask for.
In plain terms
Honesty includes the current status.
We are rolling out machine-verifiable disclosure and provenance as launch requirements. They are not guaranteed on every Render yet, and we won't describe the rollout as complete until every required path enforces it. If you need to confirm what a particular Render carries or where your data lives, email hello@kyndrify.com.
Make something you can trust.
Build a Digital Twin with consent on the record and control over what you make.