Studio
Privacy

Aioravid Studio

Privacy Policy

Last updated: September 14, 2026 · Version 2026-09-14

1. Who controls your data

This policy describes how Aioravid Studio processes personal information in connection with Aioravid Studio. If another organization provides your account, that organization may separately control information it submits or manages.

2. Information we process

We may process account details such as name, email and mobile number; authentication/session identifiers; prompts and scripts; uploaded images, audio and video; generated output; project/editor state; credit and subscription records; support communications; device, browser, IP, security and diagnostic logs; and payment-provider event metadata needed to reconcile purchases. The application is not designed to store raw card credentials.

3. Why we use information

We use information to authenticate users, provide AI generation and editing, save projects, calculate credits and limits, process and reconcile payments, prevent fraud and abuse, secure the service, troubleshoot failures, respond to support requests, maintain service reliability and comply with legal obligations.

4. AI and service providers

When you request a feature, the minimum content reasonably required for that request may be transmitted to configured AI, media-processing, hosting, storage, authentication or payment providers. Provider handling may occur in other countries and is also subject to the provider's applicable privacy terms and contractual safeguards.

5. Sharing

We do not sell personal information as part of the Aioravid product. We may share information with service providers acting for us, with payment and fraud-prevention providers, when you direct us to share or publish content, during a lawful corporate transaction, or when reasonably necessary to comply with law, enforce rights, prevent harm or protect the service.

6. Storage and retention

Account and project records are retained while needed to provide the service and for legitimate security, billing, dispute and compliance purposes. Generated media may remain on provider or storage systems according to configured retention and provider policies. Deleted records may persist temporarily in backups or legally required records. We aim to avoid retaining data longer than reasonably necessary for its purpose.

7. Security

We use authentication, ownership checks, server-side secrets, access controls, rate limits and storage policies intended to reduce unauthorized access. No internet service can guarantee absolute security. Keep your password private, use a trusted device, and notify support if you suspect account compromise.

8. Your choices and rights

Depending on applicable law, you may have rights to access, correct, delete, restrict or object to certain processing, or request a portable copy of certain information. Product controls may allow project deletion and account-security actions. For account/data requests, contact Support. We may need to verify identity before completing a request.

9. Payments

Payments are handled by the configured payment provider. Aioravid stores normalized payment, subscription and credit events needed to reconcile your account, detect abuse and maintain financial records. The payment provider may independently process billing information under its own privacy policy.

10. Cookies and local storage

Authentication and security may use cookies. The editor may use browser storage such as IndexedDB to preserve local project state and media. Clearing browser data can remove locally stored editor material that has not been uploaded or synced.

11. Children

Aioravid is intended for adults and is not directed to children under 18 or under the legal age required to consent to the service in their jurisdiction. Do not knowingly submit a child's personal information without lawful authority.

12. International processing

Because cloud and AI providers may operate globally, information can be processed outside your country. Where required, the operator should use legally recognized transfer mechanisms or provider contractual protections.

13. Changes to this policy

We may update this policy as product capabilities, providers or legal requirements change. The version and date above identify the current policy. Material changes should be communicated where applicable law requires it.

14. Contact

Privacy questions or rights requests should be submitted through the Support page. A monitored privacy/support address must be configured before public launch.