Privacy Policy

1. Who this covers

This policy applies to aiEdit.pro (the “Service”), including the marketing site, the studio application, and its APIs. It describes what we collect when you visit the site, create an account, generate media, or contact us.

2. What we collect

Account information

When you sign up we receive your name, email address, and profile image from our authentication provider. If you sign in with Google or another identity provider, we receive the basic profile that provider releases. We never receive your password.

Content you create

Prompts, scripts, storyboards, project settings, uploaded images and audio, and the video, image, and audio files generated on your behalf. This content is stored so the Service can show it back to you and so you can export it.

Usage and billing records

Credit balances, generation history, model selections, render jobs, plan tier, and subscription status. Payment card details are handled entirely by Stripe — they never reach our servers.

Technical data

Server logs including IP address, user agent, requested route, and timestamps, retained for security, abuse prevention, and debugging.

Messages you send us

If you use the contact form, we store the name, email address, subject, and message you submit so we can reply.

3. How we use it

• To operate the Service: run generations, save projects, and deliver exports.
• To meter credits and process subscriptions and renewals.
• To provide support and respond to your messages.
• To detect abuse, prevent fraud, and keep the platform available.
• To improve the product in aggregate — how features perform, where errors occur.

We do not sell personal information, and we do not use your private project content to train our own or third-party models.

4. Processors we share data with

Running the Service requires sending certain data to infrastructure providers. Each receives only what its function requires:

• Clerk — authentication and session management (identity, email).
• Stripe — subscriptions and payments (email, plan, payment details you enter on Stripe’s own forms).
• Neon / Postgres — the application database (accounts, projects, credits, contact messages).
• Vercel — application hosting, edge delivery, blob storage for media, and request logs.
• AI model providers — the prompts, reference images, and parameters needed to fulfil a generation you request. These are routed through model gateways and providers including FAL and the Vercel AI Gateway, and reach the specific model you select (for example Sora, Veo, Kling, Luma, or ElevenLabs). Each provider’s own terms govern the request it receives.
• Render workers — our export service, which receives the scene payload for a render job you start.
• Resend — transactional email delivery, when configured.

We may also disclose information where legally required, or to protect the rights, safety, and property of our users or the Service.

5. Retention

Account and project data is retained while your account is active. Generated media is retained until you delete it or your account is closed. Server logs are retained on a rolling short-term basis. Billing records are retained as long as required for tax and accounting obligations. Contact form messages are retained until resolved and then periodically purged.

6. Your choices and rights

You can edit your profile and delete projects and generated media from within the application at any time. Depending on where you live, you may also have the right to access, correct, export, or delete the personal data we hold, and to object to or restrict certain processing.

To make any of these requests, contact us through the contact page. We will respond within the timeframe required by applicable law.

7. Cookies

We use cookies that are necessary to run the Service: session cookies set by our authentication provider to keep you signed in, and preference cookies that remember interface choices. We do not use third-party advertising cookies on the application.

8. Security

Traffic is encrypted in transit. Access to production data is restricted to the people who operate the Service. API routes that mutate data or spend credits require an authenticated session, and export payloads are signed. No system is perfectly secure, so we encourage you to use a strong, unique password and to keep your account credentials private.

9. Children

The Service is not directed at children under 13, and we do not knowingly collect their personal information. If you believe a child has provided us data, contact us and we will delete it.

10. International transfers

Our infrastructure providers operate globally, so your data may be processed in countries other than your own, including the United States. We rely on our providers’ standard contractual protections for those transfers.

11. Changes

We may update this policy as the Service evolves. Material changes will be reflected in the “last updated” date above, and significant changes affecting how we use your data will be communicated in-product or by email.

12. Contact

Questions about this policy or a data request? Reach us via the contact page.