Legal
Privacy Policy
Last updated: October 8, 2026
What we collect
- Account data — email address, display name, password hash (scrypt; we never store plain passwords), and optional Google profile if you use Google sign-in.
- Uploads — the photos and short written directions you upload, stored privately by default.
- Service data — job status, moderation results, credit ledger entries, payment order records.
- Session data — a session cookie (HttpOnly) whose token is stored only as a SHA-256 hash, plus a hashed IP for abuse prevention.
How long we keep things
- Draft uploads that never enter generation: 7 days.
- Input photos: 14 days after a video completes.
- Generated outputs: 14 days. Download them before expiry — your videos page shows the exact date for each video.
- Account, order and credit ledger records: kept while your account is active, as required for accounting and dispute resolution.
When a file expires it is deleted from storage automatically; its database record is kept only as a tombstone for accounting and abuse prevention.
Who processes your data
We use processors to run the Service: a database host, object storage, AI model providers (to generate videos), a moderation provider (input and output safety review), an email provider (transactional email), and a payment provider. We never sell personal data.
Your rights
You can access, correct, export, or delete your account data from the account page or by emailing privacy@aigenvideo.com. Deleting your account removes personal data; ledger entries required for accounting are retained in anonymized form.
Cookies
We use one essential session cookie for login. No advertising or tracking cookies are used in V1.
What we collect, and why
Your account
Email address, display name and authentication credentials — the minimum needed to identify your account, secure it, and deliver notifications. Sign-in with Google shares only the email and name you approve on the Google consent screen.
Your uploads and outputs
The photos you upload and the videos we generate for you. They are stored privately behind signed, expiring links, and both are deleted automatically 14 days after generation. Uploads that never enter a generation are removed on the draft schedule.
Billing records
Order amount, currency, status and the Stripe identifiers needed to reconcile payments and honor refunds. Card details never touch our servers — they go directly to Stripe.
Operational logs
Generation parameters (model, resolution, length), moderation outcomes, and error logs — used to run the service, support failures, and bill accurately. Request payloads with your photos are not kept beyond the operation that uses them.
Who processes your data
Generation and safety review: SeeAPI. Payments: Stripe. Transactional email: Resend. Storage: Cloudflare R2. Each processor receives only the data its step requires — your photos go to the generation and review steps, your payment details to Stripe, your email to Resend — and nothing is sold, shared for advertising, or used to train models.
Your rights
You can delete your account and its data at any time, download your generated videos before their expiry, and request a copy of your billing records. Requests are honored within 30 days — the contact address is on the terms page.
Minors, cookies and analytics
The service is 18+, and age is enforced at generation through the content policy — there is no legitimate use case for a minor's photos in the pipeline, and uploads containing them are blocked and sanctioned.
The site sets two kinds of cookies: the session cookie that keeps you signed in, and a short-lived nonce cookie used by sign-in with Google. Neither is used for advertising, and there are no third-party tracking pixels. Server logs keep request metadata for operational debugging only.
International users: your data is processed in the locations where our processors operate (the United States and the provider regions described above), under the contract terms incorporated into these pages.
Changes to this policy are announced on this page with a new effective date. Material changes — new processors, different retention, new data uses — are announced at least 14 days before they take effect.
How your data is protected
Everything private is behind signed, expiring links — objects are never public pages, and every file request re-checks ownership or a valid HMAC token. Credentials are hashed, sessions are revocable per device, and the signing keys live only in server environment variables. Payment details are isolated at Stripe, and the generation pipeline pulls your photos through short-lived scoped links that stop working the moment the operation ends.
What we do not do
We do not sell data — not your email, not your photos, not your generation history. We do not use your uploads to train models, ours or anyone else's. We do not build advertising profiles, we do not run third-party trackers, and we do not send marketing email you did not ask for — the only emails are transactional: account security, verification, payment receipts and generation status.
Security practices
All traffic is HTTPS. Private files are addressed by unguessable keys behind ownership checks and expiring signatures. Sessions are database-backed and revocable per device, passwords are stored hashed with a modern password hashing function, and every write request passes an origin check against cross-site misuse. No system is perfect — but the design assumes your uploads are sensitive, because they are.
Generation inputs versus generation outputs
Your uploaded photos and the finished videos are treated as two separate retention pools with the same purpose: long enough to use, short enough to matter. Both are deleted on the 14-day schedule from the moment a generation completes, and both are deleted earlier if you remove them yourself from the library. Deletion is real deletion — the object is removed from storage and the record is tombstoned, not merely hidden from your view.