Privacy and data

Use Onira with the same care you would apply to any production tool that processes prompts, files, generated media, and team workspaces.

Data surfaces

Onira projects can contain:

• User prompts.
• Project titles and descriptions.
• Saved characters.
• Voice selections.
• Uploaded or attached source material.
• Generated images.
• Generated video clips.
• Generated audio.
• Timeline and subtitle state.
• Rendered output files.
• Billing and usage records.

What to avoid in prompts

Avoid putting unnecessary sensitive data into prompts, including:

• Passwords or API keys.
• Private customer records.
• Unredacted financial, medical, or legal documents.
• Material you do not have permission to use.
• Secrets that do not need to influence the output.

Source material

When using source material, provide only the context needed to create the video. For high-stakes subjects, keep a separate review process for claims before publishing.

If the material is confidential, confirm that it is appropriate for processing before uploading or referencing it in a production.

Workspace access

Workspace members can affect projects, credits, and production settings according to their permissions. Keep membership current, especially for agencies and client-facing teams.

Remove members when they no longer need access. Review membership before inviting external collaborators into a client workspace.

Generated assets

Generated assets, versions, renders, and project state are part of the project history. Treat them as production material and review before sharing externally.

Generated output can still contain factual, visual, continuity, or rights issues. The workspace remains responsible for final review.

Project links and sharing

Project sharing controls can change over time. Before sending a project externally, confirm the current share state in the live app.

When sharing with clients, prefer finished renders unless the client needs Studio review access.

Support

For billing or account questions, contact support with the workspace name, project link when relevant, invoice number for billing cases, and a concise description of the issue.

Do not send passwords, API keys, private keys, or unrelated personal data to support.