AIVid. / Company
Trust & clarity
Clear words.
Visible rules.
Trust should not depend on vague promises. This is the starting point for AIVid.'s policies, content standards, and the routes available when you need help.
Policy desk
AIVid. / Company
Trust & clarity
Trust should not depend on vague promises. This is the starting point for AIVid.'s policies, content standards, and the routes available when you need help.
Policy desk
Public record / 04
Each policy answers a different kind of question. The complete wording, scope, and current update date live in the published source.
A clear route / 03
Trust pages work best as a route, not a wall of claims. Start with the public source, add safe context, then choose the right contact channel.
Choose the policy closest to your question. The source pages contain the full wording, scope, and last-updated date.
For account or billing help, include your account email, the affected feature, what happened, and safe screenshots or order references when relevant.
Use [email protected] for detailed requests or @aivid_support on Telegram for quick general guidance. Both routes are listed on Contact.
Content safety / 03
The short version is useful, but the published Content Safety Policy remains the source for definitions, scope, restricted categories, and prohibited use.
Use content you own or have permission to use. The published rules address copyright, likeness, privacy, voice, and other rights across inputs and outputs.
The Content Safety Policy calls for consent and clear disclosure in relevant real-person synthetic media contexts and prohibits deceptive or exploitative use.
Review generated outputs for legality, accuracy, and rights clearance before publishing or using them in another workflow.
FAQ / 05
Short answers that point back to the published source instead of replacing it.