Your data & privacy
A straight answer for the person actually using the app — not a stack of jargon. We’ll add formal terms where teams need them; this is the “what you should know” version.
You’re in charge of your work
You use Veyra to make something — a cut, a storyboard, a set of stills. That work is yours. We don’t use your uploads to train public models, sell personal dossiers, or do anything that would surprise you in a friend-to-friend conversation. If the product ever does something with your data that’s worth a banner, we’ll say it clearly, not hide it in clause 19.
What we need the service to do
To run the studio, we have to process what you put in: mixes, transcriptions, prompts, and the files you generate. That’s how a timeline, a render, or a review link exists. In practice that means: storage, compute, and (if you use hosted AI features) requests to the model providers you pick or that we list on the product — same idea as any serious creative app that talks to a cloud service.
What you can expect from us
We don’t want your creative process to be a data-mining project. We keep the focus on: giving you a stable place to work, being honest about who touches what, and replying if you have a question. Exact retention periods, subprocessors, and DPA text may be part of a signed agreement for teams; this page is the “what to tell your bandmate” version first.
If something’s wrong, talk to us
If you have a question about a project, export, or your account, use the same channels as everyone else: request access or book a call from the site. We’d rather have a real conversation than send you in circles.
Want to get started? Get started · Request access